Console · Sites
Staging and Production
Last updated 18 November 2026
Build and test on staging, then deploy to production.
Every Insites site runs in one of two environments: staging or production. You build and test on staging, and your visitors use production. This page explains what each is for and how your work gets from one to the other.
Two sites, two jobs
Staging and production are separate sites. Each has its own address, database and files. You create each one in the Console and choose where it runs in the first step of the create wizard.
| Staging | Production | |
|---|---|---|
| Used for | Building, testing and showing work to others | Real users and real data |
| Cost | Free | A paid hosting plan |
| Domains | Its default address only | Its default address and your own custom domains |
| Goes only to your test email list | Sent to the real recipient | |
| API call notifications | Off until you turn them on | On |
| Who can create or delete it | Editor and above | Admin and above |
The Billing page lists a staging site as Free staging.
Build and test on staging
Make every change on staging first. Open the page, submit the form and check the result. Because staging email goes only to your test list, you can test with realistic data without emailing a real customer. To receive test email, add your address to the test recipients in the site configuration.
Move work to production
Production is a separate site, so a change does not appear there until you send it. You deploy the same code to production, either with the Insites CLI or through your AI tool using CloudShell. Check the change on staging, then deploy it.
Tip
Use sync on staging during day-to-day work, and a deploy for production. Production then changes only by a complete release. Run a deploy with a dry run first to read what would change.
The steps are in Deploy to Production. If you connect a site to a Git repository, every push to the branch it watches deploys to that site, so read Insites GitHub App before you connect production.
Go live on your own domain
Only a production site can have a custom domain. Open the site, go to its Domains tab, connect your domain and add the DNS records the Console shows. See Site Domains.
Note
Each site has its own database. Records you create on staging stay on staging, and production keeps its own.
Find the right site
The Sites page shows each site's environment. Use the Environment filter to list only staging or only production sites.
Related
- Environments: a short comparison
- Staging vs. Production: the full comparison
- Deploy to Production: the deploy steps
- Creating a Site: choose the environment
- Billing: hosting plans for production