On this page
Why people are looking
- The repository is archived. Archived means no new fixes or releases from the owner (github.com/opticdev/optic, checked 2026-11-01).
- A CI check that no one maintains is a risk to your pipeline.
- A CI diff check reports to the pull request author. Teams on the other side of the API still have to be told another way.
We make no claim about why this happened. Optic was a good tool for what it did.
What Graphwake does that a CI diff does not
Graphwake takes your spec (a published URL checked every 30 minutes, or one CI step on every pull request) and compares each version with the last. Then it looks at which teams subscribed to each endpoint and alerts only them, in Slack, Microsoft Teams or email, before the merge if the spec came through CI. Each change set gets an explainable 0-100 impact score.
Alerts to subscribed teams
Only the teams that subscribed to an endpoint hear about its breaking changes, in Slack, Microsoft Teams or email.
Before the merge
When the spec comes through CI, the alert goes out while the change is still a pull request.
Explainable impact score
Each change set gets a 0-100 impact score with public rules.
Hosted: nothing to run
Keep your OpenAPI files as they are: a published spec URL checked every 30 minutes, or one CI step that never blocks a build.
Switching from Optic’s breaking-change check
- Keep your OpenAPI files as they are. Nothing in your code changes.
- Add the Graphwake CI step, or paste your published spec URL.
- Have each team that calls your API subscribe to the endpoints it uses. Subscriptions are per whole endpoint.
- The next breaking change reaches exactly those teams.
Your options
| Option | Good for | Keep in mind |
|---|---|---|
| Graphwake | Breaking changes caught and sent to the right teams, an impact score, an ownership map | Reads only the spec; never blocks a build |
| Keep running Optic (MIT code) | No migration work today | Archived, read-only repository; you maintain it or fork it |
| oasdiff | A breaking-change diff and GitHub Action; Pro adds approvals | Output goes to the PR; consumer routing is not listed on their site |
| Specmatic | Spec-driven contract testing and a compatibility gate | Tests a running service |
| Pact / PactFlow | Consumer-driven contract tests | Needs test code from consumers |
When Optic alone is enough
- It still runs in your pipeline, does what you need, and you are willing to own an archived MIT codebase.
- You rely on its lint rulesets, or on
optic captureto keep the spec in step with test traffic.
Pricing
Graphwake: a flat monthly price set by watched endpoints, with extra users billed per user. See pricing. 7-day free trial. Cancel before day 7 and you pay nothing.
Questions
Is Optic discontinued?
Its GitHub repository is archived and read-only as of January 12, 2026, per the repository page. The README says Optic Labs is now part of Atlassian. Atlassian announced the acquisition in April 2024; read their announcement for what it means for the product.
Can I still use Optic?
The code is MIT-licensed, so you can. It will not receive updates from its owner.
What does Graphwake do with my spec?
It finds the breaking changes, maps the teams that consume each endpoint, scores the impact and alerts only those teams.
Does Graphwake need repository access?
No code access: it reads only your spec.
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.