Skip to content
These docs are a preview of Self-Managed Kindo 2026.11, an upcoming release.

Your own data center

Requirements and sizing and Infrastructure give the versions each service needs.

Kindo needsWhat to runNotes
KubernetesAny conformant clusterSee Storage setup
PostgreSQLPostgreSQL on your own serversSee PostgreSQL setup
RedisRedis on your own servers, standalone
RabbitMQRabbitMQ on your own servers, or one Kindo runs in the clusterKindo’s is a single broker with no failover; see RabbitMQ
Object storageAny store that serves the S3 APIIf it runs in the cluster, it is published on its own hostname
Mail relayYour own relayWith a username and password, or trusting the cluster’s addresses. See Email
Secret store (optional)Kubernetes Secrets, or VaultSee Secret store
AI modelsModels you host, such as with vLLMReachable from the cluster. See AI models
Container imagesYour own registry, as a mirrorSee Image setup

The cluster has a default StorageClass, and the sandbox nodes have storage for agent sandboxes. See Kubernetes cluster.

The Hatchet settings live in the PostgreSQL configuration file. A reload applies them, except one that needs a restart.

FileSetting that needs a restart
postgresql.confautovacuum_max_workers

Kindo’s images and charts are mirrored into your own registry, which the config template names. Each new version is copied into the mirror before an upgrade.