Component
core/datastore/chroma
A Chroma vector database. Stores embeddings with their documents and metadata in named collections and answers nearest-neighbour queries over them through Chroma's HTTP API, so an application that retrieves reference material by similarity is wired here rather than to a general-purpose store. Collections are created through that API at runtime; the component declares the server, not its contents. Exports its host, port and protocol via the uses topology. The server checks no credential: at 1.5.9, the release this component runs by default, any client that reaches its address reads and writes every collection. Both Recipes therefore publish it only inside the Release — a ClusterIP Service on Kubernetes, the compose network locally — and a Release that exposes it further puts something that authenticates clients in front of it. Realized two ways, both self-hosted and both fetching nothing: reach for the Helm Recipe on Kubernetes, which synthesizes a StatefulSet with a persistent volume, and for the Compose Recipe for local development. Its Recipes are verified by their rendered output, not by a started server storing and querying vectors.
Provenance
- Content digest
- sha256:af981aed131769886e56c2643700eaa18218246ad61ed9e35d21149a802d1646
- Published
- 2026-11-10T10:10:28Z
- Signing identity
- https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
Signature
- Officialapplication/vnd.dev.sigstore.bundle.v0.3+json
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main
sha256:52494a501e8d320c8882c472b3f7402c8d11b77bc7fc7edf0610d83fedf1a473
Reference at this version
oci://hub.aggrega.ai/component/core/datastore/chroma:1.0.0Developer parameters
Values the developer sets in the Aggregate.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| allow_reset | boolean | false | no | Let a client wipe every collection through the server's reset call. Off by default, matching the server's own default; since the server checks no credential, turning it on lets any client that reaches the address do so. |
| max_payload_size_bytes | integer (min 1) | — | no | Largest request body the server accepts, in bytes. Omit to use the server default (41943040, which is 40 MiB). |
Operator sizing
Infrastructure sizing the operator tunes per environment.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| port | integer (min 1024, max 65535) | 8000 | no | HTTP listen port. Most operators should omit this and let the Recipe assign the default (8000). Every Recipe hands it to the server as its own port, so the server, its health check and the published address all follow it. |
| engine_version | string | 1.5.9 | no | Tag of the chromadb/chroma image the Recipes run, a Chroma release such as 1.5.9. The build halts on a value that is not a 1.x release, because the Recipes configure the server the way its 1.x releases read their settings. |
| compute | object | — | no | — |
| storage | object | — | no | — |
| overrides | object (open) | — | no | Provider-specific overrides. Accepts any nested structure. Each Recipe documents which keys it reads. |
Output contract
Values this component publishes to consumers over the uses topology.
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| host | string | — | yes | Address a client calls the server's HTTP API at. On Kubernetes it is the Service's DNS name, and on Compose the service name. |
| port | integer | — | yes | TCP port the HTTP API is served on. It follows the port an operator set in the Release, so a consumer reads it rather than assuming a default. |
| protocol | string | — | no | How the published address is spoken to on `port` — `http`, so a consumer composes its address on that scheme. |
Uses sockets
The dependency sockets this component connects through. The target of every connection wired through a socket must satisfy its label selector, and each connection may carry an attachment in the slots the socket declares. A required slot is owed by each connection the Aggregate or the Release wires through the socket.
No uses sockets declared.
Attachment slots
Named binding points at which a Feature attaches to this component. A slot's selector constrains which Feature may fill it and its inject list names how the Feature's material may be delivered. A required slot must be bound on every instance, by an attachment on the instance or at a scope above it, and a sensitive slot is declared to handle secret material. A Feature may also attach under a name no slot declares.
No attachment slots declared.
Self-inject allowlist
env
Relationships
Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.
Uses
This entity uses nothing in the catalog.
Used by
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «backend»
uses socket «cache»
uses socket «queue»
uses socket «knowledge_base»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «vector_store»
uses socket «backend»
uses socket «cache»
uses socket «backend»
uses socket «cache»
uses socket «state_store»
uses socket «vector_store»
uses socket «vector_store»
uses socket «task_memory»
uses socket «document_store»
uses socket «vector_store»
uses socket «vector_store»
uses socket «checkpointer_db»
uses socket «checkpointer_db»
uses socket «backend»
uses socket «backend»
uses socket «backend»
uses socket «vector_store»
uses socket «vector_store»
uses socket «storage»
uses socket «knowledge_base»
uses socket «data_store»
uses socket «metadata_store»
uses socket «target_datastore»
uses socket «target_datastore»
uses socket «target_datastore»
uses socket «backend»
uses socket «databases»
uses socket «etcd»
uses socket «backend»
uses socket «backend»
uses socket «cache»
uses socket «state_store»
uses socket «forward_target»
uses socket «backend»
uses socket «cache»
uses socket «chunk_cache»
uses socket «scrape_target»
uses socket «backend»
uses socket «backend»
uses socket «database»
applies to
applies to
applies to
implements
implements