What we build with
The stack, and what it means
for the person paying for it.
One page per technology we actually build on, written for the person paying for it rather than for the person typing. Each says what the technology does for your business, what it costs you in the long run, and the cases where it is the wrong answer — including when the right answer is rescuing what you already have rather than replacing it. Nothing is listed here that we do not genuinely build on.
- Next.js →Server-rendered React, instant rollback, no plugin stack to patch.
- Supabase and Postgres →Access enforced at the database, private storage, migrations you can prove were applied.
- Stripe →Server-side re-pricing, webhooks as the only writer of paid orders, Apple Pay, and Connect.
- React Native and Expo →Cross-platform apps in one codebase, and an honest answer about whether you need one.
- AI integration →AI on the reading order, not the decision, with every call’s cost logged.
- Rescuing an existing system →Taking over a site or platform somebody else built, and what we check first.
Questions
Why this matters to you.
Why should I care what my site is built on?
Because it decides three things you will feel: how fast it is, who else can work on it, and what happens if we part company. Google’s own target is a Largest Contentful Paint of 2.5 seconds or less for three quarters of page loads, and the stack is most of what decides whether you hit it.
Am I locked in to your choices?
No. Everything here is open technology running on infrastructure in your own accounts where possible, so the code, the data and the hosting are transferable. That is the practical difference between a built system and a white-label platform, and it is worth checking in any contract rather than assuming it.
Can you work on something somebody else built?
Often, yes. That is what the rescue page is for: taking over a system that works but cannot be changed, or one that has been abandoned by whoever built it. We will say plainly when a rebuild is cheaper than a rescue, because sometimes it is.
Got an existing stack?
Tell us what you are on now and we will tell you whether it should be kept, upgraded or replaced.
Start a project →