Timesys vs Very: full comparison for 2026
Quick verdict
Timesys (4.1/5) edges ahead of Very (3.8/5) overall. Timesys is the better choice for linux devices facing SBOM and security compliance. Very is the stronger option for US companies building a first connected product. The right choice depends on your project size, budget, and required tech stack.
Timesys vs Very: head-to-head summary
| Criterion | Timesys | Very |
|---|---|---|
| Founded | 1996 | 2011 |
| HQ | Pittsburgh, Pennsylvania, USA | USA (fully distributed) |
| Team size | 51–200 | 51–200 |
| Rating | 4.1 / 5 | 3.8 / 5 |
| Primary differentiator | Embedded Linux services combined with Vigiles vulnerability tracking | Product-strategy-led IoT development with Nerves and Elixir experience |
| Pricing model | Fixed project, time & materials, software subscription | Time & materials, fixed project |
| Min. engagement | Not disclosed | Not disclosed |
| Primary tech stack | Embedded Linux, Yocto, Buildroot | C, Elixir, Nerves |
| Industries served | Industrial IoT, Medical devices, Aerospace & defence | Industrial IoT, Consumer electronics, Energy & EV charging |
Timesys vs Very: overview
Timesys
Timesys came out of Pittsburgh in the mid-1990s, with founders tied to Carnegie Mellon University, and shipped one of the first real-time embedded Linux distributions. Its business now combines engineering services for open-source embedded software with Vigiles, a tool that tracks vulnerabilities in device software bills of materials. Lynx Software Technologies acquired Timesys in December 2023 and said all Timesys products would remain supported. The firm suits Linux-based devices that have to meet the security and SBOM rules arriving in the US and EU.
Very
Very is a US IoT engineering firm that grew out of a design and development agency founded in 2011 and now works as a distributed team, with its earlier base in Chattanooga, Tennessee. Directory listings put its size at 51 to 200 people. It builds IoT products across hardware engineering, firmware, mobile apps and data, and it hired a co-author of the Nerves project, which runs Elixir on embedded Linux. Reviews mention hardware, firmware, React Native and AI feature work, so firmware is one part of a broader product offer.
Services and capabilities: Timesys vs Very
| Capability | Timesys | Very |
|---|---|---|
| Bare-metal & RTOS firmware | ✗ | ✗ |
| Embedded Linux & BSP | ✓ | ✓ |
| Electronics & PCB design | ✗ | ✓ |
| Wireless & IoT connectivity | ✗ | ✓ |
| Secure boot & OTA | ✓ | ✗ |
| FPGA development | ✗ | ✗ |
| Firmware testing & HIL | ✗ | ✗ |
| Dedicated team model | ✗ | ✗ |
Tech stack comparison: Timesys vs Very
| Framework / platform | Timesys | Very |
|---|---|---|
| FreeRTOS | N/A | N/A |
| Zephyr | N/A | N/A |
| Embedded Linux | ✓ | ✓ |
| Yocto | ✓ | N/A |
| AUTOSAR | N/A | N/A |
| STM32 | N/A | N/A |
| Nordic | N/A | ✓ |
| NXP | ✓ | N/A |
| FPGA | N/A | N/A |
Pricing comparison: Timesys vs Very
| Criterion | Timesys | Very |
|---|---|---|
| Minimum engagement | Not disclosed | Not disclosed |
| Engagement models | Consulting, Fixed project, Time & materials | Fixed project, Time & materials |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: Timesys vs Very
| Dimension | Timesys | Very |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Industrial IoT, Medical devices, Aerospace & defence | Industrial IoT, Consumer electronics, Energy & EV charging |
| Best use cases | Hardening an i.MX-based medical device's Linux image and producing an SBOM, Setting up ongoing CVE monitoring for a fleet of industrial gateways | Taking a first IoT product from concept to pilot, Building Nerves-based device software on embedded Linux |
| Typical project type | Consulting | Fixed project |
Timesys vs Very: pros and cons
| Timesys | |
|---|---|
| + | Vigiles gives continuous CVE monitoring for the Linux image after launch |
| + | Long history with Yocto, Buildroot and secure boot on common application processors |
| + | Practical help with SBOM requirements under US and EU cybersecurity rules |
| - | Acquired by Lynx Software in 2023; product focus may shift toward Lynx's hypervisor and RTOS line |
| - | Little bare-metal MCU firmware work |
| - | No hardware design services |
| Very | |
|---|---|
| + | Combines product strategy, design and engineering for teams new to hardware |
| + | Nerves experience is rare and useful for Elixir-based device software |
| + | Delivers the device, app and data platform together |
| - | Firmware is one part of a product agency offer |
| - | US rates without a lower-cost offshore option |
| - | Office location and headcount details vary between sources |
Who should choose Timesys?
A typical fit: hardening an i.MX-based medical device's Linux image and producing an SBOM.
Embedded Linux services combined with Vigiles vulnerability tracking. Minimum engagement is not publicly disclosed. Works best with clients in Industrial IoT, Medical devices, Aerospace & defence.
Who should choose Very?
A typical fit: taking a first IoT product from concept to pilot.
Product-strategy-led IoT development with Nerves and Elixir experience. Minimum engagement is not publicly disclosed. Works best with clients in Industrial IoT, Consumer electronics, Energy & EV charging.
Decision matrix: Timesys vs Very
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | Timesys |
| You need a large dedicated team for an ongoing programme | Check each company's engagement model |
| Your budget is at the lower end | Compare: Timesys (Not disclosed) vs Very (Not disclosed) |
| You need specialist depth in a specific vertical | Timesys |
| You need engineers to extend your own firmware team | Neither lists a dedicated-team model |
| You need consulting before committing to a build | Timesys |
Use case fit: Timesys vs Very
| Use case | Timesys fit | Very fit | Winner |
|---|---|---|---|
| Hardening an i.MX-based medical device's Linux image and producing an SBOM | Strong | Limited | Timesys |
| Setting up ongoing CVE monitoring for a fleet of industrial gateways | Strong | Limited | Timesys |
| Taking a first IoT product from concept to pilot | Limited | Strong | Very |
| Building Nerves-based device software on embedded Linux | Limited | Strong | Very |
| Fixed-price firmware build | Strong | Strong | Both |
| Extending an in-house firmware team | Strong | Strong | Both |
Verdict: Timesys vs Very
Timesys (4.1/5) is the stronger overall choice for most Firmware Development projects. Embedded Linux services combined with Vigiles vulnerability tracking.
Very (3.8/5) is worth a look if you need building Nerves-based device software on embedded Linux. If your situation matches that, Very is a competitive option.
Related comparisons
Timesys vs Very FAQ
Is Timesys better than Very?
Timesys (4.1/5) scores higher overall, but "better" depends on your use case. Timesys's strongest advantage: vigiles gives continuous CVE monitoring for the Linux image after launch. Very's strongest advantage: combines product strategy, design and engineering for teams new to hardware.
How do Timesys and Very differ in pricing?
Timesys uses fixed project, time & materials, software subscription pricing. Very uses time & materials, fixed project pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: Timesys or Very?
Timesys is the larger team and typically the better enterprise-scale choice. For very large programmes, verify team size and compliance coverage directly with each service provider before shortlisting.
What are the main differences between Timesys and Very?
Timesys's primary differentiator is: embedded Linux services combined with Vigiles vulnerability tracking. Very's primary differentiator is: product-strategy-led IoT development with Nerves and Elixir experience. They also differ in team size (51–200 vs 51–200), minimum engagement (Not disclosed vs Not disclosed), and primary industries served (Industrial IoT, Medical devices vs Industrial IoT, Consumer electronics).
Verify all details directly with each service provider before making a decision.