Est. in a kitchen, somewhere

Ready to brew?

I brew anything. Including software.

Plainly: WhoBrew builds healthcare software — clinical tools that work with no signal, treat regulated data the way it deserves, and survive contact with a real ward or a real aircraft. Built by someone who works where they get used. Web and hardware projects too, for people I like. The coffee and the beer are just where the name came from.

Coffee

The fuel. Black, unreasonable in volume, and the reason anything ships at all.

Beer

The reward. Cracked open the moment the tests go green, not one commit sooner.

Software

The real work. Things that keep running when the network, the power or the day has gone against you.

What I build

Three kinds of work

Clinical software

Specialism

Offline-first data capture for people who are moving, tired and out of signal. Encryption at rest under hardware-backed keys, sync that reconciles rather than overwrites, and records that hold up when someone asks who wrote what and when.

offline-firstencryption at restconflict resolutionregulated data

Websites that outlive their platform

Web

Static by default, portable by design, quick on a bad connection. Built so you can move hosts in an afternoon and so the thing still loads in four years without anyone maintaining it.

static sitesstripestructured datacore web vitals

Instrumentation

Hardware

Sensors, loggers and telemetry for places with no network and unreliable power — where you get one attempt at capturing the run and the storage has to survive losing power mid-write.

micropythonlorai²c / spitelemetry
Pull up a stool

Let's brew something

A clinical tool that has to work offline, a site that outlives its platform, or a box that logs something nobody is watching. Tell me what it has to survive.

Rather use your own mail app? hello@whobrew.dev

Copied — go on then