Architecture audit · Embedded · Automotive · Healthcare
We find architecture risks in embedded products before production, a certification body or a recall does. A fixed-price audit with a prioritised action plan in 2–3 weeks.
No rollback after a failed update
Fix: A/B partitions, signature check and automatic rollback.
What we do
2–3 weeks. Findings ranked Critical to Minor, as-is and to-be diagrams, and an action plan your team can start on Monday.
02
From concept to HLD and DLD: hardware/software split, protocols, update strategy and security. We lead the design or join your team.
03
Unattended test rigs, simulators and emulated hardware, so development and regression testing never wait for the board.
04
One team from idea to series production: architecture, firmware, client apps and back end, test rigs and support through certification. One contract, one owner of the result.
05
Outstaff: our engineers join your team and work in your process and tools. Outsource: we take an agreed scope and deliver it with our own lead. Embedded, QA and architecture.
06
Firmware for microcontrollers and embedded Linux, desktop, mobile and web apps that work with the device, and the manual and automated testing that proves they do.
Expertise
Firmware architecture that fits memory, power and deadlines.
Architecture for systems where failure is an incident, not a bug.
IEC 62304-ready architecture before the audit, not after.
Updates that never brick the device. CRA and UN R156 ready.
Reliable links from profile to production line.
Tests that run all night without a human.
Development doesn’t wait for hardware.
How an audit works
30 minutes with an architect, free. We agree scope, standards and a fixed price.
NDA first. Then code, documentation and short interviews with your team.
2–3 weeks against your standards: IEC 62304, ISO 26262, UN R155/R156, CRA.
Findings, diagrams and a prioritised plan, walked through live with your engineers.
What we see. The image is written over the running partition with no A/B scheme.
Why it matters. A power loss during the write leaves the device unbootable in the field.
What to do. A/B partitions, signature verification and automatic rollback.
An illustrative finding from a sample report.
EU Cyber Resilience Act
Vulnerability reporting has applied since 11 September 2026, including for products already on the market. Full requirements and CE marking follow on 11 December 2027. Fines go up to €15M or 2.5% of worldwide turnover.
Case studies
Rail · UK
Software architecture on QNX 8 with CAN optimisation, on-train integration and hardware simulation. About 40% higher reliability and performance than comparable existing products.
Healthcare · US
Device architecture tracking tools, cycles, physicians and detergents, with secure FOTA and automatic ordering of consumables.
Medical device · US
Embedded software for a device in IEC 62304 class C, plus an automated test framework built on the V8 engine with simulated BLE chips.
Products
Contact
An architect replies within one business day. We sign an NDA before we see any code.
