What Is Jamstack?
Jamstack is a web architecture based on pre-rendered static files served from a CDN, with dynamic functionality added via JavaScript and APIs — delivering fast, secure, and scalable sites.
JAM stands for JavaScript, APIs, and Markup. The core idea: pre-render as much as possible at build time, serve it from a global CDN edge, and handle dynamic behavior with JavaScript and API calls at runtime.
How Jamstack sites work:
- At build time, the site generates static HTML files (Next.js SSG, Gatsby, Astro)
- Those files are deployed to a CDN with edge nodes worldwide
- A user requests a page — it's served from the nearest CDN node in <50ms
- JavaScript in the browser calls APIs for dynamic data (auth, user-specific content, real-time)
Benefits:
- Performance — static files from CDN, no server round-trip for most requests
- Security — no server-side execution surface for most attacks
- Scalability — CDN handles traffic spikes automatically
- Developer experience — push to git, CI builds and deploys
Jamstack is not a pure static site: Next.js with App Router is Jamstack-compatible — static routes are pre-rendered, dynamic routes use server components or API calls. You get the performance of static with the flexibility of dynamic.
The shift toward hybrid: Strict Jamstack (100% static) is less common now. Most modern sites use a hybrid: static shell + server components + edge functions + client-side API calls. Next.js App Router is the most practical implementation of this hybrid model.