Custom Linux images. Devices onboarded to AWS IoT.
We build the OS image your industrial PC or gateway actually ships — hardened, reproducible, maintainable for a decade — then get the fleet onto AWS IoT with per-device identities and an update path that keeps it patched. On your hardware, or hardware we source for you.
The platform
You build the application. We deliver the platform.
An industrial device ships for ten years, sits somewhere nobody wants to drive to, and still has to take a security patch without becoming a support ticket. Getting that right is a different job from building your product — and it's the job we do. Your team stays on the application.
An OS image built for your device
Purpose-built with the Yocto Project and trimmed to exactly what you ship — a hardened, mostly read-only rootfs that shrugs off a power cut, with a reproducible build you can still rerun bit-for-bit in ten years. Tailored Windows images where that's the right answer.
Onboarded to AWS IoT
Every unit gets its own certificate-backed identity and device shadow on AWS IoT Core, with telemetry buffered on-device and flushed when the link returns — so a gateway that drops off a plant network for a day doesn't leave a hole in your data.
Updates you can still ship in year ten
Signed A/B updates with automatic rollback, delta payloads for constrained links, and an SBOM plus CVE tracking behind them — so patching a device in a cabinet on the far side of the country is routine, not a site visit and a held breath.
Zero-touch provisioning at the line
Identities, keys, and first-boot configuration are handled automatically, so a unit comes off the production line and connects itself — no technician, no laptop, no per-device manual step to get wrong a thousand times.
The result: your team ships features, not plumbing.
The engagement
Fixed scope. Fixed price. Eight weeks.
Most embedded platform work is sold by the hour, which means you carry the schedule risk and find out what it costs afterwards. We scope it up front instead: one price, one date, and a defined list of what lands on your board at the end of it.
Weeks 1–2
Board bring-up & base image
A Yocto layer for your board, a kernel config trimmed to what you actually ship, and a minimal mostly read-only root filesystem. The build is reproducible and running in CI before we go further.
Weeks 3–4
Secure boot & root of trust
A verified chain from power-on to userspace — signed U-Boot or UEFI, signed and integrity-checked rootfs, an encrypted data partition, and a key-management scheme where the signing keys are yours, not ours.
Weeks 5–6
Updates and the patch pipeline
A/B updates with automatic rollback via RAUC, delta payloads for constrained links, and writes that are safe against power loss mid-update. Plus an SBOM out of the build and a CVE feed against it, so you know what needs patching before a customer asks.
Weeks 7–8
AWS IoT onboarding & handover
Zero-touch provisioning with per-device certificate identities, onboarding to AWS IoT Core with device shadows and telemetry, one fleet-wide update campaign run end to end, then documentation and a live handover to your team.
What you own on day 57
- Your Yocto meta-layer, in your Git organization
- A reproducible CI pipeline that rebuilds the image from scratch
- A signed boot chain — with your signing keys, held by you
- A/B OTA with automatic rollback and delta updates
- AWS IoT onboarding, provisioning, and a device-shadow schema
- A cross-compiled SDK so your app developers never touch the OS build
- Written documentation and a recorded handover session
Pricing is agreed in writing before work begins, following an initial scoping consultation at no cost. Any material change to scope is requoted and approved by you before it proceeds.
What it doesn't include
Your application
The product logic is yours. We give your developers an SDK and a target that behaves the same on their desk as in the field.
Board design
We bring up and harden the hardware you have — or source and configure something suitable. We don't design PCBs.
Certification testing
We build toward IEC 62443 and CE/EMC requirements and hand you the evidence, but an accredited lab issues the certificate, not us.
Or tell us what you actually need
The package covers the common case. If yours isn't that, the first call is the same free scoping call — we'll tell you what the work is and quote it.
Image customization only
You already have the cloud side handled and just need the OS image done properly — trimmed, hardened, reproducible, and yours to rebuild.
Onboarding an existing fleet
The devices are already shipping. You need them onto AWS IoT with real per-device identities, telemetry, and a way to push updates.
Software help alongside it
Application work, protocol integration, a Yocto build that someone else left broken, or a second opinion before you commit to a board. Tell us the problem and we'll scope it.
After week 8
A device you ship for ten years needs kernel CVE backports, a Yocto LTS migration every couple of years, and someone to run update campaigns when a fix has to reach the whole fleet. That's an ongoing maintenance agreement, priced per year — and it's optional. Everything above is yours whether or not you take it.
Why work with us
An independent partner, not a platform that owns you
We're a hands-on, independent team — not a silicon vendor's sales channel, and not a proprietary platform that locks your product in. That independence is the whole point, and it's what you get when you work with us.
Independent & hardware-agnostic
We build your platform on whatever hardware best fits your application — no silicon-vendor agenda, no pushing a box you don't need. Want it turnkey? We'll source and configure the hardware too.
You own it — no lock-in
Everything we build stands on open-source foundations, with reproducible builds and full documentation. Take it in-house or to another partner whenever you like. Your product is never hostage to our platform.
The OS is our craft, not a sideline
Purpose-built embedded Linux is the hardest layer of an edge product to get right and the one most teams underestimate. It's what we do every day — and the cloud onboarding, OTA, and provisioning around it follow naturally from doing it properly.
You talk to the engineers
You work directly with the engineers who build your platform. The person who scopes the project is the person who delivers it — no account manager relaying requirements, no junior team substituted in after the pitch. Hardware, OS, updates, and cloud are owned by one accountable team.
Hardware
Bring your own board — or let us handle that too
We work on whatever hardware fits your application, including a board you've already committed to. If you'd rather not deal with sourcing at all, we stock and configure these lines and will ship them pre-loaded with your image.
IGT Series — IoT Gateways
ARM-based (TI Sitara AM3352), DIN-rail-mount industrial IoT gateways with isolated DI/O, analog inputs, and cellular/WiFi expansion.
Browse the range →PCIe Expansion Cards
PCIe PoE+ and USB frame grabber cards for powering and connecting machine-vision and surveillance cameras directly from a host PC.
Browse the range →POC Series — Fanless Computers
Ultra-compact fanless embedded and in-vehicle computers for edge gateway, mobile, and space-restricted deployments.
Browse the range →FAQ
Frequently Asked Questions
That's the normal case. We're independent and not tied to any silicon vendor, so bring the board you've already committed to and we build on it. If you haven't chosen yet, we'll help you pick — and source and configure it for you if you'd rather not deal with that at all.
It's a fixed price, quoted after a free scoping call, because the honest answer depends on your board. A mature SoC with a maintained vendor BSP is a very different job from a bare part with a vendor kernel nobody has touched in three years. We tell you which one you have before you commit to anything.
We find that out during scoping, not during week five. If a maintained BSP exists we harden and trim it. If it doesn't, bring-up is real work and we quote it as such — or we tell you the board is a bad bet and suggest one that isn't. Either way you hear it up front.
Yes — completely. The meta-layer lives in your Git organization, the signing keys are generated and held by you, and everything sits on open-source foundations: Yocto, RAUC, U-Boot, AWS IoT. There is no subscription, no per-device runtime fee, and no proprietary layer of ours in the middle of your product.
A reasonable question to ask of anyone entrusted with a ten-year product. Nothing we deliver depends on our continued involvement: it is standard, widely-used open source, held in your repository, with a reproducible build and written documentation — not a bespoke framework that only we understand. Any competent embedded Linux team can take it forward, and we will support that handover if it becomes necessary. Eliminating that dependency is a deliberate design decision.
You can, and we often start from one. But a vendor BSP is a demonstration that the silicon works — it ships with a kernel pinned to whatever was current at tape-out, a writable rootfs, debug access left on, and no update path. Turning that into something you can safely ship, patch, and still build in 2033 is the actual work.
Tell us about your device
What board is it, what does it need to do, and where does it end up? The scoping call is free, and you leave it knowing what the work is and what it costs — whether or not you hire us. We usually reply within one business day.