Openfuse Documentation

When a downstream service starts failing, the failure spreads. Every server keeps calling the broken dependency, response times spike, queues back up, and your users see errors everywhere. Circuit breakers solve this by cutting off failing services early, but traditional libraries run independently in each process. If you have 50 servers, you have 50 breakers that trip at different times, recover at different times, and can't be controlled from the outside.

Openfuse centralizes all of that. One SDK call wraps your existing code. One dashboard gives you visibility and control over every breaker, across every server, in real time.

How it works

Every server in your infrastructure runs the Openfuse SDK. The SDK keeps a local cache of breaker state, synced with the Openfuse API in the background. When you call protect(), the state check happens from cache in sub-millisecond time. No network round-trip in the hot path.

In your code, wrap any downstream call with protect():

const customer = await openfuse.breaker('stripe').protect(
  () => stripe.customers.retrieve(customerId),
  { fallback: () => cachedCustomer },
)

Breakers trip automatically when failure thresholds are reached, or you can flip them manually from the dashboard. State changes propagate to all servers within seconds.

Get started

Get your API credentials by signing up, then follow the Quickstart.