Krkn

6.4easy start · #9 of 23
in Chaos Engineering Platforms

Free to practise onnot on record
Free trialnot on record
Well documentedyes
Runs where you worknot on record

Runs on api, Linux, self-hosted, Web.

Visit site Alternatives

Krkn is ranked #9 of 23 in chaos engineering platforms on The Geeks Club. It runs on API, Linux, Self-hosted, Web.

Compared on chaos engineering platforms

Free plan: Yes
Kubernetes support: Yes
Cloud fault injection: Yes
Network fault injection: Yes
Deployment model: self_hosted
Blast-radius controls: Yes

Best Krkn alternatives

See all 20

Reliably 0 of 4 in the starter kit Lesson 17.4 Chaos Toolkit 0 of 4 in the starter kit Lesson 27.3 ChaosBlade 0 of 4 in the starter kit Lesson 37.3 Chaos Mesh 0 of 4 in the starter kit Lesson 47.2 LitmusChaos 0 of 4 in the starter kit Lesson 57.1 Gremlin 0 of 4 in the starter kit Lesson 66.9

The record

Purpose: Krkn injects deliberate failures into Kubernetes clusters to test their resilience.
Scenarios: The site lists more than 20 chaos scenarios covering pods, containers, nodes, networks, applications, resources, storage, and time.
CLI: krknctl discovers, runs, and orchestrates chaos scenarios, and is the recommended way to run Krkn.
Deployment options: Krkn offers a CLI, pre-built container images, a browser-based dashboard, and a standalone Python program.
Integrations: The dashboard supports Elasticsearch and Grafana integration, and Krkn can send telemetry to S3 or Elasticsearch.
Metrics and SLOs: Krkn can validate SLO pass/fail criteria with Prometheus PromQL queries and review metrics during and after chaos scenarios.
Monitoring: Cerberus monitors Kubernetes and OpenShift cluster health and exposes a go/no-go signal, reports, and a metrics API.
Slack integration: Cerberus supports reporting failures in Slack.
Krkn AI: Krkn-AI uses evolutionary algorithms and user-defined objectives such as SLOs and application health checks to identify impactful chaos experiments.
Rollback: The site says Krkn saves recovery state before changes and can automatically restore the cluster if chaos goes wrong.
Security scope: Krkn's security self-assessment says Krkn is not a security provider; it is designed to measure application or cluster resilience through controlled disruptions.
Security documentation: The security self-assessment lists a software bill of materials for Krkn, krkn-lib, and krknctl, and says a security-insights.yml should be added to the roadmap.
Notable limits: krkn-hub runs one scenario type per execution; running multiple scenario types in one execution requires the standalone Krkn installation.
Runtime requirement: The standalone Python installation requires a Python 3.9 environment and manual dependency management.

Where it ranks on The Geeks Club

Best Chaos Engineering Platforms in 2026#9 of 23

Is Krkn yours?

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.

Claim it free Promote Krkn

Sources

krkn-chaos.dev· checked 5 Oct 2026
krkn-chaos.dev/docs/installation/· checked 5 Oct 2026
krkn-chaos.dev/docs/cerberus/· checked 5 Oct 2026
krkn-chaos.dev/docs/krkn_ai/· checked 5 Oct 2026
krkn-chaos.dev/docs/security/· checked 5 Oct 2026