Most outages aren't caused by code — they're caused by a config change nobody saw. A DNS record flipped. A bucket went public. A webhook URL moved. ConfigTrace snapshots your infrastructure, diffs every change, and tells you how dangerous it was.
The changes that take you down don't show up in a pull request. They happen in dashboards, CLIs, and consoles — with no history, no diff, and no review.
ConfigTrace treats your live infrastructure like a repository — every sync is a commit, every change is reviewable.
Give ConfigTrace a scoped API token and an account, zone, or project ID. Credentials are encrypted at rest and never shown again.
ConfigTrace pulls the current configuration — every DNS record, rule, and setting — and freezes it as an immutable snapshot of that moment.
On a schedule or on demand, it fetches fresh state and lines it up against the last known-good snapshot.
A field-level diff engine surfaces precisely what moved: this record's content, this TTL, this rule — old value → new value.
Each change becomes an event, scored from low to critical based on its blast radius. A TXT comment ≠ a rerouted CNAME.
A clear timeline of when, what, old value, new value, and risk — instead of "uhhh, why is prod broken?"
The intelligence layer. ConfigTrace weighs each change by its potential blast radius so you can triage at a glance.
Start with DNS today. Connect the rest of your stack as ConfigTrace grows.
Connect a provider, take your first snapshot, and never wonder "what changed?" again.
Connect your first provider →