Toxiproxy vs Tumult
Toxiproxy
github.comTumult
tumult.rsSide by side
| Figure | Toxiproxy | Tumult |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Chaos Engineering Platforms | 8.2 (#8) | 7.1 (#20) |
| Deployment | 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. | Tumult is distributed as a static binary and as prebuilt Docker images on GHCR; the site says the binary needs no Python or runtime dependencies. |
| Install options | The README documents Linux packages and binaries, Homebrew and MacPorts for OS X, a Windows download, a GitHub Container Registry image, and building from source with Go. | The homepage provides a shell installer and a Docker image, and describes Tumult as a static binary with no runtime dependencies. |
| License | The GitHub repository identifies the project license as MIT. | Tumult is open source under the Apache-2.0 license. |
| Purpose | Toxiproxy is a TCP proxy for simulating network and system conditions in chaos and resiliency testing. | Tumult is a Rust-native chaos engineering platform for defining, running, and analyzing experiments that test how systems behave under failure conditions. |
| 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. | The production deployment guide says HTTP exposure beyond loopback requires authentication and documents TLS configuration for the analytics daemon's HTTP and gRPC listeners. |
Plans
In their own words
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.