Skip to content
← All services

Databases

Managed Chroma on your own cluster

The vector store most RAG tutorials start on, behind the API the chromadb clients already speak.

Created inside a project, beside the apps that use it. Each project gets its own instance, storage and credentials.

A recent addition. It installs today, and the console marks it as new until it has run on a customer's cluster.

01What it does

Chroma, run for you

Chroma 1.3, 1.4 or 1.5 on Anyport's own chart.

Collections of embeddings with metadata filtering and similarity search, behind the API every chromadb client already speaks. If the prototype ran against a local Chroma, this is the same thing with a volume and a URL your apps are bound to.

A single small process. A collection's index is held in memory once queried, so the size decides how large a collection stays fast. Changing the version restarts the server; Chroma migrates its data forward and there is no supported way back, and the settings say so before you do it.

02Options

What you choose

What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.

Sizes
small 1Gi, medium 4Gi, large 8Gi of memory
Storage
10Gi by default, chosen once
Versions
1.5.9 (default), 1.4.1 or 1.3.7
Pause
Yes; the volume is kept

03Binding

What your app receives

Bind it to an app and these arrive as environment variables. The values are generated once into a secret and reach the app from there, rather than as something you copy.

  • CHROMA_HOST
  • CHROMA_PORT
  • CHROMA_URL

04Adding it

Add Chroma to a project

The same four steps as every service in the catalog.

  1. 01Open a project and go to Services.
  2. 02Pick it from the catalog and choose its options. Only the size is required; everything else has a default.
  3. 03Create it. Anyport installs it into the project's namespace, generates its credentials into a secret there, and tracks its health.
  4. 04Bind it to an app. The connection details arrive as environment variables, and rotating the credential never means editing an app.
Open the console →How services work →

Also under Databases