Kubernetes Health Docker Health Terraform Health

Configuration Drift Detector

Paste two config files — staging vs production, old vs new — and instantly see every added, removed, and changed key with a drift score.

File 1 (baseline)
File 2 (current)

Paste two config files to detect drift

How It Works

1

Paste Two Files

Paste your baseline config on the left and the current version on the right. JSON, YAML, .env, and TOML are all supported.

2

Instant Diff

Every key is compared client-side in your browser. Added, removed, and changed values are categorised and colour-coded instantly.

3

Review & Share

Get a drift score from 0–100, review every change, and copy the full diff as Markdown to paste into PRs, Slack, or docs.

FAQ

Is my configuration sent anywhere?

No. Everything is parsed and compared in your browser using JavaScript. Your file contents never leave your device.

What formats are supported?

JSON, YAML, .env (KEY=VALUE lines), and basic TOML (key/value pairs with [section] headers). The tool auto-detects the format from content, or you can select it manually.

How is the drift score calculated?

The drift score is the percentage of keys that differ between the two files. A score of 0 means the files are identical; 100 means every key is either added, removed, or changed. The formula is (added + removed + changed) / total unique keys × 100.

Does it handle nested keys?

Yes. For JSON and YAML, nested objects are flattened into dot-notation keys (e.g. database.host) so every leaf value is compared individually. Arrays are compared as whole values.

Kubernetes Health Docker Health Terraform Health

Stay on top of infrastructure changes

Track releases for Kubernetes, Docker, Terraform, and hundreds more — delivered straight to your inbox when new versions land.

Powered by ReleaseRun — Free developer tools for release lifecycle management