Server
danube up standalone|cluster|edge: start a nodedanube mcp: MCP server for AI agents (stdio, or--http ADDR)danube console: web console backend (REST +/mcp)
One binary does everything: danube starts nodes, sends messages, manages topics and runs the cluster. Learn its shape once and every command feels familiar.
danube # overview of every command, plus a quick startdanube up # the three node modes, with examplesdanube topic --help # any command or subcommanddanube produce -h # short summary instead of full helpRunning danube alone only prints the overview. It never starts a server; that is always danube up <mode>.
Server
danube up standalone|cluster|edge: start a nodedanube mcp: MCP server for AI agents (stdio, or --http ADDR)danube console: web console backend (REST + /mcp)Messaging
danube produce <TOPIC> -m MSG: publish messagesdanube consume <TOPIC> -s SUB: stream messagesResources
danube topic: create, describe, peek, branch, subscriptions, schemas, DLQdanube namespace: namespaces and their policiesdanube schema: schema registry subjectsCluster operations
danube cluster: membership, storage, WAL, load managerdanube broker: list, unload, rebalance brokersdanube auth: roles, bindings, tokensdanube apply -f FILE: reconcile a desired-state manifestUtilities
danube context: saved connection profilesdanube completions <shell>: shell completion scriptsdanube version: print the versionDeep dives: Messaging, Resources, Cluster operations, MCP server.
Every client command (everything except up, context, completions and version) talks to a broker at http://127.0.0.1:6650 by default. Point it elsewhere with the shared connection flags:
--endpoint URL: broker address. https:// turns on TLS.--context NAME: use a saved profile.--token JWT: bearer token for secured clusters.--tls: force TLS.--tls-ca FILE: CA certificate used to verify the broker.--tls-cert FILE, --tls-key FILE: client certificate and key for mTLS.--tls-domain NAME: server name to verify (default localhost).danube topic list --namespace default --endpoint https://danube.example.com:6650 --tls-ca ./ca.pemEach flag has a matching environment variable: DANUBE_ENDPOINT, DANUBE_CONTEXT, DANUBE_TOKEN, DANUBE_TLS, DANUBE_TLS_CA, DANUBE_TLS_CERT, DANUBE_TLS_KEY, DANUBE_TLS_DOMAIN.
Typing endpoints and certificates gets old fast. Save them once:
# Save two profiles and make "local" the current onedanube context add local --endpoint http://127.0.0.1:6650 --usedanube context add prod --endpoint https://danube.example.com:6650 --tls-ca ./ca.pem --token "$TOKEN"
danube context list # * marks the current contextdanube context use prod # switchdanube context show # settings of the current context, token maskeddanube topic list --namespace default --context local # one-off overrideContexts live in ~/.config/danube/contexts.toml (or $DANUBE_CONFIG_DIR/contexts.toml). They are client-side only; the server never reads them. Also available: danube context current and danube context delete <NAME>.
danube up reads a few environment variables, handy in containers: DANUBE_DATA_DIR, DANUBE_LISTEN, DANUBE_ADVERTISED_ADDR, DANUBE_SEED_NODES, DANUBE_AUTH, DANUBE_JWT_SECRET, and for edge nodes DANUBE_EDGE_NAME, DANUBE_CLOUD_ENDPOINT, DANUBE_CLOUD_TOKEN. See Broker configuration for every flag.
--dry-run shows what would happen and changes nothing:
danube up cluster --data-dir /var/lib/danube --single-node --dry-run # print the resolved node configdanube apply -f desired_state.yaml --dry-run # print the reconcile plandanube broker rebalance --dry-run # preview topic movesdanube completions bash > /etc/bash_completion.d/danubedanube completions zsh > "${fpath[1]}/_danube"danube completions fish > ~/.config/fish/completions/danube.fishPowerShell and Elvish are supported too: danube completions powershell, danube completions elvish.
danube version # or: danube -V