JAMstack
Definition & meaning
Definition
JAMstack (JavaScript, APIs, and Markup) is a modern web architecture that decouples the frontend from the backend, serving pre-rendered static pages from a CDN while dynamic functionality is handled through APIs and serverless functions. Instead of monolithic server-rendered applications, JAMstack sites are built at deploy time, pushed to a global CDN, and enhanced with client-side JavaScript for interactivity. This architecture delivers exceptional performance (pages load from the nearest CDN edge), security (no server to attack), and scalability (CDNs handle traffic spikes automatically). The JAMstack ecosystem includes frameworks like Next.js, Astro, and Nuxt; hosting platforms like Vercel and Netlify; headless CMS solutions like Sanity and Contentful; and backend services like Supabase and Firebase.
How It Works
JAMstack is a web architecture where JAM stands for JavaScript, APIs, and Markup. The core principle is pre-rendering: the entire front end is compiled into static assets during a build step and deployed to a CDN. JavaScript handles dynamic interactions on the client side, while server-side functionality — authentication, payments, database queries — is abstracted into reusable APIs called over HTTPS. There is no monolithic server generating pages at request time. The build process typically uses a static site generator or a modern framework to pull content from headless CMSs, databases, or markdown files, then outputs plain HTML, CSS, and JavaScript files. These files are distributed globally via CDN edge nodes, so every user hits a server close to them. When content changes, a webhook triggers a new build or uses ISR to regenerate specific pages without redeploying the entire site.
Why It Matters
JAMstack architecture fundamentally changes the security and performance profile of web applications. With no origin server processing requests, the attack surface shrinks dramatically — there is no database to inject into and no server to exploit. Performance improves because CDN-served static files have sub-50ms TTFB globally. Developer experience also improves: front-end teams work independently, deploy via Git push, and preview every branch automatically. Scaling becomes a non-issue since CDNs handle traffic spikes natively without provisioning additional servers. We have seen JAMstack reduce hosting costs by 60-80% compared to traditional server setups while simultaneously improving Lighthouse scores.
Real-World Examples
Netlify and Vercel are the two dominant platforms purpose-built for JAMstack deployment, offering automatic builds from Git, preview deployments, and serverless functions. Popular static site generators include Next.js, Gatsby, Hugo, and Eleventy. Content is typically managed through headless CMSs like Contentful, Sanity, Strapi, or even Notion via API. Stripe and Snipcart add e-commerce functionality. Auth0 and Supabase Auth handle authentication. A typical JAMstack e-commerce store might combine Next.js for the front end, Sanity for product content, Stripe for payments, and Algolia for search — all deployed on Vercel with automatic preview URLs per pull request.
Tools We've Reviewed
Related Terms
Serverless
InfrastructureCloud model where providers manage servers — devs deploy functions on-demand.
Next.js
DevelopmentFull-stack React framework by Vercel for production web applications.
SSR / SSG / ISR
DevelopmentWeb rendering strategies: server-side, static generation, and incremental regeneration.
CDN
InfrastructureGlobal server network delivering content from the location nearest to each user.