Chaos Monkey vs LitmusChaos: open-source chaos and resilience tools compared
Metrics as of , from the GitHub or GitLab API of each repository. Refreshed monthly.
Summary
Chaos Monkey: Netflix chaos tool that randomly terminates instances and containers in production, integrated with Spinnaker.
LitmusChaos: Chaos engineering platform for Kubernetes that defines experiments as custom resources and runs them as workflows.
Both are listed under Chaos and resilience. The table gives repository metrics from the GitHub API with their fetch date, then the documented facts used for every comparison in this category, each linked to the README or docs page it comes from. A cell reads "not documented" when the fact was not found in the project's documentation; that does not mean the feature is absent.
Side by side
| Fact | Chaos Monkey | LitmusChaos |
|---|---|---|
| Stars | 17,1451 | 5,6191 |
| Forks | 1,3061 | 8991 |
| Contributors | 321 | 3271 |
| Last release | 2025-01-061 | 2026-09-171 |
| Last commit | 2024-10-031 | 2026-09-221 |
| Commits in 90 days | 01 | 441 |
| License | Apache-2.01 | Apache-2.01 |
| Primary language | Go1 | Go1 |
| Status | inactive1 | active1 |
| Target environments | Spinnaker backends: AWS, Google Compute Engine, Azure, Kubernetes, Cloud Foundry source: README | Kubernetes resources; cloud platforms such as AWS, GCP and Azure; VMware source: Docs: Litmus Experiments |
| Fault types | Random termination of virtual machine instances and containers source: README | Pod chaos: container kill, disk fill, pod delete, CPU, memory and IO stress, DNS errors, network latency, loss and corruption source: Docs: Litmus Experiments |
| Experiment format | Per-application settings in the Spinnaker web UI source: Docs: Configuring behavior via Spinnaker | Kubernetes custom resources (ChaosExperiment, ChaosEngine) combined into workflows source: README |
| CI integration | Integrated with Spinnaker, a continuous delivery platform source: README | GitHub Action litmuschaos/github-chaos-actions source: Docs: GitHub Action for Chaos Engineering in Kubernetes |
| Install method | Go (go get github.com/netflix/chaosmonkey/cmd/chaosmonkey) source: README | Helm 3 chart (litmuschaos/litmus) or kubectl YAML spec file source: Docs: ChaosCenter installation |
1 Fetched from the GitHub or GitLab API on . Hover a value for its own date.
When each fits
Written from each project's documented scope, not from preference. Neither tool is ranked.
Chaos Monkey
Fits projects that manage their applications with Spinnaker; its README describes random termination of virtual machine instances and containers in production. source: README
LitmusChaos
Fits projects that run controlled chaos tests against Kubernetes infrastructure; its README describes a control plane that constructs, schedules and visualizes chaos workflows. source: README
More on these tools
Sources
- GitHub REST API: repository, read
- GitHub REST API: repository, read
- GitHub REST API: contributors, read
- GitHub REST API: contributors, read
- GitHub REST API: latest release, read
- GitHub REST API: latest release, read
- GitHub REST API: commits, read
- GitHub REST API: commits, read
- README, read
- Docs: Litmus Experiments, read
- Docs: Configuring behavior via Spinnaker, read
- README, read
- Docs: GitHub Action for Chaos Engineering in Kubernetes, read
- Docs: ChaosCenter installation, read
Documented facts collected 2026-09-22. See the methodology for how metrics and facts are gathered.