HariKube is a Kubernetes-native middleware platform that offloads custom resource and microservice data from ETCD to scalable databases like MySQL and PostgreSQL. It enhances Kubernetes with better performance, data isolation, and horizontal scalability.

No. HariKube operates transparently beneath the Kubernetes API. Your application continues to use standard Kubernetes CRDs and APIs without any code changes.

Yes. HariKube is designed for production-grade Kubernetes clusters, providing scalability, reliability, and compliance-friendly data isolation out of the box.

HariKube supports pluggable backends, including MySQL, PostgreSQL. For more information please visit the full list of databases page.

Yes. It enables per-namespace and per-resource-type database isolation, making it ideal for secure, multi-tenant Kubernetes platforms.

HariKube uses a middleware to handle workload-aware routing based on resource type, namespace, or key-level rules.

While it’s possible, HariKube is optimized for production use. Developers can continue using stock Kubernetes in development, as HariKube integrates seamlessly at deployment time.

Yes. HariKube fully respects Kubernetes-native mechanisms such as RBAC, admission webhooks, events, and policies, maintaining full compatibility with your existing cluster setup.