About Breaklytix
Breaklytix is an API change monitoring service. It watches the changelogs of the third-party APIs a codebase depends on, detects changes that can break an integration, and maps each one to the repositories, files and lines that use the affected endpoint.
The problem it solves
Every application sits on a stack of external APIs — payments, messaging, AI models, storage, auth. Those providers publish breaking changes continuously, but the announcement lands in a changelog nobody on the team reads. The change reaches production later as a failed request in a place that is hard to trace back to a provider release note.
Breaklytix closes that gap in both directions: it reads the provider side so you do not have to, and it reads your code so an alert only fires when the change actually touches something you call.
How it works
- Connect a GitHub repository through OAuth.
- The scanner maps the providers, SDKs, endpoints and environment variable names your code uses.
- Provider changelogs are fetched daily and normalised into classified change entries.
- Each entry is matched against your detected usage; matches become alerts with file and line references.
- Mechanical fixes can be proposed as reviewable pull requests.
Read the full documentation at /docs, or browse the list of monitored providers.
Design principles
Access you control
Repository scanning uses the GitHub access you authorize with the repo scope, including private repositories. Breaklytix reads repository contents to detect API usage. It never pushes, merges or edits a repository on its own; an auto-fix pull request is created only after you approve a specific proposed fix, and a human still reviews and merges it.
Official sources only
Changes come from each provider's own changelog, release notes or release feed. No scraped aggregators, no guessed release dates, no invented severity scores.
Provider keys encrypted
Scanning detects which APIs your code calls from imports, packages, endpoint strings and environment variable names; it does not need provider credentials. If you add a provider API key for runtime signals, it is encrypted with Fernet at rest and never returned to the browser.
Honest empty states
When a provider has no telemetry yet, the dashboard says so instead of showing a synthetic health score. An alert that does not match your code is labelled unmatched, not silently dismissed.
Contact
Questions about the product, security, or data handling: support@breaklytix.site. The service is operated by Breaklytix. See the security overview, privacy policy and terms of service for the formal details.