Who runs Jamstack.org and where can I get support?
Updated
Jamstack.org is run by Netlify. The site's footer carries the Netlify logotype and a "© 2026 Netlify" copyright line, and it links to a set of Netlify-operated resources: Netlify Support, a GitHub repository, a Code of Conduct, a Trust Center, and policy pages covering Privacy, Security, GDPR/CCPA, and Abuse. So if you need help with the site itself or want to report a problem, Netlify is the organization behind it.
What Jamstack.org actually is
The site describes Jamstack as "an architectural approach that decouples the web experience layer from data and business logic, improving flexibility, scalability, performance, and maintainability." In practice that means the front end you serve to visitors is separated from the systems that hold data and run business logic, which are reached through APIs. The site frames this as enabling "a composable architecture for the web where custom logic and 3rd party services are consumed through APIs."
That definition matters for the support question: Jamstack.org is a reference and community site about the approach, not a hosted platform you deploy to. The operational support you'd look for depends on which part you're dealing with.
Support and resource channels listed on the site
| What you need | Where the site points |
|---|---|
| Product or platform help | Netlify Support |
| Source code, issues, contributions | GitHub repository |
| Community behavior standards | Code of Conduct |
| Security, privacy, and compliance documentation | Trust Center, Privacy, Security, GDPR/CCPA pages |
| Reporting misuse | Abuse page |
The site also organizes learning material under a menu that includes Home, Glossary, Jamstack TV, Site Generators, Headless CMS, Community Survey, and a "Connect with us" section. Those are the entry points for understanding the architecture rather than for filing a support ticket.
Where the concept came from
The site credits Matt Biilmann with taking the concept mainstream through his presentation at Smashing Conf 2016, described as "the quintessential introduction to the Jamstack." A video of that talk, "The New Front-End Stack," is linked from the site. This is useful context if you want the original framing rather than a later summary — the vocabulary and priorities in that talk shaped how the term is used today.
Choosing the right channel
- If your question is about how Jamstack works or what a term means, start with the Glossary and the Site Generators or Headless CMS sections.
- If your question is about a Netlify product or account, use Netlify Support rather than the community pages.
- If you want to report a bug in the site or contribute, the GitHub repository and Code of Conduct are the relevant links.
- If you need compliance or security documentation, the Trust Center and the Privacy, Security, and GDPR/CCPA pages are the ones to check.
One caveat worth stating plainly: the site lists these destinations but does not describe response times, support tiers, or whether any of them require an account. If turnaround matters to you, confirm that directly with Netlify before relying on a particular channel.