Firmware development
Readable, maintainable C and C++ for new products, new features and existing codebases — bare-metal or on an RTOS.
We develop and debug embedded software for product teams — from first board bring-up to firmware you can ship and maintain.
Focused support for teams that need to ship a device, solve a stubborn problem, or add experienced hands without a long hiring cycle.
Readable, maintainable C and C++ for new products, new features and existing codebases — bare-metal or on an RTOS.
Low-level drivers that make sensors, radios and actuators behave — with timing and error handling you can rely on.
We trace faults across hardware and software with a scope, a logic analyzer and a debugger, and hand back findings you can act on.
Firmware that talks reliably to gateways and the cloud — including secure over-the-air updates and device provisioning.
Technology follows the product's requirements — power budget, unit cost, interfaces and who maintains it next — not the other way round.
| Languages | Embedded C, C++, Python for tooling and tests |
|---|---|
| Platforms | ARM Cortex-M (STM32, nRF52/nRF53), ESP32 |
| Runtime | Bare-metal, FreeRTOS, Zephyr |
| Interfaces | UART, SPI, I²C, CAN, BLE, Wi-Fi |
| Verification | Unit tests on host, hardware-in-the-loop, static analysis |
| Delivery | Git, CI builds, code review, written handover |
Edit this table to list only what you actively support.
Short feedback loops and something concrete at every stage — so you always know where the project stands.
Product context, constraints, interfaces, risks and a shared definition of done.
You get: a written scope and estimateThe riskiest assumption is tested first with a small experiment on real hardware.
You get: a go / no-go findingWork lands in visible increments, tested on target and reviewed with your team.
You get: regular builds and demosSource, build instructions, tests and the documentation the next engineer needs.
You get: a project you fully ownPick the model that fits how clear your scope is today. We can switch as the project matures.
When something isn't working and you need to know why.
A fixed-price, short engagement: code or board review, fault analysis, a written report with recommendations.
When the deliverable is clear.
A defined feature, driver or prototype with milestones, acceptance criteria and a firm price.
When you need capacity on an evolving product.
Dedicated engineering time each month, working inside your tools, repo and sprint process.
Representative scenarios. Replace them with real, client-approved case studies as soon as you have them.
First boards are back, nothing talks yet, and the app team is waiting.
Devices freeze every few days and nobody can reproduce it on the bench.
A working device needs telemetry and remote updates without a redesign.
Yes. We're happy to sign your NDA before you share any details, or send ours.
You do. Full source code and intellectual property rights transfer to you on payment, as stated in the contract.
Yes. We work remotely with teams across the EU and beyond, in English. Hardware is shipped to us for testing on target.
Our focus is software. We review schematics from the firmware point of view and work closely with your hardware designer or a partner.
Assessments can usually start within one to two weeks. Larger projects depend on current capacity — we'll give you a concrete date in the first reply.