Reliably vs Toxiproxy

Reliably helps teams examine operational risks and incidents as part of resilience engineering. Built around an open-source chaos engineering platform based on Chaos Toolkit, it offers an experiment builder with more than 300 actions, including attacks and probes. Teams can import JSON Chaos Toolkit experiments, reuse templates, schedule runs, and review scores, freshness indicators, timelines, and dashboards. Experiments can run as GitHub Actions, through Reliably-managed execution, with the CLI, in Docker, or as Kubernetes jobs or cron jobs. Listed targets include AWS, Azure, Google Cloud, Kubernetes, Prometheus, and Spring. Pre-checks can prevent a run from starting; configured safeguards can interrupt one during execution. Environments store variables and encrypted secrets for the app, CLI, or GitHub workflows. The Free plan is free and limits teams to one member, 180 cloud execution minutes per month, a 10-minute cloud execution cap, and two weeks of data retention. Start costs £40 a month, billed monthly.

Toxiproxy is a free, open-source TCP proxy for testing how software responds to network and system problems in development, testing, and CI. Applications route test connections through it, then users change connection behavior through an HTTP API or command-line interface. Built-in toxics can add latency or jitter, restrict bandwidth, delay socket closure, time out or reset connections, slice TCP data, limit transmitted data, or drop packets. Settings support deterministic connection changes as well as randomized chaos. The API manages proxies and toxics, resets proxies, and returns version information and Prometheus-compatible metrics. It listens on port 8474; configuring a proxy with listen port 0 assigns an ephemeral port. Client libraries are listed for Ruby, Go, Python, .NET, PHP, Node.js, Java, Haskell, Rust, and Elixir. Installation options include Linux packages and binaries, Homebrew and MacPorts, a Windows download, a container image, and building from source with Go. The project identifies its license as MIT. Its HTTP API is unauthenticated by default, though bearer-token authentication is supported.