Lemberg Solutions vs Very: full comparison for 2026
Quick verdict
Lemberg Solutions (4.8/5) edges ahead of Very (3.8/5) overall. Lemberg Solutions is the better choice for connected devices needing firmware and electronics together. 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.
Lemberg Solutions vs Very: head-to-head summary
| Criterion | Lemberg Solutions | Very |
|---|---|---|
| Founded | 2007 | 2011 |
| HQ | Lviv, Ukraine (offices in Hamburg, Germany; London, UK; Kraków, Poland) | USA (fully distributed) |
| Team size | 200+ | 51–200 |
| Rating | 4.8 / 5 | 3.8 / 5 |
| Primary differentiator | Electrical engineering, firmware, cloud and an in-house hardware lab under one contract, with NXP, Microchip and ST partner status | Product-strategy-led IoT development with Nerves and Elixir experience |
| Pricing model | Fixed project, time & materials, dedicated team | Time & materials, fixed project |
| Min. engagement | Not disclosed | Not disclosed |
| Primary tech stack | C, C++, FreeRTOS | C, Elixir, Nerves |
| Industries served | Medical devices, Automotive, Energy & EV charging, Logistics & transportation, Industrial IoT, Consumer electronics | Industrial IoT, Consumer electronics, Energy & EV charging |
Lemberg Solutions vs Very: overview
Lemberg Solutions
Lemberg Solutions takes a device from schematic to field updates under one roof: electrical engineering, bare-metal and RTOS firmware, embedded Linux, FPGA programming, GUI work, connectivity and edge AI. The company started in Lviv in 2007, now has more than 200 people, and also runs offices in Hamburg, London and Kraków. Its firmware practice works across STM32, NXP i.MX and LPC, Microchip PIC and SAM, Nordic and Espressif parts, with FreeRTOS, Zephyr, Azure RTOS and VxWorks listed in its stack, and it holds partner status with NXP, Microchip and STMicroelectronics. Named clients include Astronics, Caltech, Speede, Ferno, Cellink and Bosch Rexroth. Processes are certified to ISO 27001 and ISO 9001, and an in-house lab with oscilloscopes, spectrum analyzers and evaluation kits is used to validate firmware on real hardware before it ships.
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: Lemberg Solutions vs Very
| Capability | Lemberg Solutions | 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: Lemberg Solutions vs Very
| Framework / platform | Lemberg Solutions | Very |
|---|---|---|
| FreeRTOS | ✓ | N/A |
| Zephyr | ✓ | N/A |
| Embedded Linux | ✓ | ✓ |
| Yocto | N/A | N/A |
| AUTOSAR | N/A | N/A |
| STM32 | ✓ | N/A |
| Nordic | ✓ | ✓ |
| NXP | ✓ | N/A |
| FPGA | N/A | N/A |
Pricing comparison: Lemberg Solutions vs Very
| Criterion | Lemberg Solutions | Very |
|---|---|---|
| Minimum engagement | Not disclosed | Not disclosed |
| Engagement models | Consulting, Dedicated team, Fixed project, Time & materials | Fixed project, Time & materials |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: Lemberg Solutions vs Very
| Dimension | Lemberg Solutions | Very |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Medical devices, Automotive, Energy & EV charging | Industrial IoT, Consumer electronics, Energy & EV charging |
| Best use cases | Porting medical-device firmware to a new STM32 family while keeping power consumption down, Auditing and refactoring unstable connectivity firmware on ESP32 or Nordic parts | Taking a first IoT product from concept to pilot, Building Nerves-based device software on embedded Linux |
| Typical project type | Consulting | Fixed project |
Lemberg Solutions vs Very: pros and cons
| Lemberg Solutions | |
|---|---|
| + | One team covers schematics, PCB layout, MCU firmware, cloud back end and the companion app, so integration problems surface inside a single project plan |
| + | ISO 27001 and ISO 9001 certified, with secure boot, image signing and OTA rollback offered as standard firmware work items |
| + | Partner status with NXP, Microchip and STMicroelectronics gives earlier access to silicon support and reference designs |
| + | Edge AI experience runs from sensor integration and DSP to on-device inference and computer vision |
| + | In-house lab lets the team validate firmware against real boards and RF conditions before the client receives a build |
| + | All intellectual property rights transfer to the client, across consulting, team-extension and full-product engagements |
| - | Mass production is not handled in-house; the team supports a product through development and maintenance but does not manufacture finished devices |
| - | Regulatory certification is not obtained on the client's behalf; Lemberg supplies the technical documentation and engineering support for approvals |
| - | Broad scope means a buyer who only needs a single low-level driver may be paying for capabilities they will not use |
| 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 Lemberg Solutions?
A typical fit: porting medical-device firmware to a new STM32 family while keeping power consumption down.
Electrical engineering, firmware, cloud and an in-house hardware lab under one contract, with NXP, Microchip and ST partner status. Minimum engagement is not publicly disclosed. Works best with clients in Medical devices, Automotive, Energy & EV charging, Logistics & transportation, Industrial IoT, Consumer electronics.
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: Lemberg Solutions vs Very
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | Lemberg Solutions |
| You need a large dedicated team for an ongoing programme | Lemberg Solutions |
| Your budget is at the lower end | Compare: Lemberg Solutions (Not disclosed) vs Very (Not disclosed) |
| You need specialist depth in a specific vertical | Lemberg Solutions |
| You need engineers to extend your own firmware team | Lemberg Solutions |
| You need consulting before committing to a build | Lemberg Solutions |
Use case fit: Lemberg Solutions vs Very
| Use case | Lemberg Solutions fit | Very fit | Winner |
|---|---|---|---|
| Porting medical-device firmware to a new STM32 family while keeping power consumption down | Strong | Limited | Lemberg Solutions |
| Auditing and refactoring unstable connectivity firmware on ESP32 or Nordic parts | Strong | Limited | Lemberg Solutions |
| 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: Lemberg Solutions vs Very
Lemberg Solutions (4.8/5) is the stronger overall choice for most Firmware Development projects. Electrical engineering, firmware, cloud and an in-house hardware lab under one contract, with NXP, Microchip and ST partner status.
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
Lemberg Solutions vs Very FAQ
Is Lemberg Solutions better than Very?
Lemberg Solutions (4.8/5) scores higher overall, but "better" depends on your use case. Lemberg Solutions's strongest advantage: one team covers schematics, PCB layout, MCU firmware, cloud back end and the companion app, so integration problems surface inside a single project plan. Very's strongest advantage: combines product strategy, design and engineering for teams new to hardware.
How do Lemberg Solutions and Very differ in pricing?
Lemberg Solutions uses fixed project, time & materials, dedicated team 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: Lemberg Solutions 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 Lemberg Solutions and Very?
Lemberg Solutions's primary differentiator is: electrical engineering, firmware, cloud and an in-house hardware lab under one contract, with NXP, Microchip and ST partner status. Very's primary differentiator is: product-strategy-led IoT development with Nerves and Elixir experience. They also differ in team size (200+ vs 51–200), minimum engagement (Not disclosed vs Not disclosed), and primary industries served (Medical devices, Automotive vs Industrial IoT, Consumer electronics).
Verify all details directly with each service provider before making a decision.