Home / Capabilities / Embedded & IoT
Hardware and firmware for products that have to work unattended, in a cabinet or on a wall, for ten years — and still accept an update on the last day.
Embedded work is judged on what happens after the demo. A product that behaves on a bench and fails in a plant room with a marginal radio link, brownouts and a firmware version nobody can reproduce is a warranty problem, not a product.
We design for that second phase from the start. That means an update mechanism before the first field trial, identity and keys decided while the schematic is still open, and a build system that a new engineer can run on their first morning.
We work from an idea on a whiteboard, from a reference design you want productionised, or from firmware you inherited and can no longer build.
Services
Schematic capture, PCB layout, component selection with supply‑chain reality in mind, prototype bring‑up and design for manufacture.
Bare metal and RTOS firmware where every microamp counts, or embedded Linux where the product needs a filesystem, containers and a real network stack.
Choosing the right link for the site rather than the most interesting one, then making it reliable when the site is concrete, noisy and already full of other equipment.
Device identity and update paths designed together, because an update mechanism without authentication is a way to lose an entire fleet at once.
Questions we get asked
Yes, and it is a large part of what we do. The first phase is always the same: get it building reproducibly from a clean checkout, put it under version control and CI, write down what it actually does, and only then change behaviour.
Often not. A gateway or an add‑on module can bring an existing product online without touching the certified design. We will tell you honestly when a respin is the cheaper path over the product's life.
You do — schematics, layout, firmware and toolchain configuration. They live in your repository and your accounts throughout, not just at handover.
We design for it and prepare the technical documentation, run pre‑compliance where it is useful, and work with your chosen test house through the formal process.
Send the product brief or the existing design files. We will come back with an approach and the questions that decide the cost.