Skip to main content

Aspire hosting integration for Chroma: a Chroma container in the AppHost. Built from the Chroma integration merged into the Aspire Community Toolkit, until the toolkit publishes its packages. Community project, not affiliated with Chroma.

Total Downloads
0
0
Published
Oct 14, 2026
7d ago

Get Started

dotnet add package ChromaDotNet.Aspire.Hosting --version 0.2.8
ProductVersions
.NET
net10.0net8.0net9.0

README

ChromaDotNet

ChromaDotNet.Aspire.Hosting

Adds a Chroma container to an Aspire AppHost: the chromadb/chroma:1.5.9 image, with a health check on /api/v2/heartbeat.

Website: chromadotnet.org

dotnet add package ChromaDotNet.Aspire.Hosting
var chroma = builder.AddChroma("chroma")
    .WithDataVolume();

builder.AddProject<Projects.ApiService>("api")
    .WithReference(chroma)
    .WaitFor(chroma);

WithDataVolume and WithDataBindMount mount /data, where Chroma keeps its database.

AddChroma takes an optional port, the host port of the container; without it the port is assigned at run time. The resource gives the connection string Endpoint=http://{host}:{port} and the connection properties Host, Port and Uri. The methods are exported to TypeScript AppHosts too (addChroma, withDataVolume, withDataBindMount), as in the example.

This is the Chroma hosting integration accepted in the Aspire Community Toolkit (CommunityToolkit/Aspire#2219), published by ChromaDotNet until the toolkit ships it as CommunityToolkit.Aspire.Hosting.Chroma. The API and namespaces are the same, so moving to that package only changes the package reference. Community project, not affiliated with Chroma.

Downloads by Version

Not enough data for chart

Similar & Alternative Packages

Hand-picked matching NuGet libraries based on tags & ecosystem

Depended On By

Find packages that declare this package as a dependency. NuGet does not provide a reverse-dependency endpoint, so candidates are checked on demand.

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 3 target frameworks; confirm the exact target used by your application.

Related Guides & Workflows

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