Embedded & IoT
Embedded firmware for devices that run for years
Firmware for constrained hardware that has to stay connected, stay secure and take updates over the air.
- Product requirements
- Power budget
- Enclosure and BOM limits
- Certification target
- Firmware on RTOS and embedded Linux
- Board bring-up and drivers
- Low-power radio and secure wireless
- Edge AI on microcontrollers
- Secure boot and OTA updates
- Certification support
- Interfaces
- Embedded C
- C++
- RTOS
- Embedded Linux
- MQTT
- Python test rigs
- Applies to
- Battery-powered sensors · Shelf labels and displays · Gateways
- Engagement
- Feasibility & prototype · Production firmware · Sustaining engineering
In plain words
We write the software that runs inside devices and connects them to the internet, so they work reliably for years, often on a battery.
- Who it's for
- Hardware companies, OEMs and teams whose device works on the bench but not yet in the field.
- How to start
- A short feasibility check on your board or idea, then a working prototype.
Words on this page, explained
- Firmware:
- The small program that runs inside a device, like the brain of a shelf label or sensor.
- OTA updates:
- Over-the-air: updating a device's software remotely, without anyone touching it.
- RTOS:
- A tiny operating system for devices that must react instantly and run for years on a battery.
- MQTT:
- A lightweight way for thousands of devices to send small messages to the cloud reliably.
- Edge AI:
- AI that runs on the device or camera itself, so video and data don't have to leave your site.
From board bring-up to fleet management, we build the parts of connected products that are hardest to get right: low-level firmware, power budgets, the radio link, secure boot and OTA. We do this for our own ThingsX shelf labels, which run on a coin cell with a seven-year battery target, and for clients' devices.
Defence & security · sentry alerts
One button. No internet. Command knows at once.
Each sentry carries a small rugged unit with a single button. Press patterns mean different things, and the alert travels over the ordinary cellular network to the command centre, with the post's location.
Perimeter · 6 posts · cellular
Command centre screen
- 22:30All six posts checked in.
What you’re seeing: a guarded compound from above. Choose a post, then press its button once, twice or long. The signal hops to a mobile tower and lands at the command centre in seconds. If a unit stays silent, that missed check-in is an alert too. Based on the system we built for HQ TASA.
For engineers
Rugged handheld with one button, GNSS and a cellular IoT modem (NB-IoT or GSM fallback); press patterns are configured centrally. Messages go over SMS or a lightweight UDP protocol, so no internet or app is needed. The command server tracks a heartbeat per unit and escalates on missed check-ins.
All six posts checked in.
Why teams call us
- 01
Devices that work in the lab and fail in the field
Power budgets, radio coverage, temperature and bad networks break naive designs. We test for the real environment.
- 02
Battery life that misses the spec
We measure current at every state and design firmware around sleep, not around features.
- 03
No safe way to update devices
Secure boot and signed over-the-air updates with rollback come as standard.
How we work
From first workshop to running in production.
- STEP 01
Requirements and power budget
Use cases, environment, certifications, battery and cost targets.
- STEP 02
Hardware and firmware architecture
MCU or SoC selection, radio choice, sensors, memory and security model.
- STEP 03
Bring-up and drivers
Board bring-up, BSPs, drivers and a hardware-in-the-loop test rig.
- STEP 04
Connectivity and cloud
Device provisioning, MQTT/HTTPS messaging, fleet management and dashboards.
- STEP 05
Validation and production
Environmental and soak tests, compliance support, factory test jigs and provisioning.
What you get
Deliverables, not slideware.
- Firmware with OTA
- Signed images, staged rollout and rollback
- Hardware design pack
- Schematics, PCB layout, BOM and manufacturing files
- Factory tooling
- Test jigs, provisioning scripts and serialisation
- Fleet console
- Device health, logs, configuration and alerts
- Power and coverage reports
- Measured, not estimated
Technology
No stack limits. Right tool for the problem.
Firmware
Processors
Embedded Linux
Connectivity
Edge AI
Tooling
Need something not listed? We hire for it or bring in a specialist. The problem picks the stack.
Years on a coin cell
Our shelf labels are designed for multi-year battery life at a daily update
Fleet-wide updates without truck rolls
Signed OTA with staged rollout
Production-ready from the start
Design for test and manufacture built in
Embedded & IoT engineering: common questions
Which chips do you use?
Whatever fits the cost, power and supply targets of your product. We stay vendor-neutral and choose per project.
Do you help with certification?
Yes. We prepare designs and test evidence for the certifications your market needs and work with accredited labs.
Can you take over an existing firmware codebase?
Yes. We start with a code and architecture audit, then stabilise before adding features.
Engagement models
Ways to work with us
Feasibility & prototype
4–8 weeks
Production firmware
to manufacturing release
Sustaining engineering
updates & field support
Where this sits in the stack
Six blocks on one die. One team across all of them.
We work across .NET, C, C++, MFC, Go, Java, Python, Node.js, React and Spark, on GCP, AWS and Azure, plus embedded C on RTOS and embedded Linux. Pick a block to see where it fits.
Hover, tap or tab through the blocks. Lit copper shows which blocks work together.
Block · Firmware
Code that runs on the device itself.
- Embedded C
- C++
- RTOS
- Embedded Linux
- Board bring-up and drivers
- Low-power radio stacks and secure wireless
- Secure boot and over-the-air updates
- Power budgets for coin-cell devices
Where it shows up
- Embedded & IoT (this page)
- Industrial IoT
- Product development
Scope your Embedded & IoT engineering project
Tell us the problem, the constraints and the deadline. A senior engineer replies within one business day.