MistyWest vs Very: full comparison for 2026
Quick verdict
MistyWest (4.0/5) edges ahead of Very (3.8/5) overall. MistyWest is the better choice for deep-tech startups at proof-of-concept stage. 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.
MistyWest vs Very: head-to-head summary
| Criterion | MistyWest | Very |
|---|---|---|
| Founded | 2010 | 2011 |
| HQ | Vancouver, Canada | USA (fully distributed) |
| Team size | 11–50 | 51–200 |
| Rating | 4.0 / 5 | 3.8 / 5 |
| Primary differentiator | Electrical, mechanical and firmware design for early hardware, aimed at manufacturability | Product-strategy-led IoT development with Nerves and Elixir experience |
| Pricing model | Time & materials, fixed project | Time & materials, fixed project |
| Min. engagement | Not disclosed | Not disclosed |
| Primary tech stack | C, C++, Zephyr | C, Elixir, Nerves |
| Industries served | Consumer electronics, Robotics, Energy & EV charging | Industrial IoT, Consumer electronics, Energy & EV charging |
MistyWest vs Very: overview
MistyWest
MistyWest is a Vancouver engineering consultancy that has worked on hardware, firmware and mechanical design for deep-tech companies since about 2010. Directory estimates put the team between 20 and 100 people, and it regularly hires contract firmware engineers for specific projects. Its sweet spot is early-stage hardware: proof-of-concept boards, battery-powered connected devices and robotics, carried through to designs a factory can build. Firmware is part of that product-development package rather than a standalone service line.
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: MistyWest vs Very
| Capability | MistyWest | 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: MistyWest vs Very
| Framework / platform | MistyWest | Very |
|---|---|---|
| FreeRTOS | ✓ | N/A |
| Zephyr | ✓ | N/A |
| Embedded Linux | N/A | ✓ |
| Yocto | N/A | N/A |
| AUTOSAR | N/A | N/A |
| STM32 | ✓ | N/A |
| Nordic | ✓ | ✓ |
| NXP | N/A | N/A |
| FPGA | N/A | N/A |
Pricing comparison: MistyWest vs Very
| Criterion | MistyWest | Very |
|---|---|---|
| Minimum engagement | Not disclosed | Not disclosed |
| Engagement models | Fixed project, Time & materials | Fixed project, Time & materials |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: MistyWest vs Very
| Dimension | MistyWest | Very |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Consumer electronics, Robotics, Energy & EV charging | Industrial IoT, Consumer electronics, Energy & EV charging |
| Best use cases | Building a battery-powered connected prototype for investor demos, Turning a lab prototype into a design ready for a contract manufacturer | Taking a first IoT product from concept to pilot, Building Nerves-based device software on embedded Linux |
| Typical project type | Fixed project | Fixed project |
MistyWest vs Very: pros and cons
| MistyWest | |
|---|---|
| + | Mechanical, electrical and firmware design in one team suits enclosure-heavy products |
| + | Comfortable with early, fast-changing prototypes |
| + | North American time zones with Canadian rates |
| - | Uses contract firmware engineers for some projects, so continuity varies |
| - | Less suited to long maintenance contracts on mature products |
| - | Small team |
| 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 MistyWest?
A typical fit: building a battery-powered connected prototype for investor demos.
Electrical, mechanical and firmware design for early hardware, aimed at manufacturability. Minimum engagement is not publicly disclosed. Works best with clients in Consumer electronics, Robotics, Energy & EV charging.
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: MistyWest vs Very
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | MistyWest |
| You need a large dedicated team for an ongoing programme | Check each company's engagement model |
| Your budget is at the lower end | Compare: MistyWest (Not disclosed) vs Very (Not disclosed) |
| You need specialist depth in a specific vertical | MistyWest |
| You need engineers to extend your own firmware team | Neither lists a dedicated-team model |
| You need consulting before committing to a build | Both may offer discovery engagements |
Use case fit: MistyWest vs Very
| Use case | MistyWest fit | Very fit | Winner |
|---|---|---|---|
| Building a battery-powered connected prototype for investor demos | Strong | Limited | MistyWest |
| Turning a lab prototype into a design ready for a contract manufacturer | Strong | Limited | MistyWest |
| 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: MistyWest vs Very
MistyWest (4.0/5) is the stronger overall choice for most Firmware Development projects. Electrical, mechanical and firmware design for early hardware, aimed at manufacturability.
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
MistyWest vs Very FAQ
Is MistyWest better than Very?
MistyWest (4.0/5) scores higher overall, but "better" depends on your use case. MistyWest's strongest advantage: Mechanical, electrical and firmware design in one team suits enclosure-heavy products. Very's strongest advantage: combines product strategy, design and engineering for teams new to hardware.
How do MistyWest and Very differ in pricing?
MistyWest uses time & materials, fixed project 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: MistyWest or Very?
Very 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 MistyWest and Very?
MistyWest's primary differentiator is: Electrical, mechanical and firmware design for early hardware, aimed at manufacturability. Very's primary differentiator is: product-strategy-led IoT development with Nerves and Elixir experience. They also differ in team size (11–50 vs 51–200), minimum engagement (Not disclosed vs Not disclosed), and primary industries served (Consumer electronics, Robotics vs Industrial IoT, Consumer electronics).
Verify all details directly with each service provider before making a decision.