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

Install Kindo

IfDo this
Your workstation has less than 2 GiB of memoryBefore you run any Kindo command, lower concurrency in your shell with export KINDO_CONCURRENCY=2. If a command still runs out of memory, set it to 1.
You use your own secrets managerGive Kindo access to it and create its entries, as Secret store describes.
You reach AWS Bedrock with an IAM roleSet up the role, as AI models describes.

Your workstation is the machine you run the Kindo CLI from. It needs these tools:

ToolVersionNote
kubectl1.32+
helm4+
Helm’s diff plugin3.15.0+
helmfile1.2+
bash, curl, jq, opensslany
python3anyMust be on your path even if the CLI runs on a Python of its own
Python3.11+For the CLI itself
uvanyRecommended for installing the CLI
psqlanyOnly for opening a database prompt or resetting a database

Installing the CLI needs PyPI or your PyPI mirror. If the workstation can reach neither, ask Kindo support for the CLI’s dependencies.

MinimumRecommended
CPU2 vCPU, with steady performance2 vCPU, not burstable
Memory2 GiB, or 1 GiB with lower concurrency4 GiB
Free disk2 GiB10 GiB
NetworkReaches the cluster’s API server and the registryIn the same region or network as the cluster

Don’t use a burstable virtual machine that throttles: once it has used up its CPU credits, an upgrade can take hours.

Check the version of any diff plugin you already have:

Terminal window
helm plugin list

Remove a version earlier than 3.15.0:

Terminal window
helm plugin uninstall diff

Install the plugin if you don’t have it or you removed it. Helm checks plugin signatures and can’t check a plugin installed straight from its Git repository, so the command skips that check. To install a signed release instead, follow helm-diff’s installation steps.

Terminal window
helm plugin install https://github.com/databus23/helm-diff --version v3.15.15 --verify=false

Show the cluster your context points at:

Terminal window
kubectl cluster-info

Check your permissions. The answer must be yes:

Terminal window
kubectl auth can-i create namespace --all-namespaces

Each CLI installs its own version. In the commands below, replace the version placeholder with the version you want, such as 2026.11.0.

Log in with the registry username and password Kindo provided:

Terminal window
helm registry login registry.kindo.ai --username '<registry-username>'

Download the CLI:

Terminal window
download="$(mktemp -d)"
helm pull oci://registry.kindo.ai/kindo-cli/kindo-cli --version <version> --untar --untardir "$download"

Check the download. On Linux:

Terminal window
(cd "$download/kindo-cli" && sha256sum -c SHA256SUMS)

On macOS:

Terminal window
(cd "$download/kindo-cli" && shasum -a 256 -c SHA256SUMS)

Install it as the user who runs it, not as root.

With uv (recommended), install the CLI:

Terminal window
uv tool install --force "$download"/kindo-cli/kindo_cli-*.whl

Check its version. It should report the version you downloaded.

Terminal window
kindo --version

If it reports another version, or the command isn’t found, put uv’s tool folder first on your path:

Terminal window
export PATH="$HOME/.local/bin:$PATH"

Without uv, do the rest of this step instead. Check that Python is 3.11 or newer:

Terminal window
python3 --version

Install with uv instead if it’s older.

Create a Python environment for the CLI. On Debian or Ubuntu, install the Python venv package first:

Terminal window
sudo apt-get install python3-venv
Terminal window
python3 -m venv "$HOME/.kindo-cli"

Install the CLI into it:

Terminal window
"$HOME/.kindo-cli/bin/pip" install "$download"/kindo-cli/kindo_cli-*.whl

Put the CLI on your path by adding its folder to the front:

Terminal window
export PATH="$HOME/.kindo-cli/bin:$PATH"

Check its version. It should report the version you downloaded.

Terminal window
kindo --version

Have these ready:

  • Service addresses and logins. For everything on Infrastructure: the address and login for each.
  • Base domain. The domain Kindo’s addresses sit under.
  • Superadmin email. The superadmin signs in with codes sent to it.
  • Registry login. The username and password for the Kindo registry that Kindo provided.
  • Routing, DNS, and TLS. Ready as Routing, DNS, and TLS lists them.
  • Object storage sign-in. An access key, or a cloud identity such as an IAM role.

Create your config one of two ways.

To answer questions, run this, then skip to Turn off response buffering for chat:

Terminal window
kindo config init

To fill in a template, do the rest of this step:

Save the config template:

Terminal window
kindo config init --template > config.yaml

Fill it in beside the Config reference. Replace each example value with your own, and delete the optional settings you don’t use, such as the secret store and model access settings if they don’t apply. Keep the file out of version control: once it’s filled in, it holds credentials.

Fill in your routing. With Kindo-managed ingress, uncomment the ingress section and set these:

Config settingSet it to
classNameYour ingress controller’s IngressClass, such as nginx, alb or kong.
annotationsAnnotations for every Ingress, such as load-balancer settings, or {}. With className: alb, set alb.ingress.kubernetes.io/group.name so every host shares one load balancer.
externalDnstrue to have external-dns publish your DNS records.
tls.certManager.clusterIssuerYour cert-manager cluster issuer.
tls.secret.certificate, tls.secret.privateKeyOr your certificate, followed by any intermediates, and its unencrypted private key, both in PEM.
tls.acm.certificateArnOr, with className: alb, your AWS Certificate Manager certificate.

Keep one TLS choice. If your load balancer or gateway serves its own certificate, delete the TLS section. For a full example for your controller, see Ingress, DNS, and TLS.

With your own routing, leave the ingress section commented out.

Save your config to the cluster:

Terminal window
kindo config init --file config.yaml

If it refuses because values in angle brackets are left, replace each one it lists with your own and run it again.

Delete your config template once it’s saved.

With Kindo-managed ingress, turn off response buffering for chat, or chat responses are cut short. Open the config:

Terminal window
kindo config edit

Add the values for your controller. For ingress-nginx:

overrides:
helmValues:
api:
ingress.annotations.nginx\.ingress\.kubernetes\.io/proxy-buffering: 'off'
ingress.annotations.nginx\.ingress\.kubernetes\.io/proxy-read-timeout: '3600'
ingress.annotations.nginx\.ingress\.kubernetes\.io/proxy-send-timeout: '3600'

For Kong, in milliseconds:

overrides:
helmValues:
api:
ingress.annotations.konghq\.com/read-timeout: '3600000'
ingress.annotations.konghq\.com/write-timeout: '3600000'

For any other controller, see Streaming chat responses.

Check your infrastructure first, if you want to:

Terminal window
kindo preflight

Install Kindo:

Terminal window
kindo install

Confirm the test email to the superadmin arrived before you rely on sign-in codes. To skip it, run this instead:

Terminal window
kindo install --no-test-email

Store your superadmin key. It’s printed once, at the end of the output. Store it in your password manager. If you lose it, or it expires, sign in to the superadmin dashboard and create a new key under Keys > New key.

If a warning counts failed steps, run the command the output names.

If Flagsmith keeps crashing during its setup, its database usually rejects its password or can’t be reached. Fix that, then run the command again.

If installing stops partway, fix the cause and run the command again with the same CLI.

Check the result. Status should report Kindo installed and healthy, and the health check should report nothing critical.

Terminal window
kindo status
kindo doctor

If it doesn’t, run the command the output names.

As soon as installing finishes, even with warnings, back it up. It asks for a passphrase. Store the backup apart from the passphrase.

Terminal window
kindo config backup --output kindo-$(date +%F).bundle

Copy the flags:

Terminal window
kindo feature-flags migrate

Answer yes only if the question names your cluster.

If the copy says some flags aren’t served yet, wait a few minutes and run the copy again.

If the copy tells you to create flags in Flagsmith, create them, then run the copy again. Check any other flag it lists in Flagsmith.

Switch Kindo’s applications to Flagsmith:

Terminal window
kindo config apply

Answer yes only if it changes just the four applications that read feature flags: api, next, credits, and task-worker-ts. They switch to Flagsmith. If it changes anything else, answer no and contact Kindo support. When it finishes, it reports four changes.

Next, set up access.