Create a staging branch with its own URL, env vars and test database, so every change gets checked before it reaches real users.
Set up a staging branch on staging.mydomain.com that deploys before production
How it works
- Create a staging branch: Vovy creates a staging branch in GitHub from your main branch and pushes it.
- Give it a fixed domain: In Vercel's Domains page, Vovy adds staging.yourdomain.com and assigns it to the staging Git branch so it always shows the latest staging build.
- Point staging at test services: Vovy sets Preview env vars for the staging branch to use a separate test database and Stripe test keys, so testing never touches real data.
- Add the DNS record: Vovy asks, then adds a CNAME for staging with the value Vercel shows.
- Show the workflow: A flow card shows the path: feature branch, then staging, then main. Vovy explains how to merge each step on GitHub.
What you provide
- Your project on Vercel
- Your domain's DNS
- A test database, or Vovy makes one
What you get
- staging.yourdomain.com live
- Test keys and database for staging
- A clear release workflow card
FAQ
Does staging cost extra on Vercel?
A branch domain works on any plan. Vercel's dedicated custom environments feature needs a paid plan, but you don't need it for this.
Why a separate database?
So test signups, fake orders and experiments never show up for real users or mess with real data.
Isn't a preview link enough?
Preview links change with every push. Staging gives testers one address that always has the latest candidate.
Related tasks
All tasks