BreakerMachines is a production-ready circuit breaker implementation for Ruby that prevents cascade failures in distributed systems. Built on the battle-tested state_machines gem, it provides a clean DSL, thread-safe operations, multiple storage backends, and comprehensive introspection tools. Unlike other solutions, BreakerMachines prioritizes safety by avoiding dangerous forceful timeouts while supporting fallback chains, jitter, and event callbacks.

ChronoMachines offers a flexible and configurable solution for handling transient failures in distributed Ruby applications. It provides powerful retry strategies, including exponential backoff and full jitter, with customizable callbacks. Features optional Rust-powered native performance on CRuby with pure Ruby fallback for JRuby compatibility.

BehaviorMachines runs behavior trees whose nodes follow the behavior-tree pattern: Sequence, Fallback, their reactive variants, thresholded Parallel, IfThenElse, WhileDoElse, and the usual decorators. Every running leaf the tree abandons is halted exactly once, in the same call, so leaves can own real resources. Pure Ruby, with an optional native backend built on the behavior-machines Rust crate, and leaves for state_machines objects.

Fault injection for chaos engineering: arms a named experiment that makes a dependency fail, stall or lie for a share of calls, so the breakers, retries and budgets around it can be shown to work. Bound to Ruby from the zero-dependency rogue-machines crate. Disarmed by default, and every experiment carries an expiry it cannot outlive.

A supervision tree that restarts what died the way OTP would: one_for_one, one_for_all or rest_for_one, bounded by a restart intensity that escalates instead of thrashing. The decisions come from the no_std supervisor-machines crate; Ruby owns the threads, the restart backoff comes from chrono_machines and the shutdown budget from deadline_machines.

ThrottleMachines provides ultra-thin, elegant rate limiting with temporal precision for distributed systems.