Skip to content

Qdrant

Qdrant is a vector database that searches collections of embeddings. It can store extra fields next to each vector for filtering.

Visit Qdrant

What goes into a Qdrant collection?

A collection groups the items you want to search. Each item can have a vector and extra fields such as a document ID, language or account. Qdrant calls those extra fields the payload.

Keep the document ID and version so you can open the current passage. Apply scope based on the signed-in user’s verified access. A tag or a browser-supplied filter does not protect access on its own. Keep privileged database credentials off the browser.

What changes between Qdrant Cloud and a server you run?

Qdrant Cloud Free lists one node with 1 GB RAM, 0.5 vCPU and 4 GB disk for testing. An unused free cluster can be suspended after one week and deleted after four weeks of inactivity if it stays inactive.

If you run Qdrant yourself, you own upgrades, storage and access. Qdrant’s documentation says a self-managed server starts without authentication or encryption by default. Keep it off the network until access controls and encrypted connections are configured. Cloud access controls still need to match what your app’s users are allowed to see.

How do you check that two workspaces stay separate?

On paper, write a cancellation policy for each of two fictional workspaces. Give them similar wording and different notice periods. A reader in one workspace should get only that workspace’s policy.

Check the returned passages, their titles and the cited links. If you later run the exercise, first confirm a disposable private collection, test-only credentials, fictional content and identities, and no live connection or real embedding inputs. Stay with paper if any of those are uncertain.

What does a collection snapshot carry to a new Qdrant server?

A collection snapshot can preserve its data and configuration, including points and payload fields. It excludes collection aliases and has version constraints on the receiving server.

In a distributed deployment, snapshots are taken for each node. Keep the originals, document IDs and access rules separately. Verify the version requirements and restore to a disposable target before counting on a snapshot as your recovery plan.