You find out from a user
A frontend, a mobile app or a partner integration stops working, and the first alert is a customer who can't do their job.
Building now · Looking for design partners
API changes arriveas PRs, not outages.
When an API changes, Oktet finds every place your code calls it and opens a pull request with the fix. Your clients keep working, and nobody has to read a changelog.
Keeps working when an API changes
web appsmobile appsinternal servicespartner integrationsthird-party APIspublic APIs
[01] The problem
An API change shouldn't become an incident.
Backend tests pass and the change ships. The code that calls the API lives somewhere else, and that's where things break.
Not every client can update at once
Old app versions stay on phones for weeks, and partners ship on their own schedule. Your API has to keep working for all of them.
Changelogs don't update code
Someone still has to read them, work out what's affected and write the fix. Useful new features go unnoticed.
Why nowAI lets teams ship changes faster than they can track what breaks, and agents now call APIs too.
[02] How it works
From API change to a ready-to-merge fix.
This is what we're building: connect your repos once, and Oktet checks every change and does the follow-up work for you.
01
Connect your repos
Install the GitHub App on your backend and on the repos that call it.
02
Map every call
Oktet reads the API contract from your code or OpenAPI spec, then finds every place your clients use it.
03
Check each pull request
Every backend PR is marked as no change, additive or breaking, with a comment listing the clients it affects.
04
Fix the clients
For a breaking change, each affected repo gets a PR with the fix before the change ships.
05
Keep old versions alive
When a client can't update right away, like an installed mobile app, the previous version stays live until it migrates.
06
Surface new features
When an API adds something useful, clients get a PR or a note showing how to use it.
[03] Example
What your team will see.
An example: a backend PR renames one field in a response. Here's how it will work, from the first check to the merge.
oktet commented on api-server PR #412Breaking change in GET /v1/invoices Response field renamed: due → due_dateAffected clients web-app lib/billing.ts:42 web-app hooks/invoice.ts:18 mobile-app api/client.ts:97Already done ✓ Fix opened in web-app (PR #88) ✓ Fix opened in mobile-app (PR #31) ✓ /v1 kept live for older app versions (PR #413)PR #412 timelineexample
10:02›PR opened in api-server
10:03›Breaking change found
10:09✓Fix PRs opened in 2 clients
10:41✓Clients reviewed and merged
11:15✓api-server ships, nothing breaks
█
- Every fix goes through your own code review and CI
- Your tests run in an isolated sandbox before a PR opens
- When Oktet isn't sure, it flags the PR for a person to check
[04] Why Oktet
Other tools see one side. Oktet sees both.
Keeping an integration working takes the exact change, the exact usage in each client, and the old version kept live until everyone migrates.
When you own the API
Oktet reads the change from your pull request before it ships. Clients get their fix first, and the previous version stays live until they migrate.
When you call someone else's API
Oktet reads the provider's changelog and release notes as soon as they're published, finds the calls in your code and opens a PR with the fix.
When both sides use Oktet
The provider's exact change reaches the consumer's code before it ships. Every company that joins makes the fixes more accurate for the others.
| Oktet | Docs and SDK tools | Changelog trackers | |
|---|---|---|---|
| Knows what changed | Yes, from the PR or the changelog | Yes, from the spec | Only what the changelog says |
| Knows who calls the API | Yes, across connected repos | No | Yes, in your code |
| Fixes the calling code | Yes, a PR in each affected repo | No | Some open fix PRs |
| Keeps the old version live | Yes, when you own the API | No | No |
[05] Design partners
Build it with us.
We're building Oktet now, and we're looking for a small group of startups to be the first to run it on real repos. It starts in a mode that opens no PRs until you're ready.
[06] FAQ
Questions, answered.
Ship API changes without breaking anyone.
Tell us about your API and the clients that call it. If it's a fit, you'll be among the first to run Oktet on your repos.