🧩
🩺 Check
LV2 · Toolooo Standard
Explore → See → Understand → ActUnderstand it. Feature Level describes the depth of the tool experience.

Environment Drift Detector

Compare environment configuration structures while keeping values masked by default.

EngineeringDevOpsConfigurationEnvironmentDebugging
🔒Your tool inputs are processed in your browser and are not uploaded or sent to analytics.

Find the configuration gap

Compare key presence, empty settings, and apparent value types. Different secret values are expected and are never compared for equality.

Environment 1 · Baseline

Paste replaces this panel. Only key names and masked placeholders are displayed; comments are hidden.

8 keys parsed · values omitted from results
Environment 2

Paste replaces this panel. Only key names and masked placeholders are displayed; comments are hidden.

8 keys parsed · values omitted from results
Environment 3

Paste replaces this panel. Only key names and masked placeholders are displayed; comments are hidden.

7 keys parsed · values omitted from results

The baseline defines expected keys and shapes. Missing, extra, and drift counts change when you choose a different reference.

Structural drift summary

Drift
6
Key/environment differences
Missing keys
2
Expected by Development
Extra keys
1
Outside the baseline
Empty values
1
Across all environments
Type differences
2
Compared with baseline
Development · baseline0 / 9 keys differ
Staging · highest drift4 / 9 keys differ
Production2 / 9 keys differ
What happened
Staging has the highest structural drift: 4 keys from Development.
Why
The comparison found 2 missing, 1 extra, 2 type, and 1 empty-state differences. Each affected key counts once per compared environment.
Try
Start with the missing-key checklist, then select a key in the matrix to inspect its type or empty-state differences.

Configuration matrix

✓ same shape · × missing · + extra · ! type or empty-state review. Select a key for an explanation. Values stay omitted even while an input is revealed.

9 of 9 keys · reference: Development
Configuration keyDevelopmentBaselineStagingProduction
✓ URL-likeReference shape✓ URL-likeSame shape✓ URL-likeSame shape
✓ stringReference shape✓ stringSame shape✓ stringSame shape
— AbsentNot in baseline+ Extraboolean— AbsentNot in baseline
✓ booleanReference shape✓ booleanSame shape× MissingIn baseline
✓ stringReference shape! EmptyFilled in baseline✓ stringSame shape
✓ stringReference shape✓ stringSame shape✓ stringSame shape
✓ stringReference shape✓ stringSame shape! booleanBaseline: string
✓ URL-likeReference shape× MissingIn baseline✓ URL-likeSame shape
✓ numberReference shape! stringBaseline: number✓ numberSame shape
What happened
BUILD_TRACE: review the structural difference
Why

This key exists in Staging but not in Development. It may be an intentional environment-specific setting or an incomplete rollout.

Try
Decide whether this key belongs in the baseline or is intentionally limited to one environment.

Exports include key names, environment names, and structural findings. Configuration values and comments are always omitted.

View missing-key checklist

Parsing rules & how drift is counted

Use one KEY=VALUE per line, optionally prefixed with export. Keys are case-sensitive. Blank lines and comments are ignored; # starts a comment outside quotes. Single or double quotes must close on the same line. Duplicate keys and unsupported lines pause the comparison.

Apparent types are hints: boolean, finite decimal number, URL-like, string, or empty. Quotes do not change the inferred shape. Real environment values are normally strings. Variable references and commands stay literal text; this tool does not expand or execute them.

Drift counts missing, extra, type, or empty-state changes from the selected baseline, once per key per compared environment. Empty-value counts include the baseline. A difference can be intentional; matching shapes cannot prove that credentials, addresses, or configuration are correct.

Limits: 256 KB, 2,000 lines, and 500 keys per environment. Raw inputs stay in this page’s memory and are never added to URLs, browser storage, diagnostics, or exports. Close or clear the page when finished.

Understand Environment Drift Detector

What this tool helps you understand

Paste or open local environment files to compare key presence, empty settings, and apparent value types across development, staging, and production. See structural drift in a configuration matrix and export a sanitized checklist without uploading or saving your configuration.

When to use it

Use Environment Drift Detector when engineering, devops, and configuration work raises questions about environment drift, env file comparison, and configuration matrix and you need a concrete view before making the next move.

How to read the result

Read each finding as a diagnostic signal, then confirm it against the contract, system, file, or production context you actually control.

Assumptions and limits

The comparison focuses on key presence, empty values, and apparent types while masking values. It cannot determine whether a secret is correct or whether a configuration works at runtime.