Software built to be maintained, not just launched.
Mobile and web, built from scratch by the people who spend the rest of their time fixing what other teams shipped.
We see how software fails
A lot of our work has been repairing applications somebody else built, which means we've spent a lot of time inside the decisions that turn into somebody's emergency two years later. That is an unusual thing to bring to a new build, and it is the reason we argue about state management and release process before anybody writes a screen.
What we build
iOS and Android
React Native and Expo: one codebase, native performance, and a release process that does not depend on one person knowing the incantation.
Web platforms
Next.js and TypeScript, typed end to end and deployed on Vercel, so the thing that breaks in production is the thing you changed.
Backends and data
Supabase, PostgreSQL and Firebase, with the row-level security written and tested rather than assumed, and Stripe where money is involved.
Hardware companions
The app beside the device. Connectivity, pairing, firmware handoff and the state problems that only appear on a real unit in a real room.
- React Native
- Expo
- Next.js
- TypeScript
- Supabase
- PostgreSQL
- Firebase
- Stripe
- Vercel
- Claude
You own what we build
The repository, the infrastructure accounts and the deployment pipeline are yours from the first commit. Nothing is hosted on our account, and nothing requires us to stay for you to keep shipping.
Tell us what you are building
Send us the shape of it and we will come back with what we would do, what we would question, and what it would take.