Environment Comparison
Compare feature flag states across dev, staging, and production side-by-side to catch configuration drift before it reaches your users.
Overview
The Environment Comparison view shows all your flags in a matrix format with each environment as a column. At a glance, you can see:
- Which flags are ON or OFF in each environment
- Flags that differ between environments (configuration drift)
- Flags that are ON in production but OFF in staging (potential risk)
- Flags that are ON in dev but OFF everywhere else (in-progress features)
Using the Comparison View
To access the comparison view, navigate to Flags in the sidebar and click the Compare tab, or go directly to the comparison page from the environment selector dropdown. The view displays:
| Flag | Dev | Staging | Production | Status |
|---|---|---|---|---|
| new-checkout | ON | ON | OFF | Drift |
| dark-mode | ON | ON | ON | Synced |
| ai-recommendations | ON | OFF | OFF | In Progress |
Example comparison view showing three flags across environments.
Status Indicators
Synced
The flag has the same state (ON or OFF) across all environments.
Drift
The flag state differs between environments. This is expected for in-progress features but should be investigated if unintended.
In Progress
The flag is ON in dev but OFF in staging and production — likely an active feature under development.
Filtering the Comparison View
When you have many flags, use filters to focus on what matters:
- Show only drift — Hide flags that are synced across all environments, surfacing only flags with configuration differences.
- Flag type — Filter to show only boolean, string, number, or JSON flags.
- Tags — Filter by tag to focus on flags owned by a specific team or sprint.
- Search — Search by flag key or name to find a specific flag.
Best Practices
Review drift regularly
Make environment comparison part of your pre-release checklist. Before deploying to production, review the comparison view to ensure production flags match your intended configuration. Unintentional drift is a leading cause of "it works in staging but not production" incidents.
Next Steps
- Target Inspector— debug targeting rules for specific users
- Target Comparison— compare how two users evaluate for the same flag