Environments and roles The right access, in the right place.
Each project has its own environments, each with its own state, keys and history. Roles decide who can view, change or approve in each one, so production stays calm.
How it works
-
Create environments
Start with development, staging and production, and add more for previews or regions.
-
Assign roles
Viewer, editor and admin per project, or let SCIM groups decide.
-
Protect production
Require approvals or block direct changes where it matters.
The details
- Separate keys
- Each environment has its own SDK keys, rotated in one click.
- Copy safely
- Promote a flag’s rules from staging to production with a diff.
- Preview environments
- Short-lived environments for preview deployments, cleaned up automatically.
More of the platform
-
Feature flags
Put every change behind a flag and decide who sees it, without a deploy.
Learn more: Feature flags -
Scheduled rollouts
Go from 1% to everyone over days, with automatic pauses when errors rise.
Learn more: Scheduled rollouts -
Experiments
Split traffic between variants and get a clear result, with the statistics done for you.
Learn more: Experiments
Try Environments and roles today
Free for small teams. Set up in minutes.