chaosd vs Toxiproxy
chaosd
github.comToxiproxy
github.comSide by side
| Figure | chaosd | Toxiproxy |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Chaos Engineering Platforms | 7.9 (#11) | 8.2 (#8) |
| Deployment | Chaosd is downloaded and deployed separately from Chaos Mesh. | 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. |
| License | The GitHub repository identifies its license as Apache-2.0. | The GitHub repository identifies the project license as MIT. |
| Purpose | Chaosd is a Chaos Engineering tool for injecting and recovering faults in physical machine environments. | Toxiproxy is a TCP proxy for simulating network and system conditions in chaos and resiliency testing. |
| Security | The PhysicalMachineChaos guide shows Chaosd configured with TLS certificates and says running the service without generated certificates is not recommended for cluster security. | 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
chaosd
Chaosd is free Apache-2.0 software for injecting and recovering faults on physical machines. It can create process, network, CPU or memory pressure, disk, and host faults. Use it as a command-line tool or run it as a background service controlled through HTTP requests. Chaosd is deployed separately from Chaos Mesh; PhysicalMachineChaos experiments require service mode on each targeted physical or virtual machine. The documented environment requires glibc 2.17 or later, and the binary download described is a Linux amd64 tarball. Network experiments using tc or iptables require sudo or root privileges. Deployment prerequisites include tc, ipset, and iptables; source builds additionally list stress-ng and byteman. Experiments can be searched and recovered by UID. TLS certificates are shown for service security, and running without generated certificates is not recommended.
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.