Qdrant Managed Cloud Quickstart
QdrantOfficialPublished by Qdrant
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides essential procedures for getting started with Qdrant Managed Cloud. It covers the lifecycle of a cluster, from choosing between Free, Standard, and Premium tiers to configuring secure connectivity, handling authentication, and managing data indexing. It also addresses common pitfalls such as connection failures, strict mode requirements for filtered requests, and the use of Cloud Inference for embedding generation. The guide includes best practices for transitioning from prototyping to production-ready environments, including backup management, scaling, and security considerations.
What it does
- Explains the differences between Free, Standard, and Premium cloud tiers.
- Provides instructions for creating clusters via the Console or qcloud CLI.
- Details how to authenticate using Database API keys versus Cloud Management Keys.
- Guides users on resolving connection issues and configuring TLS/HTTPS access.
- Explains how to handle strict mode and payload indexing for filtered queries.
- Outlines steps for setting up Cloud Inference and production-readiness checklists.
When to use it
- When setting up a new Qdrant Managed Cloud cluster for the first time.
- When troubleshooting authentication errors or connection failures.
- When a filtered query is rejected due to strict mode requirements.
- When transitioning a prototype to a production-ready deployment.
- When deciding between cluster tiers based on scaling or SLA requirements.
Advantages
- Clarifies the distinction between management and database access keys.
- Provides clear guidance on avoiding common pitfalls like manual replica management.
- Helps users align cluster configuration with production requirements early.
- Offers specific advice for data residency and inference model usage.
Usage examples
- “How do I create a new Qdrant Cloud cluster using the CLI?”
- The agent explains how to use the qcloud CLI to provision a cluster, including the use of the --wait flag to ensure the cluster is healthy before proceeding.
- “Why is my filtered search failing on Qdrant Cloud?”
- The agent identifies that the collection is in strict mode and instructs the user to create a payload index for the filtered field.
- “What is the difference between the Free and Standard tiers?”
- The agent outlines the limitations of the Free tier regarding backups, uptime, and scaling, and explains when to upgrade to Standard or Premium.
- “How do I connect to my cluster securely?”
- The agent provides the correct ports for REST and gRPC, emphasizes the use of TLS, and explains how to use Database API keys for authentication.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/qdrant/qdrant-managed-cloud-quickstart/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip qdrant-managed-cloud-quickstart.zip -d .agents/skills
Documentation by Qdrant
Getting Started with Qdrant Cloud
You've already chosen Qdrant Managed Cloud. If you're still deciding between Cloud, Hybrid Cloud, and self-hosting, use the deployment options skill. On Cloud, every request needs an API key over TLS, new collections run in strict mode, and free clusters are suspended when idle. Some cluster choices can't be undone later.
Choosing and Creating a Cluster
Use when: creating the first cluster, or deciding between Free, Standard, and Premium.
Use the free cluster for prototyping only: a single node with 1 GB RAM and 4 GB disk, no automatic backups, and it's suspended after 1 week without use and deleted after 4 weeks unless reactivated Free clusters
If a node runs out of RAM, the operating system stops the Qdrant process; without high availability, expect disruption until the cluster is scaled up. If it runs out of disk, it can't store new vectors, which can also lead to disruption. Scale the cluster before either happens; on the free tier, that means upgrading to Standard Cluster alerts
Size a Standard cluster before creating it with the sizing skill.
For anything production-facing, enable High Availability: 3 or more nodes and replication factor 2 or more. Without it each shard has a single replica, so upgrades and vertical scaling cause downtime Production-ready cluster
Premium is an account-wide plan with a minimum spend agreed with the Qdrant team. It adds a higher uptime SLA, 24/7 support for severe issues, Multi-AZ clusters, SSO, private network connectivity, and customer-managed encryption keys. Standard already includes scaling, high availability, and backups, so consider Premium if you need one of these Premium tier
Decide on Multi-AZ (Premium) at creation: it can't be enabled later, and node counts must then be multiples of 3 Production-ready cluster
Memory and disk can both be scaled down, but the cluster must still fit its data. Memory can't go below current usage. Scaling disk down replaces nodes one at a time, without downtime, but it takes a while and adds disk I/O load until it's done Vertical scaling Scaling down disk
Paying through the AWS, GCP, or Azure Marketplace limits cluster creation to paid clusters in that provider's regions. To run clusters in other regions or on other providers, create a separate account with a different payment method Billing
Use separate accounts to separate clusters across teams or environments, such as dev and prod: each account has its own clusters, permissions, and payment method Accounts
Create clusters in the Cloud Console, or through the Cloud API, either by calling it directly or via the qcloud CLI, Terraform, or Pulumi. All the Cloud API options need a Cloud Management Key. Provisioning takes time; qcloud's
--waitflag blocks until the cluster is healthy Console Cloud API qcloud Terraform PulumiFor a step-by-step walkthrough in the Console, from sign-up to a free cluster, a first collection, and a first search, see the Cloud quickstart
Can't Connect or Authenticate
Use when: the first request to the cluster fails, or an SDK reports an authentication or TLS error.
Send a Database API key with every REST and gRPC request, as the
api-keyheader orAuthorization: Bearer. Each key works only on the cluster it was created in. It is shown once at creation; if it's lost, create a new one Authentication Database API keysDon't use a Cloud Management Key here. Those authorize the Cloud platform API for managing clusters and backups, not the database Cloud API
Connect over HTTPS to the cluster endpoint: port 6333 or 443 for REST, 6334 for gRPC. For working connection code in each language, use the clients-sdk skill snippet search Cluster access
Test access with a single request to the cluster root URL with the key in the header Test cluster access
Read-only and collection-scoped keys are denied some actions, such as creating collections. Check what a key was granted Table of access
Keys expire after 90 days by default; an empty expiration means no expiry Create Database API keys
If IP restrictions are configured, clients outside the allowed ranges can't reach the cluster Client IP restrictions
Filtered Requests Rejected on Cloud
Use when: retrieving or updating points by a filter is rejected on a Cloud collection.
New Cloud collections run in strict mode, which rejects retrieving or updating by a filter on a payload field without an index. Create a payload index for each filtered field rather than disabling strict mode; a Cloud collection can have up to 100 payload indexes Cloud defaults Payload index
Generating Embeddings on Qdrant Cloud
Use when: the user wants Qdrant to create embeddings (Cloud Inference) instead of running a model themselves.
Cloud Inference lets Qdrant embed and store or search in the same API call. It's on by default for clusters created after July 7, 2025; enabling it on an older cluster restarts the cluster
Use a Qdrant-hosted model, or an external provider through Qdrant, which needs your own API key from that provider Embedding models
Free models run in the US, even for EU-region clusters. With EU data-residency requirements, use a paid Qdrant-hosted model or embed before upload.
Before Relying on the Cluster
Use when: moving from a prototype to something users or other services depend on.
Set a backup schedule (Standard clusters only). Restoring into the same cluster also rolls back its CPU, memory, node count, and Qdrant version, and the cluster is unavailable during the restore. You can restore into a new cluster instead Backups
Adding nodes doesn't change a collection's replication factor. After moving to more nodes, check each existing collection and set its replication factor to 2 or more; on Cloud, its shards are then replicated or dropped automatically to match, so change only the collection config and don't add or drop replicas yourself; see the horizontal scaling skill Replication
Create collections with at least twice as many shards as nodes so they can spread as the cluster grows; see the horizontal scaling skill Production-ready cluster
Cloud caps a cluster at 1000 collections. For many tenants, use the multitenancy skill instead of a collection per tenant Multitenancy
Before upgrading the cluster's Qdrant version, follow the version upgrade skill
When removing a user, revoke the Database API keys and Cloud Management Keys they created: keys keep working after their creator is gone Removing a user
Run through the Production checklist before launch.
What NOT to Do
Disable strict mode to make an unindexed filter pass instead of indexing the field
Restore a backup into the live cluster without expecting its size and version to roll back
Send EU-resident text to a free inference model, which runs in the US
Remove a user without revoking the API keys they created
Drop or move replicas by hand after changing a collection's replication factor; the Cloud platform does it, and manual calls race with it
Files
- ATTRIBUTION.mdAdded by AutoGineer874 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md10.6 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2026 Qdrant Solutions GmbH
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an API key, Needs Node.js
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Qdrant
- Publisher
- Qdrant (Official)
- Source
- qdrant/skills · skills/qdrant-managed-cloud-quickstart · commit 9f55f6a
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Qdrant.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download qdrant-managed-cloud-quickstart.zip