# Full preview environments per pull request

> Give every pull request a full, isolated environment — not just a database branch — that is secret-scrubbed and automatically swept when the branch closes.

Source: https://scribase.com/use-cases/preview-environments

Reviewing a change against production data is risky; reviewing it against nothing is useless. Scribase preview branches give each pull request a full environment — database, auth, and storage — so reviewers see real behavior without touching production, and stale environments never accumulate.

## The pains this solves

- Database-only branches that miss auth and storage state
- Manual teardown that leaves stale, credential-bearing environments
- Add-on pricing per running preview branch

## How Scribase addresses it

**Full-stack branches** — A branch includes the database, auth, and storage, so a preview behaves like the real app, not a partial copy.

**Secret-scrubbed and TTL-swept** — Branches are scrubbed of secrets and swept on a TTL when the pull request closes — no manual cleanup, no leaks.

**Included, not metered per branch** — Preview branches are part of the flat plan instead of a per-running-branch add-on.

## FAQ

**Is a Scribase branch just a database branch?**

No. A branch is a full preview environment — database, auth, and storage together — so previews reflect real behavior.

**Do I have to clean up preview environments?**

No. Branches are secret-scrubbed and swept on a TTL when the pull request closes.