Qdrant stores vectors and metadata used by search, recommendation, and retrieval systems. A self-hosted deployment can become a sensitive data service even when the public page is minimal or the product has no visible application marker. That makes measurement discipline important.
A count-only ZoomEye run on 2026-11-21 returned zero for app="Qdrant" and 59 for title="Qdrant". Both used sub_type=all, page 1, and page size 1. The application field did not establish a fingerprint in this observation. The title field found a small set of candidate pages. The result is not evidence that zero Qdrant deployments exist. It is evidence that this exact application query did not match the index during this collection.
Qdrant's security documentation is direct about the self-hosted default. Open-source deployments are not secure by default, can be open to all network interfaces, and have no authentication configured until the operator sets it. API keys, TLS, network binding, and audit logging are explicit production steps. That makes an exposed self-hosted Qdrant service a meaningful review target even when the UI is not a polished management console.
Start with the data API. Qdrant uses REST and gRPC ports. An unauthenticated API can expose collection names, point data, search results, and collection changes. If a deployment is behind a reverse proxy, verify that the proxy protects both the REST and gRPC paths and that internal peer communication is not reachable from application networks. The documentation distinguishes the API key, read-only key, and granular JWT-based access keys. Use scoped keys where available and keep the admin key out of query-only services.
The title-only evidence should be treated as a lead, not a confirmed product identity. A page may contain the word Qdrant in documentation, a blog post, or a comparison table. Do not send collection queries, test API keys, or attempt to write points. For an owned deployment, the operator can confirm the process, listener, configuration, and TLS state from the host and deployment records.
A useful baseline includes network binding, API key presence, TLS termination, gRPC exposure, snapshot and backup endpoints, and the identity of every application that holds a write key. Check whether the service accepts requests from the internet, from an application subnet, or only from a local socket. If the answer is not documented, the deployment has an inventory gap.
ZoomEye adds value by showing where a product fingerprint is absent as well as where it is present. The operator should record the failed application query alongside the positive title query and explain the decision. That is more accurate than turning an empty app result into a claim about deployment count.
Qdrant can be secured. The work is to prove that the deployed service uses those controls and that the data API is not reachable by unintended clients.
Exact query: title="Qdrant"
Open the normalized ZoomEye search