Reference
What is Jamstack?
Jamstack is an architecture where pages are pre-built at deploy time and served from a CDN, with any dynamic behaviour added through APIs and small serverless functions. In practice it produces a fast, cheap, low-maintenance site with no origin server to scale, secure or patch.
Also called: static-first architecture
What it means practically
- Pages generated at build time, served as static files
- No origin server rendering per request, so nothing to scale
- Dynamic bits handled by APIs or small serverless functions
- Deployment is a build plus an upload, and rollback is instant
What it suits
Marketing sites, documentation, blogs, portfolios and catalogue-style e-commerce where product data changes on a schedule rather than continuously.
What it does not suit
Applications where most of the page is per-user, or where content must be current to the second. Rebuilding a large site for one changed price is the wrong tool, and hybrid approaches exist precisely for that case.
The practical answer for most businesses is per-route rather than per-site: static for the marketing pages that must be fast and crawlable, server-rendered for the handful of routes that genuinely differ per visitor.
Where this is covered in depth
A definition can only go so far. JavaScript SEO: the difference between what you see and what gets indexed covers this properly — 3 minutes, free, no email required.
Who wrote this
Anas Bin Masud builds e-commerce sites and does technical SEO for businesses in the UK, Canada and Pakistan. These definitions come from client work rather than from a content brief — where an entry describes a mistake, it is usually one found on a real site. More about how I work.