Self-Managed Kindo Overview
Self-Managed Kindo (SMK) is a version of the Kindo platform designed to be fully deployed and managed by your organization within its own compute environment.
Why Self-Managed?
-
Flexible Deployment — Deployed via Kubernetes Helm Chart, SMK supports cloud-managed Kubernetes environments (e.g., AWS EKS), on-premises Kubernetes instances, and hybrid managed platforms such as OpenShift and Rancher.
-
Compliant Infrastructure — Deploy into protected environments pre-configured for Governance and Regulatory Compliance (GRC) requirements, enabling Kindo to interact with data under regulations such as PCI-DSS and GDPR.
-
Full Data Privacy — Only your organization has access to audit logs, metrics, and usage patterns generated by Kindo and its users.
Deployment Architecture
Self-Managed Kindo consists of:
- Kindo Applications — Core services packaged by Kindo (API, Next.js frontend, LiteLLM proxy, workers)
- Peripheries — Third-party and open-source services (Unleash feature flags, SSOReady, Qdrant, Cerbos)
- Infrastructure Services — PostgreSQL, Redis, RabbitMQ, S3-compatible storage
Getting Started
Follow these guides in order to deploy Self-Managed Kindo: