You change a field in your proto file. You push it. Then you spend the next two days pinging 4 teams...
You change a field in your proto file. You push it. Then you spend the next two days pinging 4 teams on Slack asking them to update their consumers.
Sound familiar?
I built Ripple to eliminate that entire workflow. Push a breaking API change → fix PRs appear in every consumer repo. In 15 seconds. No manual coordination.
The Problem Nobody Talks About
There are great tools for detecting API breaking changes:
If you maintain any kind of open source library or internal API, you already know the headache you...
I build products solo. Every single one of them sits on top of somebody else's API — Stripe for...
Every time I need to wire up GitHub + Slack + Notion (or literally any combination of APIs), I end up...
Okay, story time. If you've worked on a full stack app where the backend is Java/Spring Boot and the...
API stress testing is broken. Here's how we're fixing it. Let's be honest for a moment. If...
Every API tool eventually turns into the same mess. Your spec lives in one place. Your tests live in...
