Why we bet on Next.js and Payload

Choosing a stack is choosing a set of constraints you can live with for years. For content-driven products, we keep landing on the same pairing: Next.js on the front, Payload as the CMS, Postgres underneath.

Next.js gives us server rendering and static generation where each makes sense, so pages are fast and search engines are happy. Its App Router lets us stream content and keep JavaScript lean.

Payload gives editors a real admin experience without handing our data to a third party. Because it runs inside the same app and speaks Postgres, there's one codebase, one deploy, and no sync headaches.

The result is a site that scores well on Core Web Vitals and stays genuinely pleasant to edit — which is the combination most teams never quite reach.