Tripswitch

Tripswitch

A shared circuit breaker and reliability control plane for distributed systems

Tripswitch is a developer-facing service that evaluates real-time metrics, tracks breaker state, and makes reliability visible across services, jobs, and languages.

Instead of burying circuit breakers inside application code, Tripswitch gives your whole system a single, shared understanding of what is healthy and what is not.

What it does

Tripswitch accepts metrics and events over an API, evaluates them against breaker rules, and exposes the resulting breaker state and history in real time.

Teams use it to:

  • detect when a dependency is degrading
  • prevent cascading failure
  • understand why something tripped
  • coordinate behavior across services

Breakers can be shared by:

  • web services
  • background jobs
  • cron workers
  • or any system that can send metrics

Who it is for

  • Teams running distributed systems across multiple services, languages, or job runners who need a single source of truth for dependency health
  • Teams that depend on flaky or rate-limited third-party APIs and want failures detected, explained, and shared across all consumers
  • Teams that want reliability decisions to be visible, auditable, and testable instead of buried inside application code

Why Tripswitch exists

Circuit breakers are supposed to protect systems from cascading failure. In practice, they end up duplicated across services and invisible when something goes wrong.

One service thinks an API is down. Another thinks it is fine. A job runner keeps retrying. A web app keeps serving traffic.

Tripswitch exists to give distributed systems a shared understanding of health.

Instead of every service running its own private breaker, Tripswitch lets all of your services report metrics into a single reliability control plane. That plane evaluates those signals, tracks state over time, and exposes clear, auditable breaker decisions that every consumer can see.

You still decide how your code reacts. Tripswitch decides what the system knows.

What it looks like

Current state

Tripswitch tracks the live health of a dependency across your system. Each breaker evaluates real metrics over a rolling window and shows you its current state, threshold, and sample count in one place. This is the shared source of truth every service can check.

Screenshot placeholder

History

Every breaker transition is recorded with context. You can see when it opened, how severe the failure was, and when or whether it recovered. This makes intermittent problems visible instead of guesswork.

Screenshot placeholder

The trip event

When a breaker opens, Tripswitch captures the exact evidence that caused it. The evaluation window, sample count, threshold, and the sample that pushed it over the edge, including its trace ID, are all recorded together. You can click straight from the trip to the trace that needs debugging.

Screenshot placeholder

Get started

Tripswitch is live and available to try.

  • create a project
  • define a breaker
  • send metrics via API
  • watch the breaker evaluate and change state in real time

No credit card required