LitmusChaos vs Toxiproxy
LitmusChaos
litmuschaos.ioToxiproxy
github.comSide by side
| Figure | LitmusChaos | Toxiproxy |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 2 | 1 |
| Spec score · Chaos Engineering Platforms | 7.5 (#14) | 8.2 (#8) |
| Deployment | The homepage offers getting started on a user's own cluster and shows Helm as an installation option. | The project provides Linux packages and binaries, macOS installation through Homebrew or MacPorts, a Windows download, a GitHub Container Registry image, and a source build option. |
| Intended users | The site describes Litmus as designed for developers, Kubernetes developers, and SREs. | The project is aimed at developers and teams testing service failure handling in development, unit and integration tests, and CI. |
| Purpose | Litmus is an open-source chaos engineering platform for identifying infrastructure weaknesses through controlled chaos tests. | Toxiproxy is a TCP proxy for simulating network and system conditions in chaos and resiliency testing. |
| Security | The homepage says the MCP Server uses tokens and scoped access for safer experimentation workflows. | The HTTP API is unauthenticated by default and can create proxies to arbitrary upstreams; the project advises against exposing it to untrusted networks and supports bearer token authentication. |
Plans
In their own words
LitmusChaos
LitmusChaos is an open-source chaos engineering platform for finding infrastructure weaknesses through controlled tests. It is designed for developers, Kubernetes developers, and SREs, and supports Kubernetes along with cloud and network fault injection. Experiments can be declared, scheduled, browsed, and analyzed, and can run in sequence or in parallel. ChaosHub provides tested experiments that users can tune to get started. Probes let teams define and check steady-state hypotheses within chaos scenarios. Litmus exports Prometheus metrics so teams can assess impact through in-house dashboards or external visualization and APM tools. The platform can be installed on a user's own cluster, with Helm offered as an installation option, or used through hosted SaaS; its deployment model is hybrid. A Backstage plugin displays experiments, Chaos Hubs, environments, and experiment runs. The Litmus MCP Server works with Model Context Protocol clients, including Claude Desktop, to discover, run, and observe experiments, using tokens and scoped access. The project is CNCF-hosted and identifies itself as a CNCF Incubating Project. The hosted SaaS and open-source platform plans are both listed at free.
Toxiproxy
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.