CodeRifts
Stop breaking API changes before they hit production
A renamed field in an API response took down a POS system across 19 restaurants for a week.
The PR passed code review. All tests were green. Nobody checked the API schema.
That story is not unique. It happens constantly in microservices teams. A breaking change slips through, hits production, and costs days to debug and fix.
So I built CodeRifts.
It runs on every pull request and posts a governance report: what changed, how dangerous it is, who it affects, and what it will cost to fix. Zero config. GitHub App install and it just works.
Currently in beta. All Pro and Team features are free while I find the first paying customers.
Would love feedback from anyone who has dealt with breaking API changes in production.
1 Comment
The real tension here is whether preventing breaking changes is painful enough to become a buying priority, rather than just something engineers appreciate. Curious what progress you’re seeing in beta — are teams actually catching meaningful issues with CodeRifts that would’ve made it to production otherwise?