JAMstack
An architecture pattern that decouples the front-end (pre-rendered markup and JavaScript) from back-end services consumed via APIs, usually hosted on a CDN.
· Reviewed by senior engineers
JAMstack — originally JavaScript, APIs, Markup — is an architecture pattern where the front-end is pre-rendered or statically generated, deployed to a CDN, and talks to back-end functionality through APIs at request time. The site itself has no traditional application server; databases, auth and commerce live behind HTTPS endpoints.
The payoff is performance, security and developer velocity. With static HTML at the edge, time-to-first-byte is measured in tens of milliseconds. There is no application server to patch, no database port exposed to the internet, and the attack surface collapses to whatever APIs you call. Developers ship via git, preview every branch and roll back atomically.
The failure mode is sprawl. A JAMstack site easily ends up calling fifteen SaaS APIs from the browser, each with its own auth, latency and outage profile. The fix is to put a thin server or edge layer in front — Next.js API routes, edge functions, BFFs — so the client talks to one trusted surface and you can cache, retry and observe centrally.
We build most marketing and content sites JAMstack-style with Next.js or Astro on Vercel or Netlify, pulling content from a headless CMS and commerce data from Shopify or a custom API. It is rarely the wrong default for sites that aren't full-blown applications.