DRIFT/LINE

LOCAL CLI / RELEASE EVIDENCE

Find the first bad difference.

Turn redacted config snapshots into a timeline that says when staging and production split—and who touched it last.

Install driftline Trace the seeded incident
  • Values never enter the ledger
  • dotenv, YAML, and JSON
  • Zero telemetry
Two perforated configuration strips passing through a proofing machine, with one branch marked out of alignment in red.
One change slips out of register. Driftline marks the first observable capture.
01 / CAPTURERead layered files
02 / NORMALIZEHash and classify
03 / EXPLAINName first drift + actor

RECORDED INCIDENT / 4 CAPTURES

Scrub to the exact moment.

The demo uses fake fingerprints and never reads your files. Use the arrow keys on the timeline or choose a capture.

Capture 1 of 4

Left and right arrow keys move through captures.

ALIGNED

No active drift

Staging and production fingerprints match across 18 normalized keys.

staging
18 / 18 aligned
release-184.yaml
production
18 / 18 aligned
release-184.yaml

Observed after: deploy-bot captured production

NOT A FILE DIFF

The states incidents care about.

Absent

The key was not present in the environment snapshot.

Explicit null

The key exists and intentionally carries no value.

Overridden

A later input layer replaced the earlier fingerprint.

Secret-like

Credentials are typed as secret and represented only by a hash.

RUST / SINGLE BINARY

Keep the evidence on your machine.

Build from source today. Registry publishing is handled by the factory after release.

INSTALL
cargo install --git https://github.com/B-Divyesh/sf-config-drift-timeline config-drift-timeline
CAPTURE + REPORT
driftline capture --env production \
  --at 2026-08-28T10:42:00Z --actor priya \
  --source config/production.yaml

driftline report --compare staging,production --fail-on-drift

Raw values are discarded before the ledger is written. JSON output remains free.

ONE-TIME / NO SUBSCRIPTION

The CLI is complete. Pro standardizes the follow-through.

Keep capture, timeline analysis, JSON export, allowlists, and CI exit codes free. The $39 Pro incident pack adds reusable GitHub/GitLab rollout recipes, a team allowlist review checklist, and an incident dossier template.

  • One-time purchase, usable by one person on their devices
  • Works offline after a successful license check
  • Configuration data is never sent for verification
Buy Pro incident pack — $39

Sociobot/Dodo is the merchant of record and handles refunds. A refund revokes the license. See privacy and terms.

Restore your purchase

Paste the license from your receipt. The free CLI stays available either way.

Stored only in this browser and sent only to Sociobot for verification.

No license saved on this device.