Demo
Watch the walkthrough, then try Stack Doctor with sample stacks below.
Watch the walkthrough
Setting up a stack, validating it, and keeping config in sync.
Example stacks
Toggle between production and staging to see how Stack Doctor compares environments and detects drift.
Sample data only — no login required.
Imagine this is your production stack.
| Key | Value | Secret |
|---|---|---|
| NODE_ENV | production | No |
| API_URL | https://api.example.com | No |
| DATABASE_URL | •••••••• | Yes |
| LOG_LEVEL | info | No |
| FEATURE_X | true | No |
| LEGACY_API_KEY | •••••••• | Yes |
Now compare this against its contract and baseline…
High risk means missing required keys or secret misclassification.
Suggested fixes
Add required key: JWT_SECRET
Required by contract but missing in the environment.
Restore key: JWT_SECRET
Present in snapshot but missing in current stack.
Allow key via prefix: LEGACY_API_KEY
Add allowed prefix (e.g. LEGACY_) in Stack Contract.
Add to optional keys: LEGACY_API_KEY
Add this key to optional keys in Stack Contract.
Remove disallowed key: LEGACY_API_KEY
Key is not in contract; remove it from the environment.
$ configstack doctor --env production Running Stack Doctor (baseline)… Missing required keys: JWT_SECRET Disallowed keys: LEGACY_API_KEY Result: HIGH (risk score: 7) CI failed: fix issues above or update baseline.
This would fail your CI pipeline.
Prevent configuration drift in your own project.