Jamstack
Jamstack is a web architecture in which pages are generated ahead of time as static files, delivered through a content delivery network, and enhanced with client-side JavaScript and third-party APIs when dynamic behaviour is needed.
What is Jamstack?
The name comes from JavaScript, APIs and Markup. Rather than building each page on a server when a visitor arrives, a Jamstack site is compiled at build time into plain HTML, CSS and JavaScript. Those files are then pushed to a CDN, close to users. The result is a site that loads quickly, costs little to host and exposes a small attack surface, because there is no application server or database directly facing the public.
How a Jamstack site works
- Content lives in Markdown files or in a headless CMS.
- A static site generator or framework fetches that content and builds the pages.
- The build output is deployed to a CDN.
- The browser loads the static page, then JavaScript calls APIs for forms, search, payments or user accounts.
// Client-side call to an API after the static page has loaded
const res = await fetch('/api/newsletter', {
method: 'POST',
body: JSON.stringify({ email })
});
Jamstack vs traditional architectures
| Criterion | Jamstack | Traditional server-rendered CMS |
|---|---|---|
| Page generation | At build time | At each request |
| Delivery | CDN, static files | Application server and database |
| Speed | Very fast by default | Depends on caching and server load |
| Security | Small attack surface | Larger, plugins and database exposed |
| Content updates | Rebuild and redeploy | Instant after publishing |
Benefits and limits
- Performance: pre-built pages on a CDN help Core Web Vitals.
- Scalability: traffic spikes are absorbed by the CDN.
- Developer experience: Git-based workflows and modern frameworks.
- Limit: very large sites can have long build times.
- Limit: highly personalised or real-time pages need extra work with APIs or server functions.
When to choose Jamstack
It suits marketing sites, documentation, blogs and catalogues where content changes at a moderate pace. For dashboards or apps with heavy per-user logic, a hybrid approach that mixes static pages with server-side rendering is often more practical. Today many frameworks support both, so the line between Jamstack and other models is less strict than it used to be.
Jamstack at BeBranded
We build fast, maintainable web products and choose the architecture that fits the need, from static and headless setups to full applications. Learn more about our web apps expertise.
FAQ
What does Jamstack stand for?
Is a Jamstack site always static?
What is the difference between Jamstack and a headless CMS?
Is Jamstack good for SEO?
What are the drawbacks of Jamstack?
Which tools are used to build a Jamstack site?
Linked tools
