Where Did the Jamstack Concept Come From?

The Jamstack concept was brought into the mainstream by Matt Biilmann through his presentation at Smashing Conf in 2016. That talk is presented on jamstack.org as "the quintessential introduction to the Jamstack," and the site links to the video along with further videos and resources.

The origin story

According to jamstack.org, the roots of Jamstack trace to that 2016 Smashing Conf presentation. The site credits Matt Biilmann with taking the concept mainstream, and it treats his talk — The New Front-End Stack — as the canonical starting point for understanding the approach.

What the talk introduced

The architectural idea behind Jamstack, as described on the site, is a decoupling of the web experience layer from data and business logic. In practice that means:

• Business logic no longer dictates the web experience.
• Custom logic and third-party services are consumed through APIs.
• The result is a composable architecture for the web.

The site frames these properties as improvements to flexibility, scalability, performance, and maintainability.

Where to find the original material

jamstack.org points visitors to the Smashing Conf 2016 talk video directly, and offers a "See more videos and resources" path for going further. If you want the primary source rather than a summary, that talk is the place to start.

Why the origin matters

Knowing that Jamstack began as a conference talk rather than a formal specification helps explain why the term is used as an architectural approach rather than a fixed standard. The site's own definition — decoupling the experience layer from data and business logic, with APIs as the connective tissue — is the through-line from that 2016 presentation to how the concept is described today.