Krkn vs Tumult
Krkn
krkn-chaos.devTumult
tumult.rsSide by side
| Figure | Krkn | Tumult |
|---|---|---|
| Price from | Free | — |
| Free plan | Yes | — |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | Yes | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 0 |
| Spec score · Chaos Engineering Platforms | 8.5 (#5) | 7.1 (#20) |
| Install options | Installation options include a CLI, pre-built containers, a browser-based dashboard, and a standalone Python program. | The homepage provides a shell installer and a Docker image, and describes Tumult as a static binary with no runtime dependencies. |
| Purpose | Krkn injects deliberate failures into Kubernetes clusters to test their resilience. | Tumult is a Rust-native chaos engineering platform for defining, running, and analyzing experiments that test how systems behave under failure conditions. |
Plans
In their own words
Krkn
Krkn injects deliberate failures into Kubernetes clusters so teams can examine resilience under disruption. Its 20-plus scenarios cover pods, containers, nodes, networks, applications, resources, storage and time. The recommended krknctl command-line tool discovers, runs and coordinates scenarios; other choices include pre-built containers, a browser dashboard and a standalone Python program. Krkn evaluates Prometheus metrics against SLO pass/fail criteria and can review metrics during and after scenarios. Dashboard integrations include Elasticsearch and Grafana, and telemetry can be sent to S3 or Elasticsearch. Cerberus monitors Kubernetes and OpenShift health, providing a go/no-go signal, reports and a metrics API; it can also report failures in Slack. Krkn-AI uses evolutionary algorithms against user-defined objectives to identify experiments. Krkn says it saves recovery state and can restore a cluster, but some disruptive scenarios may leave the target unrecoverable. It is intended for resilience measurement, not security provision, and does not currently adhere to compliance standards. Requirements include Kubernetes or OpenShift 1.21+, cluster-admin kubeconfig access, and Docker 20.10+ or Podman 4.0+.