Skip to content

Introduction

The stack we build on, and the reasoning behind it.

A curated, opinionated reference: CMS, framework, hosting, and the integrations that tie it into your business. Not a directory of everything that exists, and vendor-agnostic by design. This is the set we actually evaluate, recommend and ship, grouped by the decision each layer answers.

If we started your build today.

CMS

Sanity or Storyblok

Sanity when the content model is unusual and the editing experience has to bend around it. Storyblok when marketing wants visual editing without giving up structure underneath.

Framework

Astro

For content-heavy sites it ships almost no JavaScript, so the performance budget holds after launch rather than just at it. Next.js when the surface is app-like: dashboards, logged-in product, heavy interactivity.

Hosting & Infrastructure

Vercel, or your cloud

Preview deployments and edge delivery suit most builds. Your own AWS, Azure or GCP contract when data residency or procurement says so. That path is first-class, not a compromise.

Integrations

Keep what you run

CRM, analytics, billing and internal APIs stay; the stack connects to them. Nothing here is rip-and-replace for its own sake.

  • Exclusive with none

    We hold no vendor partnership that pays us to recommend one platform over another.

  • Paid for work, not referrals

    Our revenue is building and running what we ship. The platform choice is your cost, not our income.

  • "Keep what you have" is a real answer

    If the honest answer is that your current stack is fine, that is the answer you get.

CMS

Where does content live, and can the team actually run it?

(1–3)

  • Sanity: The one to reach for when the content model is unusual and the editing experience has to bend around it.
  • Storyblok: The compromise that actually works when marketers want visual editing and developers want structure.
  • Contentful: The one procurement is most comfortable with, and the one that handles multi-market governance best.

3 platforms covered

Framework

What do we build the front end with?

(1–3)

  • Astro: Our default for content-heavy marketing sites, because the fast path is also the default path.
  • Next.js: The right answer when the marketing site and the product application are genuinely the same codebase.
  • Astro vs Next.js: The short version: Astro for content, Next.js for applications. The long version is below.

3 platforms covered

Hosting & Infrastructure

Where does it run, including your own cloud?

(1–2)

  • Vercel: Our default host, largely because preview deployments change how review conversations happen.
  • Cloudflare: The one to look at when bandwidth is the line item that keeps surprising you.

2 platforms covered

Integrations

How does it connect to the tools you already use?

(1–1)

  • Supabase: What we reach for when a marketing site grows a feature that genuinely needs a database.

1 platform covered

Not sure which fits?

Get a reasoned recommendation, not a ranking.

On a discovery call we map what you already run, work out what it is costing you in time, and put the recommendation in writing, so you can defend the choice internally.

Talk to Us