Preview environments for pull requests, Render's own version

Opening a pull request against a repository with a Render Blueprint can automatically provision an entire, isolated copy of every service the Blueprint describes — directly analogous to Railway's own PR environments, and requiring the same underlying prerequisite: the infrastructure has to already be declared as a Blueprint (lesson 4) for Render to know what a "complete copy" of the project actually consists of.

Vercel's own automatic previews and Railway's own PR environments both start any included database fresh and empty by default. Render's option to seed a preview database from an actual snapshot of production data lets a reviewer test a change against realistically-shaped, real data — directly useful for catching a bug that only manifests against data with real-world scale or edge cases, the kind of thing an empty test database structurally can't surface. This is a real, deliberate trade-off of its own: production data (even a snapshot) in a preview environment raises the exact data-sensitivity and access-control questions Application Security's own privacy-by-design lesson covers — a preview environment accessible to anyone with the PR link shouldn't automatically inherit production's full, unredacted dataset without considering who can actually see it.

A preview environment left running indefinitely after its PR merges or closes is pure waste — billed compute and storage for infrastructure nobody's using anymore, the same resource-leak concern this curriculum's own Go domain described for a goroutine that never gets cleaned up, just at the infrastructure level instead of inside one running process. Render automatically tears down a preview environment once its associated PR is closed or merged, closing this loop without requiring a team to remember a separate manual cleanup step.

A preview environment shares the shape a Blueprint describes, but is its own, fully separate instance — changing a preview environment's data or configuration has zero effect on production, the same isolation principle Railway's own environments lesson established for its own Staging/Production split, just triggered automatically by PR lifecycle events here rather than created manually.