Web applications. Software for messy data with real consequences.
how I work
I build the architecture underneath, not just the screens on top. One person across the whole stack, so nothing is lost in the handover.
From the schema up to the screens people use.
Every project follows the same path. Scope first, data second, and nothing built before both are understood.

01
Scope
What the product has to do, who uses it, and what it has to integrate with. We agree on it before anything is built.
02
Data review
A real sample of the data, and an honest read on the state of it. The work underneath is visible before it is quoted.
03
Build
Architecture and interface built together, in working increments you can use. Something real early, refined from there.
04
Handover
Deployment, documentation and monitoring that runs without me. You own the product.
The stack. Picked per project, for the data and the budget.
Front end
- TypeScriptAcross the whole stack, so the data model has one shape end to end.
- React and AstroReact for application screens, Astro for fast content sites.
Backend and data
- Supabase and PostgresDatabase, auth, row-level security and APIs.
- Cloudflare D1SQLite at the edge, for lighter data that sits close to the user.
Hosting
- Cloudflare WorkersAPIs and server logic at the edge, with no servers to run.
- DigitalOceanServers for long-running jobs, pipelines and anything that needs a box.
Work with me
Start the conversation
Send the project, a link to anything already built,
and a sample of the data if you have one.
and a sample of the data if you have one.


