Public prototype · diff engine live

Know which API change will break you before it ships.

Driftwatch compares two versions of an OpenAPI spec and flags every breaking change by rule, in seconds. Then it explains the impact and drafts the migration for your team.

Try the live demo How detection works

POST /charges · v1.0 → v2.0

- amount: integer

+ amount: string

- status: pending | paid | failed

+ status: pending | paid | failed | disputed

+ currency: required (query)

3 findings. Type change and a new required parameter are breaking. The new enum value is a warning for clients that switch on status.

From spec diff to safe release

Built for teams that publish or depend on APIs.

Compare

Drop in two OpenAPI 3.x specs, or point at your repo in the planned CI integration.

Classify

Each change is labelled breaking, warning or safe using documented, testable rules.

Act

Get impact notes and migration steps your team can paste into a PR or release note.

A deterministic core. Claude on top.

Detection must be repeatable, so it never depends on a model. AI is used where judgment helps.

Works without AI

The rule-based diff engine, severity levels, CI checks and alerts are plain code you can audit and run offline. Same input, same result.

Better with Claude

Claude turns the structured findings into client-impact explanations, migration patches and release notes. It reads the findings and never decides what counts as breaking.

Get early access

Hosted monitoring, GitHub checks and Slack alerts are in development. Join the list for the first invites.