Side by side

ChaosBlade vs Krkn

Both stand on chaos engineering platforms. Which one you can start free with, which one lets you read the code, and what each costs once you pay.

ChaosBlade

Free plan APILinuxMac+3

ChaosBlade offers several ways to run experiments and includes stopping policies to help end drills. Platform host deployment has listed prerequisites, while Kubernetes installation uses Helm.

Visit ChaosBlade

Krkn offers several ways to run a wide range of cluster disruption scenarios and evaluate their impact against SLOs. Check its access and runtime requirements, and account for the possibility that some disruptions cannot be automatically recovered.

Visit Krkn

The facts

	ChaosBlade	Krkn
Free plan	Yes	Yes
Open source	Not published	Not published
Runs on	API, Linux, Mac, Self-hosted, Web, Windows	API, Linux, Self-hosted, Web
Lowest paid plan	Free or on request	Free or on request
Plans published	1	1
Maker	Not published	Not published
Website	chaosblade.io	krkn-chaos.dev
On chaos engineering platforms	#2 of 25	#6 of 25

ChaosBlade: what it does well

Covers infrastructure, application and Kubernetes experiment scenarios.
Supports CLI, Kubernetes YAML and CRDs, HTTP calls, and Box.
Box integrates Prometheus monitoring and uses Helm.
Offers manual and timeout-based stopping policies.
Available as a free open-source tool.

What to know first

Host deployment of the platform requires Java and MySQL.
Automatic probe installation also needs Ansible and expect.

Krkn: what it does well

More than 20 chaos scenarios
Validates SLO criteria with Prometheus metrics
Offers CLI, containers, dashboard, and Python options
Can monitor cluster health through Cerberus

What to know first

Requires cluster-admin kubeconfig access
Requires Kubernetes or OpenShift 1.21+
Some scenarios may leave a system unrecoverable
Does not currently adhere to compliance standards

Alternatives to ChaosBlade Alternatives to Krkn The whole list