What is Jamstack?

What is Jamstack?

Jamstack is an architectural approach that decouples the web experience layer from data and business logic, which is how jamstack.org describes it today. The name originally stood for JavaScript, APIs and Markup, a term Netlify's then CEO Matt Biilmann coined in 2015. In the classic setup, pages are generated ahead of time, served from a CDN, and made dynamic with client-side JavaScript that calls APIs.

How it works

1. Build. A static site generator or framework turns content and templates into HTML, CSS and JavaScript files. Examples are Hugo, Eleventy, Astro and Gatsby.
2. Serve. The files go to a CDN, so visitors get pages from a nearby edge location instead of waiting for a server to render them.
3. Call APIs. Anything dynamic, such as search, checkout, comments or a CMS, is a third-party service or your own API, called from the browser or at build time.

Example

A documentation site is built from Markdown files on every commit and published to a CDN. The search box queries a hosted search API, and a contact form posts to a serverless endpoint. There is no application server to patch or scale for the pages themselves, but there are several APIs the site now depends on.

Where Jamstack stands today

The term has become less common. The jamstack.org landing page now speaks of a "composable architecture", and it does not spell out the old acronym or mention static files or CDNs. The ideas are still everywhere, but under other labels, and the line between static and dynamic has blurred: frameworks such as Next.js and Astro let you prerender some routes and render others on request, and hydration adds interactivity to prebuilt HTML. Treat "Jamstack" as a useful description of a static-first, API-driven setup, not as a strict specification.

Common mistakes

• Assuming it is always faster. A prebuilt page is fast, but a large JavaScript bundle or slow third-party APIs can undo that.
• Forgetting build time. Sites with tens of thousands of pages can take long to rebuild after every content change.
• Treating APIs as someone else's problem. Each third-party API is a dependency that can be slow or down.
• Calling it "no backend". The backend moved into services and functions, it did not disappear.

Jamstack, load testing and monitoring

Static files on a CDN rarely need a load test. The parts that do are the APIs and serverless functions behind forms, search and checkout: run a load test against those endpoints and watch them with API monitoring. See also our article on how serverless architecture changes performance testing.

FAQ

What does Jamstack stand for?

JavaScript, APIs and Markup. The acronym is the original definition, though the jamstack.org site today describes the approach as decoupling the web experience layer from data and business logic.

Is Jamstack the same as a static site?

Not exactly. Static generation is the classic way to build one, but a Jamstack-style site also calls APIs for dynamic features, and modern frameworks can render some pages on demand.

Is Jamstack dead?

The label is used less than it was, but its building blocks are standard practice: prebuilt pages, CDN delivery and API-based services. Few teams now choose it as a named category.

Is a Jamstack site good for SEO?

Prebuilt HTML is easy for search engines to read and tends to load quickly. Rankings still depend on content quality and the rest of your site.