Qdrant Cloud through Squiid

What Qdrant Cloud is

Qdrant is a vector search engine written in Rust and available both as open source and as a managed cloud. Its distinguishing features are filtering and memory economics: payloads attached to each point can be queried with nested conditions and combined with vector similarity in a single request, and scalar or binary quantization compresses vectors so a large collection fits in far less RAM. It supports named vectors for multiple embeddings per point, sparse vectors for hybrid search, and snapshots for backup and migration. Collections can be sharded and replicated across nodes, and the same REST and gRPC interfaces are used whether you run it locally or in the cloud.

For AI-coded products Qdrant is the option when the retrieval query has real structure. Searching only within a tenant, a date range, a document type and a permission set, while still ranking by similarity, is a filtering problem as much as a vector problem. The open-source core also means the same engine runs locally in a container during development and in the cloud in production, which keeps an agent's test fixtures honest. Rust and Python clients are first class, which suits pipelines where the ingestion job and the serving app are written in different languages.

Why connect it through Squiid

Qdrant Cloud is on the Squiid roadmap. When it is connected, Squiid will provision the cluster, hold the API key and the cluster URL, and route requests through https://api.squiid.io/v1/qdrant/... with Authorization: Bearer $SQUIID_API_KEY, with the official clients working by base URL swap (gateway convention). Cluster cost and usage will pass through at Qdrant's listed price on your single monthly Squiid invoice, with no markup, and rotating your Squiid key will cut off every agent and service that was querying the collection.

• One account, one key, one bill, one dashboard. Qdrant Cloud sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Qdrant Cloud credentials. Your code carries SQUIID_API_KEY, so QDRANT_URL, QDRANT_API_KEY, QDRANT_COLLECTION never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Qdrant Cloud costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Qdrant cluster with the key held by Squiid
• Payload filtering combined with vector similarity
• Quantization to reduce memory and cost
• Hybrid dense and sparse search
• Qdrant list pricing, no markup

How to connect Qdrant Cloud

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces QDRANT_URL, QDRANT_API_KEY, QDRANT_COLLECTION
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/qdrant/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Qdrant Cloud charges per hour for cluster size with storage included in the tier, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Qdrant Cloud usage, with no markup and no per-request margin.

Qdrant Cloud has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Qdrant Cloud usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: collections are snapshotted and restored into a cluster in your own Qdrant Cloud account. Squiid never owns your code, your schema or your domain, and the gateway speaks Qdrant Cloud's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Qdrant Cloud through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Qdrant Cloud usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.