Embedded firmware engineering

Firmware that makes your hardware shine.

We write firmware for devices that have to keep working, whether it’s your first prototype or a product that’s already out in the field. We’re based in the Eindhoven region.

Don’t have a board yet? We can design that too, so you work with one engineer from the first schematic to the updates in the field.

Let’s make it work right
The problem

You’ve built great hardware.

But when it freezes, misbehaves, or just won’t talk to other devices, people assume the whole thing is bad. We get it. Debugging firmware under pressure isn’t fun, and those little issues can make or break your product’s reputation.

We make sure the firmware does your hardware justice.
The approach

We bring the same care to your firmware that you bring to your hardware.

Design

Before we write any code, we agree on how it should work and what happens when things go wrong.

Test

Every change gets tested automatically, on a PC and on the real hardware.

Refine

We measure memory, power and timing, and fix what the numbers show.

Case studies

Recent work

Self-service kiosks · Raspberry Pi

Field updates that can’t brick a device

  • 18 releases
  • A/B rollback
  • Watchdog recovery
Challenge
A fleet of Raspberry Pi kiosks needed remote updates and provisioning, with nobody on site to recover a device when an update goes wrong.
What we did
We built the loader that looks after the kiosk software. It keeps two app slots and rolls back on its own when a new version keeps failing. Around it there’s a 21-step provisioning script you can safely run again, a systemd watchdog, and a Jenkins and Docker pipeline that checks every release before it goes out.
Result
18 releases in 18 months, all rolled out remotely. If one fails, the kiosk rolls itself back.
Open source · Rust

A TFTP server automotive engineers build on

  • 220k+ downloads
  • In NixOS & openSUSE
  • 33 merged community PRs
Challenge
Netbooting with U-Boot and flashing boards needs a small TFTP server and client you can rely on, running on any machine in the lab.
What we did
We wrote rs-tftpd from scratch in pure Rust, with a matching client and support for the RFC 2347–2349 and 7440 options, and we maintain it as an open-source project.
Result
It’s packaged for NixOS and openSUSE, and engineers from Renault Software Labs, Ampere and Nokia have contributed to it. Renault uses the client as a library, and its duplicate-packets option cut an Apache NuttX network boot from 4 minutes to 20 seconds.
View on GitHub →
Cyber Resilience Act

The CRA is already here.

If you sell connected devices in the EU, exploited vulnerabilities now have to be reported within 24 hours. From December 2027 your products also need secure updates, an SBOM and a few other things. It sounds like a lot, but most of the work lands on the firmware, and that’s where we can help.

The self-check is fifteen questions, and your answers never leave your browser.

Clients

Trusted by teams who build things that matter.

Altuğ Bakan
About

Hey, I’m Altuğ.

I’ve spent years working on embedded systems in industries where failure isn’t an option. These days, I help companies turn hardware ideas into dependable products, without chasing firmware bugs at midnight. I’ve also written for Elektor magazine.

Process

Here’s how we usually work:

  1. 01

    Chat

    A quick call to understand your product and goals.

  2. 02

    Plan or audit

    A clear roadmap or a report for your existing code.

  3. 03

    Agree

    Agree on an actionable and fully transparent plan.

  4. 04

    Build

    Development and testing until it’s ready for production.

Simple, transparent, and built around your timeline.

Contact

Let’s talk about your device.

Whether you’re launching something new or fixing what’s already in the field, we’d like to hear what you’re building.

Start a conversation