ChaosBlade vs Toxiproxy
ChaosBlade
chaosblade.ioToxiproxy
github.comSide by side
| Figure | ChaosBlade | Toxiproxy |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | 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 | 1 |
| Spec score · Chaos Engineering Platforms | 8.2 (#7) | 8.2 (#8) |
| Deployment | The CLI can be downloaded and unpacked on a host, while the tool and platform also document Kubernetes installation using Helm. | 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 project describes its goal as helping enterprises improve system availability during cloud-native adoption. | The project is aimed at developers and teams testing service failure handling in development, unit and integration tests, and CI. |
| Purpose | The project aims to help enterprises address high-availability problems during cloud-native adoption through chaos engineering. | Toxiproxy is a TCP proxy for simulating network and system conditions in chaos and resiliency testing. |
Plans
In their own words
ChaosBlade
ChaosBlade is a free, open-source chaos engineering project comprising the ChaosBlade experiment tool and the ChaosBlade-Box platform. Its stated aim is to help enterprises address availability problems during cloud-native adoption. Experiments cover CPU, memory, network, disk, processes, kernels, and files, as well as multilingual applications and Kubernetes resources. They can run through the command-line interface, Kubernetes YAML and CRDs, HTTP server calls, or the Box interface. ChaosBlade-Box provides a shared experiment interface, automates deployment of experiment tools, and can host ChaosBlade and LitmusChaos. It uses Helm for deployment management and integrates Prometheus monitoring. Safety policies support manual stopping or automatic stopping after a configured timeout. Users can download and unpack the CLI on a host, or install the tool and platform on Kubernetes with Helm. The host installation guide lists Java and MySQL requirements; automatic probe installation also needs Ansible and expect. The project supports Kubernetes and is identified as a Cloud Native Computing Foundation sandbox project.
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.