Skip to documentation
Documentation
StableVerified September 2, 2026
CLI

Install and connect

Put the Kaveon client on a machine, then connect to a local Engine, a private endpoint, or the qualified AKS coordinator.

Install

powershell
irm https://raw.githubusercontent.com/PruthviProdduturi/Kaveon/dev/scripts/install.ps1 | iex
$env:PATH = "$env:LOCALAPPDATA\kaveon\bin;$env:PATH"
kaveon --version
bash
curl -fsSL https://raw.githubusercontent.com/PruthviProdduturi/Kaveon/dev/scripts/install.sh | bash
kaveon --version

Tagged releases publish platform archives and SHA256SUMS. The same client supports Windows x64, macOS Intel and Apple Silicon, and Linux x64.

Local mode

bash
kaveon --local --data-dir /data/warehouse
kaveon --local --data-dir /data/warehouse --catalog OpenSource --schema public

Remote mode

bash
kaveon --server https://engine.example.com \
  --catalog OpenSource --schema public

Use --auth auto for a supplied token or Azure CLI login, --auth azure-cli to require Azure CLI, and --auth microsoft for device sign-in. --auth none is loopback development only.

Qualified AKS connection

powershell
az login
az account set --subscription 4ed07f02-b111-4eea-98ce-1c177d573a51
az aks get-credentials --resource-group kaveon-rg --name kaveon-aks --overwrite-existing
kubelogin convert-kubeconfig -l azurecli
kubectl -n kaveon port-forward service/kaveon 18443:8080 --address 127.0.0.1
kaveon --server https://localhost:18443 --ca-cert .\kaveon-ca.crt --catalog OpenSource --schema public
Keep the port-forward, CA file, and access token private. The coordinator is a trusted service boundary, not a public browser endpoint.