Firmware Development Services
Firmware for connected devices that has to run for years: microcontroller and embedded Linux firmware, secure boot, signed over-the-air updates and tested releases. From the team behind LaMetric, with ~75,000 devices online and 250 OTA releases shipped to our own fleet.
OTA releases shipped to our own fleet
Devices online
Fleet monitoring and support
Countries our devices ship to
The problem
Firmware often grows without structure. It is hard to test, hard to update and fragile in the field, so customers find the bugs instead of the tests. Fixing that after launch costs far more than designing for it.
Untested code
Bugs reach customers because nothing tests the firmware on real hardware before release.
No safe update path
Devices in the field can't be fixed without a site visit, and every update risks bricking a device.
Security and the EU CRA
Unsigned software, keys on laptops and missing updates are now a market-access problem under the Cyber Resilience Act.
Power, timing and boot time
Battery life, real-time behaviour and boot time miss the target, and customers notice.
What we do
Firmware you can test, update and maintain for the life of the product, from the first architecture decision to signed releases in the field.
Firmware architecture
RTOS (FreeRTOS, Zephyr), bare-metal or embedded Linux structure, drivers and the update path designed together, so the firmware stays testable and maintainable as features grow.
MCU firmware development
Firmware for microcontrollers on platforms we work with, such as NXP, ST and Nordic: drivers for sensors, radios and peripherals, low-power and real-time optimisation, and a bootloader that supports secure updates. Built with tests from day one.
Embedded Linux, BSP and drivers
Board bring-up, U-Boot, kernel drivers and device tree, and reproducible Yocto or Buildroot images. Boot time, power and memory optimised: on an industrial HMI we cut boot time from 55–60 s to 10 s.
Connectivity and cloud integration
Wi-Fi, BLE, LTE-M/NB-IoT and Ethernet; MQTT and HTTPS; offline buffering and store-and-forward; industrial and energy protocols such as Modbus, CAN and BACnet.
Secure boot and key management
A chain of trust from ROM to application, a signing infrastructure that keeps keys off developer laptops, encrypted storage and secrets handling, with TPM 2.0 where the hardware has it.
OTA updates that never brick a device
A/B or recovery-based updates, signed and encrypted images, automatic rollback on failed boot, delta updates for constrained links, MCU and co-processor updates, and staged rollouts with Mender, RAUC or SWUpdate.
Testing, CI and releases
Unit and hardware-in-the-loop tests on every change, reproducible builds and signed release automation in GitHub Actions, GitLab CI or Jenkins, with quality gates before anything reaches the fleet.
MCU and SoC migration
A new microcontroller, SoC or system-on-module because of cost, end-of-life or performance: target selection, BSP and driver porting, an update path from old to new hardware, and requalification.
Compliance and documentation
Firmware ready for the EU Cyber Resilience Act: SBOM, vulnerability handling and security updates over the product's life, plus support for CE, RED and FCC with pre-compliance testing and technical documentation.
Edge AI firmware
Camera and image pipelines, model optimisation and quantisation, on-device inference with TensorFlow Lite or OpenCV, and model delivery via OTA.
Firmware for energy and charging devices
EV chargers with OCPP, inverters and PV monitoring with SunSpec and Modbus, HEMS and EMS controllers with EEBUS: firmware, connectivity, OTA and production test for energy devices.
Our Engineering Process
Firmware built to be tested, updated and maintained.
1. Requirements
2. Architecture
3. Implementation
4. Testing and CI
5. Release and support
Case studies
Related accelerators
Planning something similar?
Tell us where you are. A senior engineer replies within one business day.
Related services
FAQ
What does a firmware development service include?
What is the difference between firmware and embedded software?
Do you work with an RTOS or bare-metal?
Which microcontrollers do you work with?
Can you take over existing firmware?
How do you make firmware updates safe?
Can OTA be added to devices already in the field?
How do you test firmware?
Do you develop firmware for EV chargers, inverters and energy managers?
Does firmware have to comply with the Cyber Resilience Act?
Can you migrate our firmware to a new microcontroller or SoC?
Who owns the code?
Can we start with one phase?
Talk to an engineer, not a salesperson
Idea, prototype, production or a fleet in the field: tell us where you are. A senior engineer replies within one business day.
Your benefits:
- Senior embedded engineers
- Hardware, firmware and cloud
- From prototype to fleet
- Clear scope and next steps
- Direct technical answers
- No sales pitch
What happens next?
A free 30-minute call with a senior engineer
A short technical discovery
A proposal with scope, timeline and cost























































