The program that makes your device measure, report and last

A sensor that runs out of battery in a month, loses its connection or has to be updated in person is expensive. I write firmware so your device does its job without you having to babysit it.

Tell me about your project See projects
Outdoor sensor enclosure installed on a facade

What I work with

  • ESP32 · Espressif
  • PlatformIO
  • C / C++
  • MQTT
  • LoRaWAN · The Things Network
  • Arduino

What I do

01

ESP32 firmware

From reading the sensor to deciding what to do with the data, on ESP-IDF or an RTOS as the project requires.

02

Connectivity

LoRaWAN, MQTT or cellular. We decide with numbers, not by habit.

03

Batteries that last

I measure real consumption and tune sleep modes so a battery or a solar panel goes a long way.

04

Remote updates

To fix or improve without travelling to every device.

05

No cloud dependency

If your installation cannot go dark when the internet fails, it runs locally.

Animation: a sensor sends its reading over LoRa to a gateway, the bits travel across the internet to a server that decodes them, and the data ends up on a dashboard with charts and an alert

The journey of a data point

A sensor reads 23.4 °C in the middle of a field. Within a couple of seconds that number crosses kilometres by radio, travels encrypted over the internet, gets decoded and shows up on your dashboard. And if something goes out of range, you're the first to know.

  • LoRaWAN when you need long range on a battery
  • Encrypted MQTT to talk to your systems
  • Dashboards and alerts that warn you before things fail

Real work

Solar street lights reporting battery and status over LoRaWAN Solar street lights reporting battery and status over LoRaWAN See the project → Pool control that works without depending on the internet Pool control that works without depending on the internet See the project →

How we work

Four steps and no surprises: at every point you know what comes next, what you get and what it costs.

  1. Let's talk

    You tell me what you need, what you already have and what worries you. No commitment, no jargon.

    You get: An honest view on whether it is feasible and where I would start.

  2. I propose a plan

    In writing: what I will do, what you get, in what order and what it costs. Before starting.

    You get: A fixed proposal with scope, phases and price.

  3. We move in milestones

    You see and test partial deliveries. No black boxes opened at the end.

    You get: Prototypes and versions you can hold and test.

  4. I leave it running

    Files, documentation and support during commissioning. And I am still around afterwards.

    You get: Source files, documentation and someone to call.

Start with step 1 →

Questions I often get

Do you only work with ESP32?

It is what I use most because it fits many projects, but yours decides: power, range, cost and availability.

LoRaWAN or cellular?

It depends on distance, how much data it sends and coverage. We look at it in the first conversation.

Can you take over firmware someone else started?

Yes. I review it first and tell you what is worth keeping and what should be rewritten.

Shall we talk?

Tell me where you are and what worries you. You will hear back from me, not from an automated form, with how I would approach it and, if it fits, a fixed quote.

Tell me about your project See projects

I can also help with