Qdrant Managed Cloud Quickstart

Organization

qdrant

qdrant-managed-cloud-quickstart

Getting a first Qdrant Managed Cloud cluster running and connected safely: Free, Standard, and Premium tiers, choices that can't be changed later, creating clusters from the Console or the qcloud CLI, Database API keys, ports and TLS, strict mode on new collections, Cloud Inference, and what to set before relying on a cluster. Use when someone says 'getting started with Qdrant Cloud', 'create a Qdrant Cloud cluster', 'is the free tier enough', 'do I need the Premium tier', 'create a cluster with qcloud', 'my free cluster was suspended', 'can't connect to Qdrant Cloud', 'which API key do I use', 'filter works locally but fails on Cloud', or 'Cloud Inference'.

Overview

Publisher	qdrant
Repository	`skills`
Skill name	`qdrant-managed-cloud-quickstart`
Stars	262
Forks	31
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by qdrant on GitHub. Read the source before you install it.

Installation

Install the Qdrant Managed Cloud Quickstart AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/qdrant/skills/tree/main/skills/qdrant-managed-cloud-quickstart
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/qdrant/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/qdrant-managed-cloud-quickstart .claude/skills/qdrant-managed-cloud-quickstart

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Qdrant Managed Cloud Quickstart in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Qdrant Managed Cloud Quickstart on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Qdrant Managed Cloud Quickstart is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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
Disk can't be scaled down. Memory can be, but not below current usage Vertical scaling
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 --wait flag blocks until the cluster is healthy Console Cloud API qcloud Terraform Pulumi
For 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-key header or Authorization: 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 keys
Don'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 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

Frequently asked questions

What does the Qdrant Managed Cloud Quickstart AI skill do?

Why use Qdrant Managed Cloud Quickstart on TypingMind?

Because you install it once and use it with any model. Qdrant Managed Cloud Quickstart is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Qdrant Managed Cloud Quickstart in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/qdrant/skills/tree/main/skills/qdrant-managed-cloud-quickstart. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Qdrant Managed Cloud Quickstart?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Qdrant Managed Cloud Quickstart?

As many as you like. As long as a model supports skills, you can use Qdrant Managed Cloud Quickstart with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Qdrant Managed Cloud Quickstart AI skill free?

Yes. It is published on GitHub by qdrant under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Testing

openclaw

OrganizationPopular

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Wizard

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar…

Deployment Patterns

Flujos de trabajo de despliegue, patrones de pipeline CI/CD, contenedorización Docker, health checks, estrategias de rollback y listas de verificación de preparación para producción de aplicaciones…

Docker Patterns

Patrones de Docker y Docker Compose para desarrollo local, seguridad de contenedores, networking, estrategias de volúmenes y orquestación de múltiples servicios.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Getting Started with Qdrant Cloud

Choosing and Creating a Cluster

Can't Connect or Authenticate

Filtered Requests Rejected on Cloud

Generating Embeddings on Qdrant Cloud

Before Relying on the Cluster

What NOT to Do

Frequently asked questions

Related AI Skills

Set up your own AI workspace now