Qdrant Cloud CLI

qcloud is the official command-line interface for managing Qdrant Cloud. It lets you manage clusters, authentication, and anything the Qdrant Cloud API has to offer—all from your terminal.

Installation

With Homebrew

On macOS and Linux, install from the Qdrant tap:

brew install qdrant/tap/qcloud

Homebrew also installs shell completions for bash, zsh, and fish. Update with brew upgrade qcloud.

From the install script

For systems without Homebrew, such as CI runners, containers, and sandboxed agents:

curl -fsSL https://raw.githubusercontent.com/qdrant/qcloud-cli/main/install.sh | sh

The script installs the latest release for your OS and CPU architecture to ~/.local/bin, after checking the archive against the release’s checksums.txt. Set QCLOUD_VERSION (for example v0.32.0) to pin a release, or QCLOUD_INSTALL_DIR to install somewhere else. It needs curl or wget, sha256sum or shasum, and tar.

From GitHub Releases

Download the latest release from GitHub Releases. Releases are available for macOS and Linux on x86-64 and ARM64, and for Windows on x86-64. The macOS binaries are signed and notarized.

Select the archive that matches your OS and CPU architecture, extract it, and place the qcloud binary somewhere in your PATH (e.g. ~/.local/bin or /usr/local/bin). Each release includes a checksums.txt file with the SHA-256 of every archive.

From Source

With Go installed, you can build and install directly from source:

go install github.com/qdrant/qcloud-cli/cmd/qcloud@latest

Verify the Installation

qcloud version

Quick Start

Before using qcloud, create a management API key and note your account ID from the Qdrant Cloud Console.

# 1. Create a context with your credentials
qcloud context set my-cloud \
  --api-key <YOUR_API_KEY> \
  --account-id <YOUR_ACCOUNT_ID>

# 2. List available cloud providers and regions
qcloud cloud-provider list
qcloud cloud-region list --cloud-provider aws

# 3. Create a cluster by specifying resources (waits until healthy)
#    Use --cpu, --ram, --disk to select a matching package automatically.
qcloud cluster create \
  --cloud-provider aws \
  --cloud-region us-east-1 \
  --cpu 2000m \
  --ram 8GiB \
  --disk 50GiB \
  --name my-cluster \
  --wait

# 4. Describe your new cluster
qcloud cluster describe <CLUSTER_ID>

# 5. Create an API key for it
qcloud cluster key create <CLUSTER_ID> --name my-key

Configuration

qcloud can be configured in three ways, listed here from lowest to highest precedence:

Config File

The config file is stored at ~/.config/qcloud/config.yaml by default. You can override the location with the --config flag. It stores named contexts so you can switch between accounts and environments.

Named Contexts

Named contexts allow you to save and switch between sets of credentials:

qcloud context set my-cloud --api-key <KEY> --account-id <ID>
qcloud context use my-cloud
qcloud context show

Environment Variables

Environment variables override the active context and take the highest precedence:

Pass --json to any command for machine-readable output.

Getting Help

For a full list of available commands, run:

qcloud --help