What "static" actually constrains
The word "static" in Static Site Generator (SSG) reads as a promise that a generated site is frozen until the build runs again. That reading is understandable but wrong. A static site can be as dynamic as anything else, because JavaScript remains available to it: client-side code can call an API and rewrite the pre-generated markup on the page. JavaScript, APIs and markup together are the Jamstack.
Static hosting is not the absence of server logic
Netlify is a useful lens here, since it offers static hosting only — no server-side language such as Ruby, PHP or Python rendering individual pages. Yet the platform covers most of what people assume requires an always-on server:
- Builds: Netlify runs the build process, typically including an SSG, which keeps the generated output out of version control.
- Forms: form submissions are processed by the platform, so no server has to run just for that.
- Authentication: identity is a first-class feature, meaning logged-in experiences are not off the table.
- Server-side code: it runs as cloud functions — modern, cheap, secure, focused, fast and powerful — rather than as a persistent server.
- Rendering: pages can be built on demand, so not every page must be pre-built.
Dynamic behaviour can also come from edge handlers, without any client-side JavaScript.
Where SSGs sit in this picture
SSGs and Netlify are a natural pairing, but the capability is broader than this one platform, and Jamstack increasingly describes exactly this arrangement: dynamic things happening to a static site. An SSG can produce a site with no dynamic data and no logged-in experience — and it can equally produce a site with both, on a firmer static foundation.



