Netlify
The platform that coined and popularized “Jamstack” — the missing piece in the spoke’s story of where SSG output actually gets built and served. Founded 2014 by Mathias Biilmann (San Francisco); it runs the annual Jamstack Conf + Community Survey, making it the ecosystem’s de-facto standard-setter, and raised a Series D at a $2B valuation (2021).
What it does — the Git→CDN deploy pipeline
Netlify operationalizes the jamstack architecture as a product:
- Git-based continuous deployment — push to a repo, Netlify runs the SSG build and publishes the generated static files to a global CDN (with automated prerendering).
- Deploy Previews — a unique URL per pull request (the preview-deploy workflow that the managed-PaaS providers in cloud-wiki also sell, here specialized for static publishing).
- Serverless + Edge Functions — Netlify Functions / Background / Scheduled / Edge — the “A” (APIs/serverless) in JAMstack that lets a pre-rendered site still do dynamic work without a request-time CMS backend.
- Forms, identity, build plugins — the glue that replaces a monolithic CMS’s built-ins.
Why it matters to the thesis
The spoke’s synthesis frames the shift as request-time CMS → build-time pre-rendering (wordpress → static-site-generator + jamstack). Netlify is the deployment substrate that made that shift practical: the SSGs (astro, eleventy, hugo, …) produce the bytes, Netlify builds and globally serves them, and serverless functions fill the dynamic gaps. It’s also where the spoke borders cloud-wiki — Netlify is a build/host platform like vercel (cloud-wiki), but its identity is specifically the Jamstack platform, which is why it lives here as the architecture’s originator rather than as a generic host. (vercel is the React/Next-leaning counterpart; Netlify is framework-agnostic and coined the term.)
Related
jamstack · static-site-generator · astro · wordpress · headless-cms · core-web-vitals