One team changes its API. The teams that call it don't hear about it. Their apps break in production.
Graphwake makes sure the right teams hear first. It watches your OpenAPI specs, knows which teams consume each endpoint, and alerts only those teams when a change is about to break them.
How it works
- Connect your specs: one CI step on every pull request (GitHub Actions, GitLab CI, Azure DevOps, Bitbucket Pipelines, Jenkins), or a published spec URL checked every 30 minutes
- Map who calls what: consumer teams subscribe to the endpoints they call. Producers don't maintain a consumer list.
- Catch breaking changes before merge: detection is powered by oasdiff
- Route the alert: only the teams that call a changed endpoint are alerted, in Slack, Microsoft Teams or email. Every other team stays quiet.
What you get
- Impact score: every pull request gets an explainable 0–100 score, the teams it affects, and what breaks for each one
- Service graph: who owns and who consumes every endpoint, with orphan endpoints flagged
- Change history: an append-only record of changes, subscriptions and ownership, so incident reviews start with facts
Who it's for
Engineering organisations with 20+ developers, several teams that depend on each other's APIs, and OpenAPI specs. Engineering leads, CTOs and platform teams use it to cut incidents caused by cross-team API changes. Developers use it to hear about a breaking change in the channel they already watch.
Why it's different
Diff tools tell you what changed. Changelogs broadcast to everyone. Contract testing needs test code from every consumer. Graphwake knows who each change hurts and tells only them.
We read your spec, not your code. Nothing runs in production. Data is hosted in the EU (Germany).
Pricing
From $99/month, with a 7-day trial that includes every feature. Unlimited specs, services, teams and subscriptions on every plan.
If cross-team API changes have ever broken your app, I'd love your support, and even more your honest feedback.