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.
npm install -g @danubedata/cliNode.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”
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.
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 ./distThis example uses a shared plan from the current catalog. Set SSH_KEY_ID to one of your account’s SSH keys and DANUBE_TEAM_ID to your project ID. Creation provisions a billable resource.
# Inspect available images and existing instances.
danube vps images
danube vps ls
danube --project "$DANUBE_TEAM_ID" vps create \
--name web-server --image ubuntu-24.04 \
--resource-profile nano_shared --cpu-platform amd \
--ssh-key-id "$SSH_KEY_ID" --json
# Replace web-server with your instance name or ID.
danube vps get web-server
danube vps metrics web-server
danube vps stop web-server
danube vps start web-server
danube vps reboot web-serverCreate a managed PostgreSQL database. The version uses the equals form; missing selections are requested interactively. Creation provisions a billable resource.
danube database create --name app-db --provider postgresql \
--version=17 --database-name app \
--profile micro
danube database get app-db
danube database credentials app-db
danube database dns app-db
danube database replicas ls app-db
danube database snapshots ls app-dbCreate a private bucket and access key. Save the returned secret securely. Bucket storage and usage are billed separately.
danube storage buckets ls
danube storage buckets create --name assets --region fsn1 --versioning
danube storage buckets update assets --size-limit 10GB --encryption
danube storage keys create --name deploy-key --scope buckets --bucket assets:readwrite
danube storage keys lsLink an existing site first. outputDir and ignore patterns live in danube.json; --dir overrides the configured directory.
# Set the build output in danube.json.
cat > danube.json <<'JSON'
{
"outputDir": "dist",
"ignore": ["src/**", "*.config.js"]
}
JSON
danube pages link
danube pages deploy
# Start a deployment without waiting for its build.
danube pages deploy --dir ./dist --no-wait
# View revisions before choosing one to restore.
danube pages deployments ls
danube pages deployments rollback "$REVISION"Add your domain, configure the DNS record returned by the CLI, then request verification. TLS is provisioned after verification.
danube pages domains ls
danube pages domains add blog.example.com
# Configure the returned DNS record before this step.
danube pages domains verify blog.example.comSet IMAGE to your push reference and BUILD_ID to a stable key for this change. Keep that key when retrying the same Rapids apply request.
# Confirm project access, then check the image.
danube --project "$DANUBE_TEAM_ID" registry context --json
danube registry verify-push "$REPOSITORY" --json
danube rapids preflight --image "$IMAGE" --json
# Apply provisions or updates a billable container.
danube rapids apply --name api --image "$IMAGE" \
--port 8080 --health-check-path /healthz \
--wait --idempotency-key "$BUILD_ID" --json
# Check serving and inspect findings if necessary.
danube rapids probe api --path /healthz --warm-requests 5 --json
danube rapids diagnose api --jsonA GitHub Actions deployment for an existing site. Save the scoped token, numeric team ID and static site UUID as repository secrets.
name: Deploy to DanubeData
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 22
- run: npm ci && npm run build
- run: npm install -g @danubedata/cli
- run: danube pages deploy --dir ./dist
env:
DANUBE_TOKEN: ${{ secrets.DANUBE_TOKEN }}
DANUBE_TEAM_ID: ${{ secrets.DANUBE_TEAM_ID }}
DANUBE_SITE_ID: ${{ secrets.DANUBE_SITE_ID }}Set OPERATION_ID to the operation or resource ID returned by your request. Read data.terminal instead of guessing completion from a state name.
danube operations inspect "$OPERATION_ID" --json
danube operations wait "$OPERATION_ID" --timeout 30m --json
# data.terminal is the stop condition.
# poll_after_ms is the server-supplied polling interval.
# operation.wait_timeout means the work has not finished.
# It does not mean the operation itself has failed.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.
{"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.
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 vpsCreate, inspect, resize, manage power, reinstall, retrieve passwords and list OS images.
danube databasePostgreSQL, MySQL and MariaDB instances, credentials, DNS, replicas, snapshots and metrics.
danube cacheRedis, Valkey and Dragonfly instances, connection info, DNS, snapshots and metrics.
danube queueRabbitMQ instances, connection info, power management, automated snapshot settings and metrics.
danube appsBrowse the app catalog and manage app instances, credentials, metrics and logs.
danube parameter-groupsList, create and update database and cache parameter groups.
Shipping and deployment
danube pagesLink and deploy static sites, list revisions, roll back and manage custom domains.
danube rapidsCreate, apply and deploy containers; inspect logs, revisions and events; preflight, probe and diagnose.
danube registryInspect your push context, verify permission and manage private repositories.
danube operationsInspect or wait on long-running operations using explicit terminality.
Storage and monitoring
danube storage bucketsCreate and update buckets, configure quotas and versioning, and inspect metrics.
danube storage keysCreate, list, inspect and revoke scoped S3 access keys.
danube storage policyInspect and apply bucket policies, with confirmation for changes.
danube uptimeManage uptime checks and inspect their results.
danube metric-alertsConfigure resource metric alerts and inspect alert history.
Authentication, projects and CLI settings
danube authAuthorize the CLI through browser login.
danube loginAuthenticate with an API token.
danube logoutRemove stored credentials.
danube whoamiShow the authenticated account and its teams.
danube projectList, select, inspect or clear the saved project context.
danube configRead CLI settings and configure automatic updates.
danube upgradeCheck for an update or upgrade the CLI.
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
