https://github.com/qdrant/qcloud-cli
The Command Line Interface for Qdrant Cloud
https://github.com/qdrant/qcloud-cli
Last synced: 23 days ago
JSON representation
The Command Line Interface for Qdrant Cloud
- Host: GitHub
- URL: https://github.com/qdrant/qcloud-cli
- Owner: qdrant
- License: apache-2.0
- Created: 2026-03-09T16:17:58.000Z (2 months ago)
- Default Branch: main
- Last Pushed: 2026-04-14T10:11:49.000Z (about 1 month ago)
- Last Synced: 2026-04-14T11:27:24.870Z (about 1 month ago)
- Language: Go
- Size: 518 KB
- Stars: 16
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Agents: AGENTS.md
Awesome Lists containing this project
README
# qcloud - The CLI for Qdrant Cloud
The official command-line interface for managing Qdrant Cloud
`qcloud` is the CLI for [Qdrant Cloud](https://qdrant.tech/). It lets you manage clusters, authentication and anything the API has to offer with a terminal experience.
[](https://asciinema.org/a/ijIHYveH9SCBZEBX)
## Disclaimer
`qcloud` currently is under heavy development. The output and command shape can heavily change from version to version.
## Installation
### From GitHub Releases
Download the latest release from [GitHub Releases](https://github.com/qdrant/qcloud-cli/releases).
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`).
> **macOS:** The binary is not signed. If macOS blocks it, run `xattr -d com.apple.quarantine qcloud` after extracting. In the future we will sign the binary so that this step is not needed.
> If `~/.local/bin` is not in your `PATH`, you can use `/usr/local/bin` instead (requires `sudo`).
### From source
With Go installed, you can build and install directly from source:
```sh
go install github.com/qdrant/qcloud-cli/cmd/qcloud@latest
```
### Verify
```sh
qcloud version
```
## Quick Start
Before using `qcloud`, create a management API key and note your account ID from the [Qdrant Cloud UI](https://cloud.qdrant.io).
```sh
# 1. Create a context with your credentials
qcloud context set my-cloud \
--api-key \
--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
# 5. Create an API key for it
qcloud cluster key create --name my-key
```
## Configuration
`qcloud` can be configured in three ways, listed here from lowest to highest precedence:
**Config file** at `~/.config/qcloud/config.yaml` (override with `--config`). Stores named contexts so you can switch between accounts and environments.
**Named contexts** allow you to save and switch between sets of credentials:
```sh
qcloud context set my-cloud --api-key --account-id
qcloud context use my-cloud
qcloud context show
```
**Environment variables** override the active context:
| Variable | Description |
|---------------------------|---------------------------------------------|
| `QDRANT_CLOUD_API_KEY` | API key for authentication |
| `QDRANT_CLOUD_ACCOUNT_ID` | Account ID to operate against |
| `QDRANT_CLOUD_ENDPOINT` | API endpoint URL (defaults to Qdrant Cloud) |
| `QDRANT_CLOUD_CONTEXT` | Name of the context to use |
Pass `--json` to any command for machine-readable output.
## Getting Help
Found a bug or something not working as expected? [Open an issue](https://github.com/qdrant/qcloud-cli/issues/new) on GitHub and include:
- The `qcloud` version (`qcloud version`)
- The command you ran and the output you got
- Your OS and architecture
## Acknowledgements
`qcloud` is inspired by and partially based on [hetznercloud/cli](https://github.com/hetznercloud/cli). Thank you to the Hetzner Cloud team and contributors for building such a well-designed CLI that we could learn from.
## Contributing
If you are interested in contributing follow the instructions in [CONTRIBUTING.md](./CONTRIBUTING.md)