SAP to open-stack ERP migration
Manufacturer, 500+ employees. Phased migration off SAP ERP onto an open stack with custom modules — run in stages while the plant kept working.
- 0 downtime
- 8 mo migration
- −40% on licences
Embedded software for devices that ship and then have to be updated
Code that works on the bench is a solved problem. Software you can update safely on ten thousand devices in the field, over a network that keeps dropping, is the actual job.
What we can show you
Embedded software
What we take, and what your hardware partner takes
We own the software side of the device and everything above it. Schematics, RTOS firmware and certification stay with your hardware people.
Firmware development services in a partner model — stated plainly
Device projects have two halves. The hardware half — board design, component choice, bare-metal and RTOS firmware, EMC testing, CE and FCC certification, manufacturing — belongs to your hardware team, ODM or a specialist partner. We do not design boards and we do not certify devices; claiming otherwise would waste a month of your time before anyone noticed.
The software half is ours: the device agent on embedded Linux, protocol work and the gateway that normalises what the hardware speaks, the over-the-air update mechanics and rollout server, the health telemetry, the test bench that exercises a real device automatically, and the integration into your platform and business systems.
When this split works — and when it does not
It works when the device exists or has a hardware owner, and the gap is everything between the sensor and the business system. It does not work when what you actually need is a firmware house for a bare-metal microcontroller: then you need that partner first, and we will say so on the first call rather than take the scoping fee.
Signals the device software needs work
- the prototype works but there is no way to update it in the field;
- a device «hangs about once a week» and nobody can say why;
- data from the device is needed in an ERP or a billing system;
- testing means one engineer, one device and a desk;
- firmware exists, but nothing above it does.
Price
Scoping $4,490, builds from $18,900
Timeline
Scoping in 1 week
Payment
50/50 by milestone
Comparison
Bare-metal, RTOS or embedded Linux
The choice decides who does the work, what it costs to maintain and whether over-the-air updates are realistic at all.
Criterion
Bare-metal / RTOSEmbedded Linux
Embedded LinuxBare-metal or RTOS
Typical hardware cost
Lowest
Higher: more memory and storage
Power consumption
Best
Worse — matters on battery devices
Networking, TLS, filesystem
Hand-built, painful
Standard, maintained upstream
Over-the-air updates
Custom bootloader work
A/B partitions, a solved problem
Who writes it
Your hardware partner or firmware house
Us
When it wins
Simple, battery-powered, deterministic devices
Connected devices that must be updated and integrated
Process
Updates and the test bench: the two things that decide the second year
A fleet you cannot update is a fleet you will replace by hand — and a device tested only on one desk fails in ways nobody predicted.
Over-the-air updates, done safely
Signed images so a device only accepts what you built. A/B partitions so a failed update falls back instead of bricking. Staged rollouts so a bad build reaches ten devices, not ten thousand. Health checks that decide whether an update is confirmed or rolled back.
Adding this to a device already in the field is sometimes impossible — it depends on flash layout and bootloader, and the scoping week answers it definitively.
A test bench, not a desk
Real hardware wired into CI where the device can be power-cycled, starved of network and fed malformed data automatically on every build.
Protocol logic is additionally simulated, so most regressions are caught before they reach the bench queue.
The gateway and the protocol layer
Whatever the hardware speaks — Modbus, CAN, a vendor serial protocol — gets normalised in one place, with a schema and versioning, so the platform above never learns firmware quirks.
Buffering and store-and-forward belong here too: connectivity in warehouses, basements and vehicles is intermittent by nature.
Integration upwards
Health telemetry, provisioning and the path into your platform and business systems — see IoT software development and API and integration.
Sources, toolchain configuration and build scripts are yours, with IP assigned at delivery.
Why us
Why this split is worth having
Four things we can prove, rather than four adjectives.
We name what we do not do
No board design, no RTOS firmware on our own, no certification. A vendor that claims all of it is either very large or about to learn on your project.
Updates designed before the fleet ships
Signed images, A/B partitions, staged rollout and rollback. Retrofitting this into deployed devices is the most expensive mistake in the category.
Hardware costs at cost
Devices, lab time and certification are paid to your partner directly. Our discount applies to engineering, never to hardware you would buy anyway.
Your sources, your toolchain
Code, build scripts and toolchain configuration live in your repository, with IP assigned at delivery and a documented chain of title.
Industries
Device softwareby industry
Connected devices land where physical work happens: fleets and cold chain in logistics, lines and meters in manufacturing, access and utilities in property.
- IT companies and digital agencies
- Insurers and brokers
- Lenders and microfinance
- E-commerce
- Wholesale and distribution
- Manufacturing
- Freight and forwarding
- Clinics and medical centres
- Dental
- Car dealers and service centres
- EdTech
- Legal and consulting firms
- Equipment rental
- Real estate agencies
- Property developers
- Travel and events
- Beauty and wellness
- Construction and renovation
FAQ
Embedded and firmware questions
Six answers that usually replace a discovery call.
Do you design hardware?
No — and that is what separates us from a full-stack embedded software development company. Schematics, PCB, enclosures, EMC and certification stay with your hardware partner or ODM; we take the software side of the device and everything above it.
Which platforms do you work on directly?
Embedded Linux device agents, gateways and protocol work. Bare-metal and RTOS firmware we take only alongside your embedded engineer or hardware partner — that is a deliberate limit, not a sales position.
Bare-metal, RTOS or embedded Linux?
Bare-metal for simple deterministic devices, RTOS when several responsibilities run concurrently, embedded Linux when you need networking, TLS and safe updates. The choice also decides who writes it.
Can you add over-the-air updates to a device already in the field?
Sometimes — it depends on flash layout and bootloader. The scoping week gives a definitive answer instead of a hopeful one.
How do you test device software?
A hardware-in-the-loop bench in CI where a real device is power-cycled, starved of network and fed malformed data on every build, plus simulation for protocol logic.
Who owns the code?
You: sources, toolchain configuration and build scripts, with IP assigned at delivery and a documented chain of title.
2–4×
faster on the code-writing share
in 3 weeks
from idea to MVP
230+
projects delivered
17 years
of engineering experience
Work
Work we can show you
SMARTWILL
Digital inheritance service (Web3)
AIRDEVELOPPA
Indoor air quality finder driven by sensor data
CAR5
Car-sharing app
APP.DENTAL
Cloud CRM for dental clinics
NEXORA
Warehouse and logistics management platform
As-built docs
Digital as-built documentation
EX211
Telegram Mini App for currency exchange
SMARTWILL
Digital inheritance service (Web3)
Have a device and nothing above it?
Tell us what the hardware is, who owns it and what has to reach your systems. You get an architecture for the software side, an honest split with your hardware partner and a fixed quote for scoping.