On this page
If you want the right people told
A diff does not know who calls an endpoint. Graphwake keeps that map from subscriptions and sends the alert to only those teams. Read how routing models compare.
Routing by subscription
Each breaking change goes only to the teams subscribed to the endpoint.
Impact score
Each change set gets a 0-100 score with public rules.
Ownership
See who owns each endpoint, next to who consumes it.
Discovery
When an endpoint has no subscribers, Graphwake suggests teams that may be affected, with a reason for each.
Sorted by the question each tool answers
| Tool | Answers | Good for | Keep in mind |
|---|---|---|---|
| Graphwake | Who is affected, and how badly? | Routing each breaking change to subscribed teams, impact score, ownership | Reads only the spec; never blocks a build |
| oasdiff | What changed? | A breaking-change diff, GitHub Action and review pages | Consumer routing is not listed on their site |
| Optic | What changed? | Was a CI-native diff and lint tool | Repository archived on 2026-01-12 |
| Bump.sh | What changed? (and publish it) | Hosted docs and changelogs, webhooks | A docs platform, not a per-team router (not listed) |
| Pact / PactFlow | Does it break at runtime? | Consumer-driven contract tests | Needs consumer test code |
| Specmatic | Does it break at runtime? | Spec-driven contract tests and a compatibility gate | A different job: testing a running service |
Competitor facts as of 2026-11-01; each tool has its own page with sources. “Not listed” means we did not find it on their public pages.
When oasdiff alone is enough
- Only the pull request author needs to know what changed: oasdiff is free and mature.
- You want to inspect or extend the rules, since the code is open.
A practical combination
Keep a spec check in every pull request, route alerts through Graphwake, and add contract tests (Pact or Specmatic) only where the cost of a runtime break is high.
Questions
What is the best alternative to oasdiff?
It depends on the question. If your gap is telling the teams that depend on an endpoint, Graphwake: it keeps the consumer map, scores the impact and alerts only those teams. For a diff alone, look at the tools that answer “what changed”.
Can I keep oasdiff?
Yes. Graphwake works next to it.
Is there a free OpenAPI breaking change checker?
Yes: oasdiff is free and open source (Apache-2.0).
Pick an endpoint. See who it reaches. 7-day free trial. Cancel before day 7 and you pay nothing.
Start free trialSources and last verified
Competitor facts were checked on 2026-11-01; check their pages for the latest.