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

Glossary

TermMeaning
applicationsKindo’s own services, such as api, next, and task-worker-ts.
componentAny one thing Kindo deploys: an application or a supporting service. Each component is a Helm release.
configAn instance’s config settings, stored in the cluster. See How the config works.
config backupThe file kindo config backup writes and kindo restore reads. See Back up and restore.
config settingOne named entry in the config, with its value. See the config reference.
config templateThe file you fill in with your config settings to create the config. See Config template.
instanceOne Kindo running on one cluster.
Kindo CLIThe command-line tool, kindo, that installs and manages Kindo. See Commands.
planWhat a command will change, shown before it changes anything.
registry loginThe username and password for Kindo’s registry.
release lineA Kindo release as a whole, such as 2026.11. It covers the first version, 2026.11.0, and every patch after it. Release notes and the support schedule use release lines; steps that name the exact thing you run use versions. See Releases and support.
sandboxesWhere agents run code. See Scaling and resources.
secret storeWhere Kindo reads its credentials from: Kubernetes Secrets, or your secrets manager. See Secret store.
secrets managerYour organization’s own product for keeping credentials, such as Vault, AWS Secrets Manager, or Azure Key Vault. Kindo’s secret store can use it. See Secret store.
superadminAn admin of the whole instance, who signs in to the superadmin dashboard. An instance can have several. Installing creates the first one from the superadmin email in the config.
superadmin dashboardThe separate Kindo app, at superadmin.<domain>, where superadmins manage organizations, models, and keys. See Set up access.
supporting servicesThe services Kindo runs for itself in the cluster, such as Qdrant or Unleash.
versionOne exact Kindo version, such as 2026.11.2.