Jikkou
The Resource as Code framework for Apache Kafka. Leveraging GitOps for Kafka at scale!
FreeCLIDevOpsOpen Source1,948 impressions#10 of its week
Jikkou is an open-source GitOps framework for declaratively managing Kafka resources via YAML and CI pipelines.
- for
- Platform, DevOps/SRE, and application teams that operate Apache Kafka clusters.
- pricing
- open source
- license
- Apache-2.0
- 1.2.0-early-accessRelease 1.2.0-early-access15 days ago
- v1.1.0Release v1.1.02 months ago
- 1.1.0-early-accessRelease 1.1.0-early-access2 months ago
Key features
- Stateless reconciliation — Diffs Git definitions against the live cluster and applies only the necessary changes.
- Multi-cluster support — Apply the same YAML across on-prem, Confluent Cloud, Aiven, MSK and other clusters.
- Templating at scale — Jinja templates and environment files let you define hundreds of similar topics efficiently.
- Dry-run mode — Preview exact changes without touching production resources.
- Validation policies — Enforce naming rules, ISR minimums, partition limits, and other policies before apply.
- CLI + REST API — Native command-line tool for CI and an API server for team-wide automation.
Use cases
- Self-service topic and schema provisioning for app teams via pull requests
- Automated drift detection and remediation across multiple Kafka clusters
- Enforcing organizational policies on ACLs, quotas, and connector configurations
Jikkou vs alternatives
 Jikkou |  Daytona |  Keel |  tenv |  Chaterm | |
|---|---|---|---|---|---|
| Best for | GitOps-driven Kafka resource management | One-click dev environment setup | Backend as a service platform | Version manager for IaC tools | Terminal-based infra automation |
| Pricing | Open source | Free | Subscription | Free | Subscription |
| DevHunt upvotes | 0 | 339 | 46 | 58 | 65 |
| Launched | Apr 2025 | May 2024 | Mar 2024 | Jul 2024 | Apr 2026 |
- Jikkou vs Daytona: Daytona focuses on provisioning development environments, not Kafka resource management.
- Jikkou vs Keel: Keel provides backend services and team tools, whereas Jikkou manages Kafka resources via GitOps.
- Jikkou vs tenv: tenv manages Terraform/Tofu versions, while Jikkou manages Kafka resources declaratively.
- Jikkou vs Chaterm: Chaterm automates infra via a terminal UI; Jikkou offers GitOps-driven Kafka configuration.
Jikkou FAQ
How does Jikkou differ from Terraform?+
Terraform provisions the Kafka cluster itself, while Jikkou manages the resources inside the cluster without a state file.
Can Jikkou work with Kubernetes operators like Strimzi?+
Jikkou complements the Strimzi Topic Operator by handling resources it cannot manage, such as schemas, ACLs, and connectors.
What language is used for templating?+
Jikkou uses Jinja templating within YAML files.
Is there a way to see changes before they are applied?+
Yes, the `jikkou diff` command shows a preview of all changes, and a dry-run mode is also available.
How are policies enforced?+
Validation policies like naming conventions and partition limits run during the diff step, blocking invalid changes.
Summarized by DevHunt from jikkou.io · Sep 29, 2026. Details may change; check the official site.
