Skip to main content
net8.0

Qdrant vector database support for Aspire.

Published
Dec 4, 2025
10mo ago
Total Downloads
156.6K
156,588

Install

dotnet add package Aspire.Hosting.Qdrant --version 13.0.2
ProductVersions
.NET
net8.0

README

Aspire.Hosting.Qdrant library

Provides extension methods and resource definitions for an Aspire AppHost to configure a Qdrant vector database resource.

Getting started

Install the package

In your AppHost project, install the Aspire Qdrant Hosting library with NuGet:

dotnet add package Aspire.Hosting.Qdrant

Usage example

Then, in the AppHost.cs file of AppHost, add a Qdrant resource and consume the connection using the following methods:

var qdrant = builder.AddQdrant("qdrant");

var myService = builder.AddProject<Projects.MyService>()
                       .WithReference(qdrant);

Connection Properties

When you reference a Qdrant resource using WithReference, the following connection properties are made available to the consuming project:

Qdrant server

The Qdrant server resource exposes the following connection properties:

Property Name Description
GrpcHost The gRPC hostname of the Qdrant server
GrpcPort The gRPC port of the Qdrant server
HttpHost The HTTP hostname of the Qdrant server
HttpPort The HTTP port of the Qdrant server
ApiKey The API key for authentication
Uri The gRPC connection URI, with the format http://{GrpcHost}:{GrpcPort}
HttpUri The HTTP connection URI, with the format http://{HttpHost}:{HttpPort}

Aspire exposes each property as an environment variable named [RESOURCE]_[PROPERTY]. For instance, the Uri property of a resource called db1 becomes DB1_URI.

Additional documentation

Feedback & contributing

https://github.com/dotnet/aspire

Qdrant, and the Qdrant logo are trademarks or registered trademarks of Qdrant Solutions GmbH of Germany, and used with their permission.

Changes from Previous Version

v13.0.1v13.0.2
Deprecation Removed
Deprecation notice was removed in this version.

Adoption Assessment

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

Compatibility metadata lists 1 target framework; confirm the exact target used by your application.The published metadata declares 25 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

Related Guides & Workflows

Learn how to evaluate, integrate, or audit this package in your .NET project.