{
  "manifest_version": "1",
  "slug": "chroma",
  "title": "Chroma",
  "headline": "Self-host Chroma",
  "description": "Run the open-source Chroma vector database on an exe.dev VM, private behind exe.dev login, with keyless embeddings, backups, and a tested way off Chroma Cloud.",
  "category": "databases",
  "tags": [
    "chroma",
    "chromadb",
    "chroma self-host",
    "chroma docker",
    "chroma cloud alternative",
    "chroma cloud migration",
    "vector database",
    "rag",
    "embeddings",
    "qdrant",
    "weaviate"
  ],
  "url": "https://exe.dev/deploy/chroma",
  "markdown_url": "https://exe-staging.dev/deploy/chroma.md",
  "upstream": {
    "website": "https://www.trychroma.com",
    "source": "https://github.com/chroma-core/chroma",
    "docs": "https://docs.trychroma.com",
    "license": "Apache-2.0"
  },
  "example_vm_name": "my-chroma",
  "time": "10 minutes",
  "stack": [
    {
      "name": "Chroma 1.5.9",
      "detail": "The official chromadb/chroma image in Docker Compose, on localhost only",
      "port": 8000,
      "data": "~/chroma/data"
    },
    {
      "name": "HTTP API and API docs",
      "detail": "Chroma's own API and Swagger UI, through the exe.dev proxy",
      "port": 8000
    },
    {
      "name": "Embeddings",
      "detail": "text-embedding-3-small through exe.dev's LLM integration, no API key"
    },
    {
      "name": "Nightly backups",
      "detail": "A tar.gz of the data directory, 14 nights kept",
      "data": "~/chroma/backups"
    }
  ],
  "access": [
    {
      "url": "https://my-chroma.exe.xyz/docs/",
      "who": "private",
      "what": "Chroma's API docs (Swagger UI), behind exe.dev login"
    },
    {
      "url": "https://my-chroma.exe.xyz/",
      "who": "private",
      "what": "The HTTP API, for programs that send an exe.dev VM token"
    },
    {
      "url": "http://localhost:8000/",
      "who": "private",
      "what": "The HTTP API for apps on the VM"
    }
  ],
  "delivers": [
    "Chroma 1.5.9 in Docker, started at boot, listening on localhost only, its data in `~/chroma/data`.",
    "The API and its Swagger docs at `https://\u003cvm\u003e.exe.xyz/`, private behind exe.dev login.",
    "An `exe-docs` collection of exe.dev's documentation, embedded with no API key, and a script that answers questions from it.",
    "A script that copies collections from Chroma Cloud or another Chroma server and checks the copy.",
    "Nightly backups, one restored and checked."
  ],
  "owner_runs_after": [
    "ssh my-chroma.exe.xyz 'cd chroma \u0026\u0026 uv run ask.py \"How do I make my VM public?\"'",
    "ssh exe.dev ssh-key generate-api-key --vm=my-chroma --label=chroma --exp=90d"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20Chroma%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Fchroma.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-chroma.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-chroma.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20Chroma%201.5.9%20in%20Docker%2C%20started%20at%20boot%2C%20listening%20on%20localhost%20only%2C%20its%20data%20in%20%60~%2Fchroma%2Fdata%60.%0A-%20The%20API%20and%20its%20Swagger%20docs%20at%20%60https%3A%2F%2F%3Cvm%3E.exe.xyz%2F%60%2C%20private%20behind%20exe.dev%20login.%0A-%20An%20%60exe-docs%60%20collection%20of%20exe.dev%27s%20documentation%2C%20embedded%20with%20no%20API%20key%2C%20and%20a%20script%20that%20answers%20questions%20from%20it.%0A-%20A%20script%20that%20copies%20collections%20from%20Chroma%20Cloud%20or%20another%20Chroma%20server%20and%20checks%20the%20copy.%0A-%20Nightly%20backups%2C%20one%20restored%20and%20checked.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20For%20initial%20setup%2C%0Afollow%20%22Install%20by%20hand%22%20from%20top%20to%20bottom%2C%20skipping%20VM%20creation%3A%0ADocker%2C%20the%20config%20and%20Compose%20files%2C%20starting%20Chroma%2C%20the%20scripts%20and%0Athe%20exe-docs%20collection%2C%20the%20backup%20timer%2C%20and%20the%20restore%20test.%20The%0Awalkthrough%20sections%20are%20for%20the%20owner%20afterwards%3A%20don%27t%20run%0Achroma-migrate.py%2C%20ask%20for%20a%20Chroma%20Cloud%20key%2C%20set%20up%20Tailscale%2C%0Aintegrations%20or%20Qdrant%2C%20or%20run%20the%20Restore%20or%20Update%20instructions%0Aduring%20initial%20setup.%20Remove%20only%20the%20chroma-restore-test%20container%20and%0A%2Ftmp%2Fchroma-restore%20that%20the%20restore%20test%20creates.%0ALeave%20the%20VM%20private%20and%20do%20not%20reboot.%20Finish%20with%0Ahttps%3A%2F%2F%3Cvm%3E.exe.xyz%2Fdocs%2F%20and%20the%20answer%20ask.py%20gives%20to%20%22How%20do%20I%20make%0Amy%20VM%20public%3F%22.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open%20and%20these%20commands%2C%20which%20only%20I%20can%20run%2C%20from%20my%20own%20computer%20%28with%20this%20VM%27s%20name%20in%20them%29%3A%0A%20%20ssh%20my-chroma.exe.xyz%20%27cd%20chroma%20%26%26%20uv%20run%20ask.py%20%22How%20do%20I%20make%20my%20VM%20public%3F%22%27%0A%20%20ssh%20exe.dev%20ssh-key%20generate-api-key%20--vm%3Dmy-chroma%20--label%3Dchroma%20--exp%3D90d%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/chroma/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Chroma on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/chroma.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-chroma. This VM's name is the output of `hostname`: use it wherever the recipe writes my-chroma. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- Chroma 1.5.9 in Docker, started at boot, listening on localhost only, its data in `~/chroma/data`.\n- The API and its Swagger docs at `https://\u003cvm\u003e.exe.xyz/`, private behind exe.dev login.\n- An `exe-docs` collection of exe.dev's documentation, embedded with no API key, and a script that answers questions from it.\n- A script that copies collections from Chroma Cloud or another Chroma server and checks the copy.\n- Nightly backups, one restored and checked.\n\nRead the whole recipe, including the closed details. For initial setup,\nfollow \"Install by hand\" from top to bottom, skipping VM creation:\nDocker, the config and Compose files, starting Chroma, the scripts and\nthe exe-docs collection, the backup timer, and the restore test. The\nwalkthrough sections are for the owner afterwards: don't run\nchroma-migrate.py, ask for a Chroma Cloud key, set up Tailscale,\nintegrations or Qdrant, or run the Restore or Update instructions\nduring initial setup. Remove only the chroma-restore-test container and\n/tmp/chroma-restore that the restore test creates.\nLeave the VM private and do not reboot. Finish with\nhttps://\u003cvm\u003e.exe.xyz/docs/ and the answer ask.py gives to \"How do I make\nmy VM public?\".\n\nFinish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them):\n  ssh my-chroma.exe.xyz 'cd chroma \u0026\u0026 uv run ask.py \"How do I make my VM public?\"'\n  ssh exe.dev ssh-key generate-api-key --vm=my-chroma --label=chroma --exp=90d\n",
    "prompt_url": "https://exe-staging.dev/deploy/chroma/prompt.txt"
  },
  "published": "2026-11-22",
  "updated": "2026-11-22",
  "verified": "2026-11-22",
  "related": [
    "postgres",
    "mem0",
    "claude-mem",
    "dify",
    "clickhouse",
    "docker-compose"
  ],
  "alternatives": [
    "Chroma Cloud",
    "Pinecone",
    "Qdrant Cloud",
    "Weaviate Cloud"
  ],
  "files": [
    "https://exe-staging.dev/deploy/chroma/ask.py",
    "https://exe-staging.dev/deploy/chroma/chroma-migrate.py",
    "https://exe-staging.dev/deploy/chroma/index-docs.py"
  ]
}
