DanubeData CLI.
Stay in your terminal.

Your infrastructure, one command away. Deploy sites, inspect servers and manage storage from the same terminal you use to build.

  • EU hosted
  • TLS encrypted

The CLI is free. Infrastructure is billed separately at the current platform rates.

Install the CLI
npm install -g @danubedata/cli

Node.js 18 or later. Open source under the MIT license. Resources you provision are billed at their current hosting rates.

What customers say

“As a developer and cloud enthusiast, I’ve tried a lot of infrastructure platforms — but DanubeData genuinely stands out as one of the most intuitive, modern, and reliable cloud services I’ve used. From signup to deployment, everything feels thoughtfully designed and developer-centric. Deploying a VPS, cache, or database instance takes under a minute — and that’s not an exaggeration! Their intuitive dashboard and instant provisioning make launching new services effortless, even if you’re just getting started with cloud infrastructure”

Keoma WrightCEO/Founder at OpenWeb.co.za
Cristian TorzsaCEO at InnovaSoftware SRL
Bo PereiraParis-Brest srl
Read more customer stories

Commands you can put to work

Start with your own resources. These are reusable examples, with no simulated output or promised deployment time.

Install with Node.js 18 or later. Sign in, then inspect your infrastructure before creating anything.

Quick start
npm install -g @danubedata/cli
danube auth
danube whoami
danube vps ls
danube storage buckets ls

# Link an existing static site, then upload its built files.
danube pages link
danube pages deploy --dir ./dist

Built for your shell, ready for your scripts

  • Browser authentication

    Run danube auth, sign in and authorize in your browser. CI runners can use DANUBE_TOKEN instead.

  • JSON for unattended work

    Resource commands accept --json and return a success, data, error and meta envelope on stdout. JSON mode skips prompts and reports missing flags.

  • A project for each invocation

    Use --project to scope one command without changing your saved selection. DANUBE_TEAM_ID sets the project in CI.

  • An explicit completion signal

    Inspect operations or wait for their terminal boolean. The server supplies the polling interval, and a timeout tells you the work is still unfinished.

Read the result. Know the next step.

JSON output gives scripts a common envelope. Completion, retryability and diagnostic verdicts have their own fields.

Success and failures on stdout

Read success, then data or error. API failures can include error.cause.retryable; use that field when deciding whether to retry. A usage error needs a corrected command.

Example of an empty list result
{"success":true,"data":[],"error":null,"meta":{"count":0}}

For rapids diagnose, success describes the call. A successful diagnosis can find a fatal problem and exit with code 1. Check findings[].severity and the exit code.

Wait for explicit completion

data.terminal is the stop condition for operations. poll_after_ms supplies the polling pace. Check the final state and error too: terminal does not mean successful.

operation.wait_timeout means the client’s wait ended before the operation finished. Inspect it again or allow more time.

Read the automation contract
Exit codes for automation
0
Success.
1
Generic or API failure, or a diagnosis that found a fatal problem.
2
Usage error, unknown command or a required flag missing in noninteractive mode.
3
Not authenticated.
4
Resource not found.
5
Confirmation required. Review the action before adding its confirmation flag.
8
Bucket metrics are stale or unavailable.
75
The client stopped waiting for a run or bucket policy change; the work has not necessarily failed.
124
A Rapids run timed out on the server.
130
Cancelled by the user, or a Rapids run was cancelled.

Rapids run waiting and followed run logs can pass through a workload’s own exit code from 1–255. Interpret those codes in the context of the command you ran.

Find your command group

Use danube <group> --help for flags and subcommands. Open a group below to see where it fits in the platform.

Servers and managed services
  • danube vps

    Create, inspect, resize, manage power, reinstall, retrieve passwords and list OS images.

  • danube database

    PostgreSQL, MySQL and MariaDB instances, credentials, DNS, replicas, snapshots and metrics.

  • danube cache

    Redis, Valkey and Dragonfly instances, connection info, DNS, snapshots and metrics.

  • danube queue

    RabbitMQ instances, connection info, power management, automated snapshot settings and metrics.

  • danube apps

    Browse the app catalog and manage app instances, credentials, metrics and logs.

  • danube parameter-groups

    List, create and update database and cache parameter groups.

Shipping and deployment
  • danube pages

    Link and deploy static sites, list revisions, roll back and manage custom domains.

  • danube rapids

    Create, apply and deploy containers; inspect logs, revisions and events; preflight, probe and diagnose.

  • danube registry

    Inspect your push context, verify permission and manage private repositories.

  • danube operations

    Inspect or wait on long-running operations using explicit terminality.

Storage and monitoring
Authentication, projects and CLI settings

Installation and reference

The CLI is published on npm. Its source, command reference and issue tracker are on GitHub.

CLI questions, answered

Authentication, scripts and deployments.

  • Run npm install -g @danubedata/cli with Node.js 18 or later. Then run danube auth for browser login, or danube login for token authentication.

    Link to this answer

Put your terminal to work

Install the CLI, connect your account and use the tools that fit your workflow.

npm install -g @danubedata/cli