qdrant: A Rust repository from SethWen

Vector Search Engine for the next generation of AI applications

Qdrant (read: quadrant ) is a vector similarity search engine. It provides a production-ready service with a convenient API to store, search, and manage points - vectors with an additional payload. Qdrant is tailored to extended filtering support. It makes it useful for all sorts of neural-network or semantic-based matching, faceted search, and other applications.

Qdrant is written in Rust 🦀, which makes it fast and reliable even under high load.

With Qdrant, embeddings or neural network encoders can be turned into full-fledged applications for matching, searching, recommending, and much more!

Demo Projects

Semantic Text Search 🔍

The neural search uses semantic embeddings instead of keywords and works best with short texts. With Qdrant and a pre-trained neural network, you can build and deploy semantic neural search on your data in minutes. Try it online!

Similar Image Search - Food Discovery 🍕

There are multiple ways to discover things, text search is not the only one. In the case of food, people rely more on appearance than description and ingredients. So why not let people choose their next lunch by its appearance, even if they don’t know the name of the dish? Check it out!

Extreme classification - E-commerce Product Categorization 📺

Extreme classification is a rapidly growing research area within machine learning focusing on multi-class and multi-label problems involving an extremely large number of labels. Sometimes it is millions and tens of millions classes. The most promising way to solve this problem is to use similarity learning models. We put together a demo example of how you could approach the problem with a pre-trained transformer model and Qdrant. So you can play with it online!

API

REST

Online OpenAPI 3.0 documentation is available here. OpenAPI makes it easy to generate a client for virtually any framework or programing language.

You can also download raw OpenAPI definitions.

gRPC

For faster production-tier searches, Qdrant also provides a gRPC interface. You can find gRPC documentation here.

Clients

Qdrant offers the following client libraries to help you integrate it into your application stack with ease:

Features

Filtering and Payload

Qdrant supports any JSON payload associated with vectors. It does not only store payload but also allows filter results based on payload values. It allows any combinations of should, must, and must_not conditions, but unlike ElasticSearch post-filtering, Qdrant guarantees all relevant vectors are retrieved.

Rich Data Types

Vector payload supports a large variety of data types and query conditions, including string matching, numerical ranges, geo-locations, and more. Payload filtering conditions allow you to build almost any custom business logic that should work on top of similarity matching.

Query Planning and Payload Indexes

Using the information about the stored payload values, the query planner decides on the best way to execute the query. For example, if the search space limited by filters is small, it is more efficient to use a full brute force than an index.

SIMD Hardware Acceleration

Qdrant can take advantage of modern CPU x86-x64 architectures. It allows you to search even faster on modern hardware.

Write-Ahead Logging

Once the service confirmed an update - it won't lose data even in case of power shut down. All operations are stored in the update journal and the latest database state could be easily reconstructed at any moment.

Distributed Deployment

Since v0.8.0 Qdrant supports distributed deployment. In this mode, multiple Qdrant machines are joined into a cluster to provide horizontal scaling. Coordination with the distributed consensus is provided by the Raft protocol.

Stand-alone

Qdrant does not rely on any external database or orchestration controller, which makes it very easy to configure.

Usage

Docker 🐳

Build your own from source

docker build . --tag=qdrant/qdrant

Or use latest pre-built image from DockerHub

docker pull qdrant/qdrant

To run the container, use the command:

docker run -p 6333:6333 qdrant/qdrant

And once you need a fine-grained setup, you can also define a storage path and custom configuration:

docker run -p 6333:6333 \
    -v $(pwd)/path/to/data:/qdrant/storage \
    -v $(pwd)/path/to/custom_config.yaml:/qdrant/config/production.yaml \
    qdrant/qdrant

/qdrant/storage - is a place where Qdrant persists all your data. Make sure to mount it as a volume, otherwise docker will drop it with the container.
/qdrant/config/production.yaml - is the file with engine configuration. You can override any value from the reference config

Now Qdrant should be accessible at localhost:6333.

Docs 📓

The best place to start is Quick Start Guide
The Documentation
Use the OpenAPI specification as a reference
Follow our Step-by-Step Tutorial to create your first neural network project with Qdrant
Assess Qdrant's performance in our benchmarks
Check out our further plans in v1.0 Roadmap

Contacts

Join our Discord channel
Follow us on Twitter
Subscribe to our Newsletters
Write us an email info@qdrant.tech

Building something special with Qdrant? We can help!

Contributors ✨

Thanks to the people who contributed to Qdrant:

_{Andrey Vasnetsov} 💻	_{Andre Zayarni} 📖	_{Joan Fontanals} 💻	_trean 💻	_Konstantin 💻	_{Daniil Naumetc} 💻	_{Viacheslav Poturaev} 📖
_{Alexander Galibey} 💻	_HaiCheViet 💻	_{Marcin Puc} 💻	_{Anton V.} 💻	_{Arnaud Gourlay} 💻	_{Egor Ivkov} 💻	_{Ivan Pleshkov} 💻
_Daniil 💻	_{Anton Kaliaev} 💻	_{Andre Julius} 💻	_{Prokudin Alexander} 💻	_{Tim Eggert} 💻	_{Gabriel Velo} 💻	_{Boqin Qin(秦伯钦)} 🐛
_{Russ Cam} 💻