ChaosBlade
chaosblade.io
- Free plan
- Windows
- macOS
- Linux
- Web
- API
- Self-hosted
What ChaosBlade is
ChaosBlade is a free, open-source chaos engineering project made up of the ChaosBlade experiment tool and the ChaosBlade-Box platform. It aims to help enterprises examine availability problems as they adopt cloud-native systems. Experiments cover CPU, memory, network, disk, processes, kernels, files, multilingual applications, and Kubernetes resources. Teams can run them through the CLI, Kubernetes YAML and CRDs, HTTP server calls, or the Box interface. ChaosBlade-Box brings experiments into a unified 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. The CLI can be downloaded and unpacked on a host; the tool and platform also document Kubernetes installation with Helm. The platform's host installation lists Java and MySQL requirements, and automatic probe installation needs Ansible and expect. The project identifies itself as a CNCF sandbox project.
Who it suits
ChaosBlade is aimed at enterprises seeking to investigate availability risks during cloud-native adoption. It suits teams able to deploy and operate experiments through a CLI, Kubernetes, HTTP calls, or ChaosBlade-Box.
Good to know, and what to watch
- Free, open-source chaos engineering project.
- Experiments include Kubernetes resources and basic system components.
- Multiple execution methods include CLI and Kubernetes YAML.
- Box integrates Prometheus monitoring.
- Timeout policies can stop experiments automatically.
- Host platform deployment requires Java and MySQL.
- Automatic probe installation requires Ansible and expect.
Plans
Every plan and priceChaosBlade
Free plan
Getting started
- Open https://chaosblade.io/en/
- Download and unpack the CLI on a host
- Install the tool or platform on Kubernetes with Helm
- Provide Java and MySQL for host platform deployment
- Add Ansible and expect for automatic probe installation
- Run experiments through the CLI, YAML, CRDs, HTTP, or Box interface
The Club's review
Overview
ChaosBlade is an open-source chaos engineering project that pairs a fault-injection tool with the ChaosBlade-Box platform. It is a strong fit for cloud-native teams seeking a free way to exercise infrastructure, applications and Kubernetes. Its broad experiment coverage and flexible execution methods are balanced by extra prerequisites if you deploy Box on a host.
Key features
ChaosBlade covers faults affecting CPU, memory, network, disk, processes, kernels and files, plus multilingual applications and Kubernetes resources. That range lets teams investigate failures across several layers instead of focusing on a single fault category. The free ChaosBlade plan states support for 3 system platforms, 4 programming-language applications, 200+ experiment scenarios and 3,000+ parameters.
Experiments can be run from the CLI, with Kubernetes YAML and CRDs, through HTTP server calls, or in the ChaosBlade-Box interface. Teams can choose command-driven or Kubernetes workflows, while Box offers a shared interface and automates deployment of experiment tools. It can host ChaosBlade and LitmusChaos, uses Helm for deployment management, and integrates Prometheus monitoring.
Box describes manual stopping and automatic stopping after a configured timeout as ways to ensure drills are resumed. These provide operators with explicit ways to end an experiment; teams still need to configure and manage drills responsibly. The project also identifies as a Cloud Native Computing Foundation sandbox project and links to Gitter, Twitter, Slack and a DingTalk community group.
Pricing
ChaosBlade is free: its plan costs nothing and is described as an open-source chaos engineering tool. The plan’s stated scope includes 3 system platforms, 4 programming-language applications, 200+ experiment scenarios and 3,000+ parameters. There are no paid tiers or seat-based limits to weigh against that offer.
The project is self-hosted, so free access comes with deployment work rather than a hosted-service option. The CLI can be downloaded and unpacked on a host; the tool and platform also document Kubernetes installation using Helm. For host deployment of Box, Java and MySQL are required, while automatic probe installation needs Ansible and expect. That makes the free plan most appealing to teams able to operate their own environment, not those looking for a managed service.
Platforms
ChaosBlade’s listed platforms are API, Linux, macOS, self-hosted, web and Windows. Kubernetes is supported, and the project documents both host-based CLI use and Helm-based Kubernetes installation. Cloud fault injection, network fault injection, experiment scheduling and blast-radius controls are also supported.
Who it's for
ChaosBlade suits enterprise and platform teams working to improve availability during cloud-native adoption, especially those that need to inject faults across host resources, applications and Kubernetes. Its multiple execution routes accommodate teams that prefer CLI or Kubernetes definitions as well as those that want Box’s shared interface. It is less suitable for teams that cannot take on self-hosted deployment and operational prerequisites.
Pros and cons
- Pros: Broad scenario coverage spans core host resources, applications and Kubernetes, giving teams more fault types to investigate in one project.
- Pros: CLI, YAML and CRDs, HTTP calls and Box provide several ways to run experiments, while Box adds tool deployment management and Prometheus integration.
- Pros: The free open-source plan and self-hosted deployment avoid a subscription commitment.
- Cons: Host deployment of Box requires Java and MySQL, with Ansible and expect needed for automatic probe installation, adding setup dependencies.
- Cons: Self-hosting means teams must run the deployment themselves rather than relying on a hosted ChaosBlade service.
Alternatives
Consider Chaos Engineering Platforms to compare options across the category. If a different fit matters more than ChaosBlade’s particular combination of tools and workflows, these alternatives are worth considering:
- FaultMesh offers a free Starter plan for up to 3 services with core fault types, basic resilience scoring and community support; its Growth plan costs $49 a month, billed per h.
- Reliably is an open-source option that describes its approach as avoiding lock-in; its Free plan is free for 1 team member.
- Chaos Toolkit is a free, open-source CLI under Apache License 2.0.
- Krkn is a free option with no pricing or usage limits stated on the opened pages.
- Chaos Mesh is a free, open-source cloud-native chaos engineering platform that runs on Kubernetes.
- Krkn-AI is free open-source software under Apache License 2.0.
- LitmusChaos offers both free hosted SaaS and an open-source platform for installation on your own cluster.
- Toxiproxy is a free, open-source TCP proxy under the MIT license.
Verdict
Choose ChaosBlade if your team needs a free, self-hosted toolkit for testing faults across infrastructure, applications and Kubernetes, with both command-line and Box-based execution. Its breadth and multiple workflows are compelling for teams prepared to own deployment. Look elsewhere if you need a hosted service or want to avoid Box’s host-installation dependencies.
The verdict
ChaosBlade offers several ways to run fault experiments, with ChaosBlade-Box adding a shared interface and deployment management. Teams considering host deployment should account for the listed Java, MySQL, Ansible, and expect requirements.
Questions people ask
Is ChaosBlade free?
Yes. The ChaosBlade plan is free and the project is open source.
Which systems and platforms does it support?
It lists Linux, macOS, Windows, API, web, and self-hosted use.
Does it support Kubernetes?
Yes. Experiments include Kubernetes resources, and Kubernetes installation uses Helm.
How can experiments be executed?
Experiments can run through the CLI, Kubernetes YAML and CRDs, HTTP server calls, or ChaosBlade-Box.
What monitoring and deployment integrations are included?
ChaosBlade-Box uses Helm for deployment management and integrates Prometheus monitoring.
What the maker publishes
- Community status
- The project site identifies ChaosBlade as a Cloud Native Computing Foundation sandbox project. source
- Deployment
- The CLI can be downloaded and unpacked on a host, while the tool and platform also document Kubernetes installation using Helm. source
- Execution methods
- Experiments can be run through the CLI, Kubernetes YAML and CRDs, HTTP server calls, or the ChaosBlade-Box interface. source
- Experiment scenarios
- Scenarios cover basic resources such as CPU, memory, network, disk, processes, kernels and files, as well as multilingual applications and Kubernetes resources. source
- Founded
- 2019 source
- Integrations
- ChaosBlade-Box uses Helm for deployment management and integrates Prometheus monitoring. source
- Intended users
- The project describes its goal as helping enterprises improve system availability during cloud-native adoption. source
- Notable deployment requirement
- The platform installation guide lists Java and MySQL requirements for host deployment, with Ansible and expect needed for automatic probe installation. source
- Platform features
- ChaosBlade-Box provides a unified experiment interface, automated deployment of experiment tools, and hosting for tools including ChaosBlade and LitmusChaos. source
- Purpose
- The project aims to help enterprises address high-availability problems during cloud-native adoption through chaos engineering. source
- Safety controls
- ChaosBlade-Box describes manual stopping and automatic stopping through a configured timeout as policies to help ensure drills are resumed. source
- Support channels
- The project site links to Gitter, Twitter, Slack and a DingTalk community group. source
- What it is
- ChaosBlade is an open-source chaos engineering project comprising the ChaosBlade experiment tool and the ChaosBlade-Box platform. source
Checked against the maker's pages on 29 Sept 2026.