4f18519099
* [1.19] Document language-neutral BM25 text processing (#2445)
* Break Inference page into several pages
* Edits
* Document short query optimization in Cloud Inference
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* [1.19] Document language-neutral BM25 text processing
Replaces the deprecated `language: "none"` workaround with the new explicit
API: `stemmer: {"type": "none"}` to disable stemming and `stopwords: {}`
(empty StopwordsSet) to disable stopword removal.
Updates the language-neutral snippet for all seven client languages and
refreshes the Stemming and Stopwords + Language-neutral sections in
text-search.md with a deprecation callout for the old approach.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Document that stemming and stopword removal are disabled by default for payload indexes
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
* Edits
* The multilingual tokenizer doesn't do lemmatization
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* Document `max_disk_usage_percent` for Strict Mode (#2504)
* Document max_disc_usage_percent.
* Generate MD version for the snippets.
* Rephrase sentence.
* [1.19] Documentation for the Turbo4 datatype (#2517)
* Add 'turbo4' section to Vectors docs
* Edit existing datatypes sections
* Update outdated 'Vector Datatypes' section on the Collections page
* Edit
* Documentation for the slice filtering condition (#2529)
* [1.19] Documentation for per-query IDF statistics (#2526)
* Documentation for per-query IDF statistics
* Clarify that IDF is calculated per shard
* Review feedback
* Document `X-Qdrant-Route-Affinity` header for deterministic read routing (#2541)
* Document X-Qdrant-Route-Affinity header for deterministic read routing.
* Address feedback.
* Address feedback.
* Revert "Document `max_disk_usage_percent` for Strict Mode (#2504)" (#2582)
This reverts commit 460ee971ff.
* [1.19] Documentation for resource quotas (#2586)
Document the global quota API from qdrant/qdrant#10035, which replaces the
per-collection strict mode knobs for memory and disk with a single cluster-wide
quota.
New page, ops-configuration/quotas.md (weight 7, between Configuration and
Administration):
- Configuring quotas via storage.quotas, QDRANT__STORAGE__QUOTAS__* env vars,
and PUT /quotas, with the parameter reference
- Configuration precedence: the API wins once used anywhere in the cluster, and
a joining peer receives the config through consensus instead of reading its
own file
- What happens when a limit is reached: the full node's replica is excluded and
marked dead, the write still succeeds at write_consistency_factor
acknowledgements, and clients see HTTP 507 only when no replica can accept it
- Which operations stay allowed, the release margin, GET /quotas for finding the
full node, and the quota_exceeded metric plus the /telemetry quota field
Supporting changes:
- configuration.md: add the storage.quotas block
- monitoring.md: add quota_exceeded to Application Metrics, and note the
/telemetry quota field
- security.md: add get quotas and set quotas to the JWT access table
- common-errors.md: new Insufficient storage (HTTP 507) entry
- faq/qdrant-fundamentals.md: entry on writes rejected with HTTP 507
- administration.md: mark max_resident_memory_percent deprecated as of 1.19.0
- ops-configuration/_index.md: add the new page
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Test code snippets against 1.19
* Document prefix match filtering condition (#2512)
* Document prefix match filtering condition.
* Add generated files.
* Address feedback.
* Address feedback.
* [1.19] Remove links to docs for removed APIs (#2596)
* Remove links to docs for removed APIs
* Add links to new end endpoints
* Use title case for all headers
* [1.19] Add new 'Memory Tiers' page under 'Configuration' (#2510)
* Add new 'Memory Tiers' page under 'Configuration'
* Change doc structure
* Edits
* Review feedback
* [1.19] Memory tiers: existing page updates (#2535)
* Link Vector Storage section to Memory Tiers
* Update collections.md and hnsw-and-quantization snippet for Memory Tiers
* Update indexing.md for Memory Tiers, add sparse-vector-index default snippet
* Update quantization.md and its snippets for Memory
Tiers
* Update storage.md and its snippets for Memory Tiers
* Update configuration.md for Memory Tiers
* Update administration.md Low Memory Mode section for Memory Tiers
* Update optimize.md and its snippets for Memory Tiers
* Cross-link memory-usage.md fields to Memory Tiers
* Update read-write-contention.md RAM scaling note for Memory Tiers
* Update capacity-planning.md for Memory Tiers
* Update production-checklist.md storage section for Memory Tiers
* Update what-is-qdrant.md Storage bullet for Memory Tiers
* Update cloud-getting-started.md cost-optimization tip for Memory Tiers
* Update create-cluster.md disk sizing note for Memory Tiers
* Update bulk-upload.md Upload Directly to Disk section for Memory Tiers
* Note deprecated legacy params in large-scale-search.md benchmark config
* Fix missed Update Vector Parameters section and sparse-index description for Memory Tiers
* Release blog for v1.19 (#2553)
* Initial commit
* Review feedback
* Add 'Resharding Progress' section to Web UI Enhacements
* Add preview images
* Add missing section image
* Added link to Qdrant Advisor agent skill
* Add links; small edits
* Remove max_disk_usage_percent entry
* Add Resource Quotas entry
* Update release date
* Fix create-payload-index/keyword-with-prefix/rust.rs issue
* Fix create-collection/with-memory-tiers/csharp.cs issue
* Don't publish the blog post yet
* Remove blog post from this PR
---------
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: István Zoltán Szabó <istvan.zoltan.szabo@qdrant.com>
2.8 KiB
title, short_description, description, weight, partition, aliases
| title | short_description | description | weight | partition | aliases | |
|---|---|---|---|---|---|---|
| Getting Started | Get started with Qdrant Managed Cloud: prepare access, size your cluster, deploy, and prepare a workload for production. | Onboarding guide for Qdrant Managed Cloud — set up your account, size and create clusters, and prepare a production-ready vector search deployment. | 205 | deploy |
|
Getting Started with Qdrant Managed Cloud
Welcome to Qdrant Managed Cloud! This document contains all the information you need to get started.
Prerequisites
Before creating a cluster, make sure you have a Qdrant Cloud account. Detailed instructions for signing up can be found in the Qdrant Cloud Setup guide. Qdrant Cloud supports granular role-based access control.
You also need to provide payment details. If you have a custom payment agreement, first create your account, then contact our Support Team to finalize the setup.
Premium Plan subscribers can enable single sign-on (SSO) for their organizations. To activate SSO, please reach out to the Support Team at https://support.qdrant.io/ for guidance.
Cluster Sizing
Before deploying any cluster, consider the resources needed for your specific workload. Our Capacity Planning guide describes how to assess the required CPU, memory, and storage. Additionally, the Pricing Calculator helps you estimate associated costs based on your projected usage.
Creating and Managing Clusters
After setting up your account, you can create a Qdrant Cluster by following the steps in Create a Cluster.
Preparing for Production
For a production-ready environment, consider deploying a multi-node Qdrant cluster (at least three nodes) with replication enabled. More details are available in the Distributed Deployment guide. For more information on how to create a production-ready cluster, see our Vector Search in Production article.
If you are looking to optimize costs, you can reduce memory usage through Quantization or by moving vectors to the cold memory tier.
Infrastructure as Code Automation
Qdrant Cloud can be fully automated using the Qdrant Cloud API. This allows you to create, manage, and scale clusters programmatically. You can also use our Terraform Provider to automate your Qdrant Cloud infrastructure.