Two purpose-built Kafka backup tools
Kannika Armory is a strong Kubernetes-native backup platform: continuous backup of records and schemas, an operator with CRDs, environment cloning, and commercial support. OSO Kafka Backup covers the same core job but is open source and CLI-first, so it runs with or without Kubernetes. Here is how the two differ.
Both do point-in-time recovery — the difference is elsewhere
Unlike replication tools, both Kannika Armory and OSO Kafka Backup are actual backup-and-restore products. Both take point-in-time copies of Kafka data to object storage and restore to the same or a different cluster. So the comparison is not "backup vs replication" — it is two backup tools with different licensing models and deployment footprints. See the feature comparison for how backups sit against replication approaches like MirrorMaker 2.
Kannika Armory is a commercial, Kubernetes-native platform. It continuously backs up records and schemas, ships an operator with custom resources for GitOps workflows, and adds tooling for environment cloning and cluster migration. It is a licensed product installed into your Kubernetes cluster, with a free trial and commercial support.
OSO Kafka Backup takes scheduled point-in-time backups of topic data, consumer group offsets, and cluster metadata to S3, Azure Blob, GCS, or local disk. Its core is open source (MIT). It ships a CLI and Kubernetes operators — including a Strimzi-native operator — so it runs on Kubernetes or on a plain host with a cron entry.
| Feature | OSO Kafka Backup | Kannika Armory |
|---|---|---|
| Purpose | Backup / restore | Backup / restore |
| Licensing | Open source (MIT) | Commercial (licensed) |
| Point-in-time recovery | Yes | Yes |
| Backup model | Scheduled point-in-time | Continuous / real-time |
| Deployment | CLI + Kubernetes operator | Kubernetes-native operator |
| Runs without Kubernetes | Yes | No |
| Schema Registry backup | Enterprise | Built-in |
| Storage backends | S3, Azure, GCS, local | S3, Azure, GCS, K8s volumes |
| Offset preservation | Built-in | Yes |
| Free trial / free tier | Open source core | Time-limited trial |
When to choose which
Choose OSO Kafka Backup when you want an open source core with no per-cluster licence, you need to back up Kafka that does not run on Kubernetes, or you prefer a CLI you can drop into any scheduler or pipeline. Scheduled point-in-time backups cover disaster recovery, cluster migration, and compliance retention.
Choose Kannika Armory when you are all-in on Kubernetes, want continuous real-time backup rather than scheduled snapshots, need native schema-registry backup without an enterprise tier, and want a commercial support contract behind the product.
If schema-registry backup is your deciding factor on the open source tier, Kannika has the edge — OSO Kafka Backup treats Schema Registry sync as an Enterprise feature. If licensing footprint and running outside Kubernetes matter more, OSO Kafka Backup fits better.
Frequently asked questions
Is OSO Kafka Backup open source and is Kannika Armory?
The core of OSO Kafka Backup is open source under the MIT licence. Kannika Armory is a commercial, proprietary product: a licence is installed into your Kubernetes cluster, with a time-limited free trial available. They differ mainly on licensing model and deployment, not on the basic backup-and-restore job.
Does OSO Kafka Backup require Kubernetes like Kannika Armory?
No. OSO Kafka Backup ships a CLI as well as Kubernetes operators, so it runs on a plain host with a cron schedule or inside Kubernetes. Kannika Armory is Kubernetes-native and runs its operator inside a cluster.
Which tool backs up the Schema Registry?
Kannika Armory includes schema-registry backup natively. In OSO Kafka Backup, Schema Registry sync is an Enterprise feature; the open source core backs up topic data, consumer group offsets, and cluster metadata.
Do both tools support point-in-time recovery?
Yes. Both restore Kafka data to a chosen point in time and can restore to the original cluster or a different one. OSO Kafka Backup uses scheduled point-in-time backups; Kannika Armory backs up continuously and restores within its retention window.
Can OSO Kafka Backup run against a Strimzi-managed cluster?
Yes. OSO Kafka Backup provides a Strimzi-native operator that resolves connection details and credentials from your Strimzi custom resources, alongside a generic operator for Kafka running outside Strimzi.
Ready to protect your Kafka data?
Take your first backup in minutes with the open source CLI, or talk to us about Enterprise features like encryption, RBAC, and audit logging.