Jamstack is an approach to building sites in which pages are generated ahead of time, served as static files from a CDN, and enhanced with client-side JavaScript that calls APIs for dynamic data. The name originally stood for JavaScript, APIs and Markup.
Why it matters
Serving files from edge locations improves speed and resilience, and removing the application server from the request path reduces the number of things that can fail. Third-party APIs for forms, search or payments become dependencies, so their availability affects your page even though your host is fine.
Example
A typical setup:
- Content lives in a headless CMS.
- A build tool pulls it and generates HTML.
- Files deploy to a CDN.
- A contact form posts to a serverless function or form API.
Common mistakes
- Treating it as a product. It is an architectural pattern with many tools.
- Forgetting to monitor the external APIs that the static pages depend on.
- Rebuilding the whole site for tiny content edits when incremental builds are available.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.