The platforms we build on — and why we choose them.
A curated, opinionated reference: the CMS, framework, hosting and integrations we actually evaluate, recommend and ship. Not a directory of everything that exists — vendor-agnostic by design, grouped by the decision each layer answers.
CMS
Where your content lives — and who can actually run it.
The CMS decides who can update the site, how content is structured, and how easily it feeds everything else you run. We build on a small, opinionated set — chosen by the job in front of us, not by habit.
Framework
What we build the front end with.
The framework sets the performance budget and the ceiling for what the front end can do. We build app-like surfaces in Next.js and content-first sites in Astro — the right tool for the shape of the job.
Hosting
Where it runs — managed by us, or your own cloud.
Hosting is where performance, security and reliability are won or lost. We run managed environments and VPS boxes ourselves, and deploy to edge platforms like Vercel and Cloudflare — or your own cloud when procurement says so.
Commerce
What powers the store — hosted or fully your own.
The commerce engine decides how you sell: how the checkout converts, how much of the infrastructure you own, and how deeply the store weaves into your content. We build on two, chosen by how much control versus convenience a business wants.
Integrations
How it connects to everything else you run.
A website is rarely an island. We connect the systems you already run — analytics, CRMs, databases, payments, internal APIs and more — so the site works with your estate rather than beside it. Nothing here is rip-and-replace.
Not sure which stack fits?
Tell us about the build and we will recommend the platforms — a reasoned recommendation, not a ranking. No jargon, no lock-in.
