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

Config reference

Each entry describes one config setting from the config template. A config setting marked required has no default and must be set. To change a config setting after the instance is installed, see How the config works.

Required. The domain Kindo is served under. Each public address is a name under this domain, such as app.example.com for the domain example.com, unless you give it its own address under How people reach Kindo.

Required. The email address of the first superadmin. The install prints this person’s key once.

Required. The registry Kindo’s charts and images come from.

Config settingRequiredDefaultWhat it sets
hostNoregistry.kindo.aiThe registry’s address. It can include a path under the registry, such as mirror.example.com/kindo. Charts and images then come from that path.
usernameYesThe username Kindo gave you.
passwordYesThe password Kindo gave you.

Optional. Moves the Kindo web app, webhooks or file downloads to their own address. Every address you leave out keeps its default.

Config settingDefaultWhat it sets
apphttps://app.<baseDomain>Where people open Kindo. It can include a path.
webhookshttps://api.<baseDomain>Where outside services send webhooks. It can include a path.
storagehttps://storage.<baseDomain>Where browsers download files. Azure Blob Storage only, and it can’t include a path. For S3, publicEndpoint under storage sets it.

Each value is a full URL starting with https. Plain http is accepted only for localhost, a .localhost name or a loopback IP address. When Kindo creates the Ingress, the web app and webhooks addresses can’t include a path.

Optional. Has Kindo create an Ingress for every public address. Without it, you provide your own routing.

Config settingRequiredDefaultWhat it sets
classNameYesThe IngressClass to use.
annotationsNoNoneAnnotations added to every Ingress. Kindo sets alb.ingress.kubernetes.io/group.order and alb.ingress.kubernetes.io/healthcheck-path itself, so the config refuses them.
externalDnsNofalseWhen true, adds an external-dns hostname annotation to each Ingress.
tlsNoNo TLSHow TLS certificates are provided: one of certManager, acm or secret.

The choices for TLS:

ChoiceConfig settingWhat it sets
certManagerclusterIssuerThe cert-manager ClusterIssuer that issues the certificates.
acmcertificateArnThe ARN of the ACM certificate. Works only with className set to alb.
secretcertificate, privateKeyYour own certificate: the PEM certificate, then any intermediates, and its unencrypted PEM private key. Kindo serves it on every host, so it must cover all of them. Renewing it replaces both values with kindo config edit, then kindo config apply.

Where Kindo keeps its passwords and API keys. Each store takes the config settings below.

Edit the config to change the store before installing. After that, only moving the secret store changes it. Once an instance uses your secrets manager, its config settings can’t change. A move of the store waits for an install that didn’t finish.

StoreConfig settingRequiredWhat it sets
kubernetesThe default. Keeps them in Kubernetes Secrets in the cluster.
vaultaddressYesThe Vault server’s URL.
pathNoThe path in Vault. Defaults to secret.
authYeskubernetes with a Vault role, or token with a secretName.
awsSecretsManagerregionYesThe AWS region of the secrets.
authYespodIdentity, assumeRole with a roleArn, or accessKey with a secretName.
azureKeyVaultvaultUrlYesThe key vault’s URL.
tenantIdYesThe Azure tenant ID.
authYesworkloadIdentity with a managed identity’s clientId, or servicePrincipal with a secretName.

A Vault role or an Azure managed identity is bound to this ServiceAccount:

system:serviceaccount:kindo-system:kindo-secret-store

AWS pod identity and assumed roles use the AWS credentials of the External Secrets Operator.

A secret name refers to a Kubernetes Secret in this namespace:

kindo-system

Its keys are:

Secrets managerKeys
Vaulttoken
AWS Secrets Manageraccess-key-id, secret-access-key
Azure Key Vaultclient-id, client-secret

See Secret store for setting up your secrets manager.

Optional.

Config settingDefaultWhat it sets
storageClassThe cluster’s default StorageClassThe StorageClass for Kindo’s data volumes. You can’t change it after installing.
sandboxNodePoolA nodeSelector and tolerations that place agent sandboxes on their own nodes.

Required. The PostgreSQL servers Kindo creates its databases on. Each server takes an address and an administrator login that can create databases and roles. After installing, you can’t move a database to another server: its host and port stay as they were.

ServerRequiredWhat it holds
mainYesKindo’s databases.
auxiliaryNo, recommended for productionThe databases of Kindo’s supporting services. Without it they go on main.
hatchetNo, recommendedHatchet’s database. Hatchet runs Kindo’s background jobs. Without it Hatchet uses auxiliary, or main if there is none.

All three servers take the same config settings:

Config settingRequiredDefaultWhat it sets
hostYesThe server’s address.
portNo5432The server’s port.
tlsNoencryptencrypt uses TLS without checking the certificate. verify uses TLS and checks the certificate against public certificate authorities only. none uses no TLS.
admin.usernameYesThe administrator login.
admin.passwordYesThe login’s password.
admin.databaseNopostgresThe database the login connects to.

Required. Your Redis server.

Config settingRequiredWhat it sets
urlYesThe connection URL, including the password if the server has one.

Required. Where Kindo keeps uploaded files: S3 or S3-compatible storage, or Azure Blob Storage. Set exactly one of the two below.

Config settingRequiredDefaultWhat it sets
bucketYesThe bucket’s name.
regionNoThe bucket’s region.
authYesaccessKey with an accessKeyId and secretAccessKey, irsa with a roleArn for an AWS role Kindo’s pods assume, or podIdentity to use the pods’ own AWS credentials.
endpointNoFor MinIO, GCS or a gateway in front of another store: the store’s URL.
publicEndpointNoThe URL browsers download from, when endpoint is reachable only inside the cluster. Needs endpoint.

With an IRSA role, the role’s trust policy must allow these ServiceAccounts:

system:serviceaccount:api:api
system:serviceaccount:task-worker-ts:task-worker-ts
system:serviceaccount:kindo-system:kindo-preflight
Config settingRequiredWhat it sets
accountYesThe storage account’s name: 3 to 24 lowercase letters and digits.
containerYesThe container’s name: 3 to 63 lowercase letters, digits and hyphens, starting and ending with a letter or digit.
authYesworkloadIdentity with a managed identity’s clientId, or accountKey with the storage account’s access key.

With workload identity, the managed identity holds the Storage Blob Data Contributor role on the account and a federated credential for the S3 gateway’s ServiceAccount:

system:serviceaccount:kindo-s3proxy:s3proxy

Browsers download files from the storage name under the domain unless you change the storage address under How people reach Kindo.

Required. The mail relay that sends invites, sign-in codes and alerts.

Config settingRequiredDefaultWhat it sets
hostYesThe relay’s address.
portNo587The relay’s port. On port 465 the connection uses TLS from the start. On any other port it upgrades with STARTTLS when the relay offers it.
authYeslogin with a username and password, or none for a relay that allows Kindo by its source address.
fromEmailYesThe sender’s address.
fromNameNoKindoThe sender’s name.
tlsServerNameNoThe name to check the relay’s certificate against, when the certificate doesn’t cover host.

Required. One of:

ChoiceWhat it sets
bringYourOwnYour broker, with its connection url.
bundledHas Kindo run a broker in the cluster.

Kindo runs a single broker with no failover, so Kindo can’t queue work while it restarts. If you switch from your own broker to Kindo’s, Kindo starts with an empty broker and doesn’t move work still queued on yours.

Optional. Qdrant is Kindo’s vector search. Kindo runs it in the cluster unless you bring your own server.

ChoiceWhat it sets
bundledHas Kindo run it in the cluster.
bringYourOwnYour server, with its url and its apiKey if it has one.

Optional. Speaches is Kindo’s speech-to-text. Kindo runs it in the cluster unless you turn it off.

ChoiceWhat it sets
bundledHas Kindo run it in the cluster.
noneTurns it off.

Optional. Models aren’t added here: superadmins add every model in the superadmin dashboard after the install. This entry lets Kindo reach a model provider through a cloud identity instead of access keys. It supports an IAM role for AWS Bedrock.

Config settingRequiredDefaultWhat it sets
bedrock.auth.irsa.roleArnYesThe IAM role Kindo assumes. Its trust policy must allow the ServiceAccount system:serviceaccount:litellm:litellm.
bedrock.regionNoThe cluster’s regionWhere Kindo calls Bedrock models that don’t name their own region.

Optional. The integrations to turn on, by catalog name. Kindo refuses unknown names and config settings when the config is saved. To see the names:

Terminal window
kindo integrations list
Config settingDefaultWhat it sets
enabledfalseTurns the integration on.
clientId, clientSecretThe OAuth client. An OAuth2 integration needs both before users can connect it.
scopesThe integration’s own scopesThe OAuth scopes to request. OAuth2 integrations only.

An integration that doesn’t use OAuth2 takes only the first config setting above.

Optional. Turns on web search and web page reads for agents.

Config settingWhat it sets
apiKeyA Tavily API key.

Optional. A Google OAuth client, which adds Google sign-in. Set both config settings or neither.

Config settingWhat it sets
clientIdThe OAuth client ID.
clientSecretThe OAuth client secret.

Optional. Sends audit events to a syslog receiver.

Config settingRequiredDefaultWhat it sets
syslog.hostYesThe receiver’s address.
syslog.portNo514The receiver’s port.
syslog.transportNoudptls, tcp or udp. With tls, caPem holds the PEM certificate of the authority that signed the receiver’s certificate, unless a public authority signed it.