Netlify has coined Distributed Persistent Rendering (DPR), much as it coined Jamstack. While DPR introduces new mechanisms, its goal is simplification, and it draws on ideas as old as the web itself.
Netlify CEO Matt Biilmann frames the problem in terms of complexity creep. React began simple and addressed clear JavaScript architecture problems, but as it has taken on more use-cases it has grown more complicated and risks losing the appeal its simplicity once provided. Jamstack faces the same pressure as it grows to accommodate more use-cases.
The large-site build problem
One such complication is sites with many thousands of pages, which can have very slow build times. Frameworks have responded with incremental builds, but the fundamental issue remains: change a single link in a site footer and the whole site is rebuilt on that one change.
DPR inverts this: instead of building many thousands of pages during a build, skip them until each page is requested.
How the page lifecycle works
The mental model is straightforward:
- Some pages are pre-built as usual.
- Some pages are deferred and not built.
- When a deferred page is requested for the first time, it is built and cached so it doesn't need to be built again.
In a demonstration, Zach Leatherman found a part of his site that generates roughly 400 pages on each build and told Eleventy to defer that work to the cloud — a lambda runs and builds the page when needed. Deferring those 400 pages saves seven seconds in the build. On a site of 16,000 pages, by scratch-pad math, the saving runs to four minutes. The benefit isn't only time: it also means less electricity consumed and less long-term storage used.
The pattern resembles old WordPress caching plugins, where a first request ran the PHP and MySQL queries and saved the result as an .html file on disk to serve subsequent requests. Not new, but still efficient.
No new architecture, by design
Netlify's blog post is explicit that naming DPR doesn't mean creating a brand-new solution:
Just like coining the term “Jamstack” didn’t mean inventing an entirely new architecture from scratch, naming this concept of “Distributed Persistent Rendering” doesn’t mean we’re creating a brand new solution.
The term “DPR” is new to us, but in a lot of ways, we’re taking inspiration from solutions that have worked in the past. We’re simply reworking them to fit with modern Jamstack best practices.
Implementing it
On Netlify, a DPR architecture relies on the beta On-Demand Builders.




