Comment by rodrigorcs

I've been building Openfuse (https://openfuse.io), a centralized circuit breaker platform.

Started building it about a year ago after dealing with the same problem across multiple companies: circuit breakers scattered across dozens of services, each configured slightly differently, no single place to see what's happening when things go sideways. The existing options are either libraries you embed in every service (Resilience4j, opossum, etc.) leaving every server stateful, or going full service mesh which is overkill for most teams.

Openfuse gives you a central control plane for circuit breaker policies across your stack. You define your reliability rules in one place, get visibility into breaker states, and can react without redeploying anything.

Been a great project and I'm genuinely happy with where it landed. If you're running microservices or an integration-heavy monolith and have ever cursed at a cascading failure, I'd love to hear how you're handling it today! :)