18 platforms · 13 full write-ups
Introduction
The stack we build large, multi-brand sites on — and the reasoning behind it.
A curated, opinionated reference for a serious rebuild: CMS, framework, hosting, and the integrations that tie it into your estate. Not a directory of everything that exists — the set we actually evaluate, recommend and ship, grouped by the decision each layer answers.
If we started your rebuild today.
CMS
Sanity or Storyblok
Sanity when content is product-like and developers shape the editing experience; Storyblok when marketing wants visual editing and locale autonomy. Contentful when procurement wants the market incumbent.
Hosting
Vercel — or your cloud
Preview deployments and edge delivery for most estates. Your own AWS, Azure, GCP or CDN contract when data residency or procurement says so — that path is first-class, not a compromise.
Integrations
Keep what you run
CRM, PIM, analytics, SSO and internal APIs stay; the stack connects to them. Nothing here is rip-and-replace.
Exclusive with none
Right when the estate grew by accretion, navigation and search underperform, or this budget won’t come around again soon.
Paid for work, not referrals
Our revenue is building and running your estate. The platform choice is your cost, not our income.
“Stay” is a possible verdict
Every migrate-from page includes the case for staying. If the honest answer is keep your platform, that's the answer you get.
Arriving with a legacy platform?
Start from our stay-or-migrate take on the one you're holding:
6 platforms · 10 full write-ups
Not sure which fits?
Get a reasoned recommendation, not a ranking.
In the audit we map your estate, model the cost of staying versus moving, and document the recommendation — so you can defend the choice internally, in writing.