Engineering, not a deck.
We take a small number of projects at a time and see each one into production. If a piece of work is outside what we do well, we will say so in the first conversation rather than learn it on your budget.
Not a pitch deck — a running portfolio.
Every product below is live, under our own name, with real users on it today. Full case studies — screens, stack and status — are on the Work page.
- Products built and operated
- 29
- Live in production today
- 17
- Android apps on Google Play
- 20
Four disciplines, one delivery team.
The same people design the schema, write the app and own the deploy. Nothing is thrown over a wall, which is why the estimate and the release date tend to agree.
- Product platforms
- Server-rendered Next.js applications with a real data model behind them — roles and permissions, billing, audit trails, background jobs. Built to be handed to a team, not to demo once.
- Next.js · React
- PostgreSQL · Prisma
- Auth · RBAC
- iOS & Android
- Native-feeling apps in React Native and Swift, released through App Store Connect and Google Play. We handle entitlements, store metadata and the release pipeline end to end.
- Expo · Swift · Kotlin
- StoreKit · RevenueCat
- Infrastructure
- Self-hosted deployment, Postgres, TLS, backups and monitoring you can audit.
- Docker · Traefik
- Rescue work
- Inherited codebases made releasable again: test coverage, CI, and a path off the fire.
- Audit · CI/CD
Three ways to start.
- Fixed-scope build
- A defined product with an agreed schema and acceptance criteria. Priced per milestone, paid on delivery of each.
- 4–16 weeks
- Embedded engineering
- We join your team for a period, work in your repository and your process, and leave the codebase in better shape than the brief required.
- Monthly
- Technical audit
- A written assessment of an existing codebase: what is fragile, what it will cost to fix, and the order to do it in. Delivered as a document you own.
- 1–2 weeks
Predictable delivery, not a black box.
- 01
Scope against a schema
Before any interface exists we agree the data model and the permissions on it. Half of what looks like a design argument turns out to be an unresolved question about who owns a record.
- 02
Build in reviewable slices
Work lands as small pull requests against a running deployment. You get a URL in week one and it never stops working — there is no integration phase at the end where things go quiet.
- 03
Prove it, then ship it
A feature is done when a test drives it end to end and someone has exercised it on a real device against real data. A green build alone has never proved an app can open.
- 04
Hand over the keys
Infrastructure as code, documented runbooks, your own accounts. If you want to take the project in-house on day one, nothing about the setup prevents it.
Tell us what is broken
or what should exist.
Send the shape of the problem and any constraints you already know — budget, deadline, the stack you are stuck with. You will get a written reply from the engineer who would do the work, not a sales sequence.