Environment Drift
Find The Differences The Build Number Cannot Show
Side-by-side environment snapshots with an X-ray range slider — peel through App version, dependencies, schema, env vars, flags, runtime config, and integrations until drift is visible at the layer that matters.
billing-saas · RC-204
DevelopmentStagingProduction
App version
204-rc1
204-rc1
203
Dependencies
libbilling 2.4.0
libbilling 2.4.0
libbilling 2.3.1
Schema
2047 pending
2047 missing
2046 applied
Env vars
14 set · 3 delta
12 set · 1 delta
11 set
Feature flags
3 enabled
2 enabled
0 enabled
Runtime config
v2 API on
v2 API partial
v1 API only
Integrations
webhook v2
webhook v2
webhook v1
Move the X-Ray boundary to focus a layer, or Accept Intentional Drift with an audit note.
- Compare Environments — full snapshot diff across three envs
- Move X-Ray Boundary — scrub through layers sequentially
- Inspect Drift — open source evidence for a mismatch
- Accept Intentional Drift — document expected differences
- Create Remediation Task — route fix to owner with context
Green Builds Still Need Context
Promote every build with the context production actually needs.
PromoJade is the Software Release Context Layer between source control, CI/CD, and production — not another pipeline. Know what moves, where it lands, and whether environments agree before traffic arrives.