| applications | Kindo’s own services, such as api, next, and task-worker-ts. |
| component | Any one thing Kindo deploys: an application or a supporting service. Each component is a Helm release. |
| config | An instance’s config settings, stored in the cluster. See How the config works. |
| config backup | The file kindo config backup writes and kindo restore reads. See Back up and restore. |
| config setting | One named entry in the config, with its value. See the config reference. |
| config template | The file you fill in with your config settings to create the config. See Config template. |
| instance | One Kindo running on one cluster. |
| Kindo CLI | The command-line tool, kindo, that installs and manages Kindo. See Commands. |
| plan | What a command will change, shown before it changes anything. |
| registry login | The username and password for Kindo’s registry. |
| release line | A 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. |
| sandboxes | Where agents run code. See Scaling and resources. |
| secret store | Where Kindo reads its credentials from: Kubernetes Secrets, or your secrets manager. See Secret store. |
| secrets manager | Your 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. |
| superadmin | An 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 dashboard | The separate Kindo app, at superadmin.<domain>, where superadmins manage organizations, models, and keys. See Set up access. |
| supporting services | The services Kindo runs for itself in the cluster, such as Qdrant or Unleash. |
| version | One exact Kindo version, such as 2026.11.2. |