Self-host Chroma with Levelrail

A developer-friendly embedding database for AI applications, served over a simple HTTP API. Open to anyone who can reach it, so reach it from other services in this project at chroma:8000, or attach a domain only behind Basic Auth. Not published on the host.

  • Authorchroma-core
  • LicenceApache-2.0
  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host Chroma

  1. Pull the images

    One image is pulled on your server.

    Show images
    • ghcr.io/chroma-core/chroma:1.0.0
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 8000.

  3. Fill in the secrets

    3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Chroma requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
8000
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
Apache-2.0, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Chroma. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Chroma docs page.

Deploy Chroma your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Chroma from the CLI

levelrail-cli templates deploy chroma --name my-chroma

Deploy Chroma with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/chroma/deploy

Chroma configuration

Chroma services

ServiceImagePortsVolumes
chroma ghcr.io/chroma-core/chroma:1.0.0 8000 chroma_data -> /data

Chroma environment variables

VariableServiceValue
ANONYMIZED_TELEMETRY chroma Preset by the template
IS_PERSISTENT chroma Preset by the template
PERSIST_DIRECTORY chroma Preset by the template

Ports and volumes

Ports
8000
Volumes
1 named mount: chroma_data -> /data

Chroma FAQ

How much memory does Chroma need?

The catalog lists about 512 MiB of memory for Chroma.

Does Chroma run on arm64?

For Chroma, an arm64 image is published; amd64 is image published.

What licence is Chroma under?

Chroma is licensed under Apache-2.0, which is permissive, with few conditions on reuse.

Does Chroma need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Chroma use?

Chroma listens on port 8000 inside the stack.

Where does Chroma keep its data?

In a named volume: chroma_data mounted at /data.

Can I deploy Chroma on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id chroma for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/chroma-core/chroma:1.0.0 is what you deploy there.

levelrail-cli templates deploy chroma --name my-chroma