chaosd vs Tumult
chaosd
github.comTumult
tumult.rsSide by side
| Figure | chaosd | Tumult |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | — | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Chaos Engineering Platforms | 7.9 (#11) | 7.1 (#20) |
| Deployment | Chaosd is downloaded and deployed separately from Chaos Mesh. | 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. |
| License | The GitHub repository identifies its license as Apache-2.0. | Tumult is open source under the Apache-2.0 license. |
| Purpose | Chaosd is a Chaos Engineering tool for injecting and recovering faults in physical machine environments. | Tumult is a Rust-native chaos engineering platform for defining, running, and analyzing experiments that test how systems behave under failure conditions. |
| 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 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
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.