The Jamstack is a web architecture whose name comes from its three parts: JavaScript, APIs, and Markup. The idea is to pre-build the markup of a site into static files at build time, serve those files directly from a content delivery network, and layer in dynamic behavior on the client using JavaScript that talks to reusable APIs. The term was coined by Mathias (Matt) Biilmann and Chris Bach, the founders of Netlify, who needed a way to refer to this approach in conversation.
The official site jamstack.org describes Jamstack as “an architecture designed to make the web faster, more secure, and easier to scale.” The founders explain that they introduced the terminology because there was “no easy way to refer to the architectural approach in conversation” when describing the modern way they were building for the web. By naming the pattern, they gave a growing community a shared vocabulary, much as the term “Ajax” had done a decade earlier.
The core move is decoupling. In older server-rendered stacks like PHP or Rails, a server assembled HTML on every request by querying a database. Jamstack instead separates the build of the markup from the runtime serving of it. Pages are generated ahead of time by a static site generator, committed as plain files, and pushed to a CDN edge close to users. Because there is no application server rendering pages on demand, the attack surface shrinks and the site scales by simply copying files.
Anything that needs to be dynamic, such as form submissions, search, comments, or authentication, is handled by calling APIs from the browser or from build-time functions. These can be third-party services or the site’s own serverless functions. This separation is why Jamstack became closely tied to the rise of serverless platforms and headless content management systems.
The approach grew rapidly through the late 2010s alongside tools like Gatsby, Next.js, Hugo, and Eleventy, and hosting platforms like Netlify and Vercel that automated the build-and-deploy pipeline. Over time the strict “static-only” framing softened as frameworks blended static generation with on-demand server rendering, but the central Jamstack ideas of pre-rendering, decoupling, and serving from the edge remained influential on how modern sites are built.