Chroma Cloud workload evaluation

Assess and copy a Chroma Cloud workload

Use Jylus Migrate to discover collections, assess compatibility and storage, then approve a verified record-copy evaluation while Chroma Cloud keeps serving.

Components that could move: The selected record-retrieval or search path, after data, filter and relevance checks.
What stays in your stack: Your application, model, authorization and Chroma workloads that have not passed evaluation.
How to test it: Run the matching quickstart in a free workspace alongside your existing system. Compare the records, relevant operations and latency before moving this workload.

Get Jylus Migrate See the order-support example

One workload, using Jylus HTTP APIs. Existing drivers, query languages and connectors are not assumed compatible. Keep production traffic in place during evaluation.

Current architecture

Application → Chroma collection → ranked IDs, documents and metadata
Application → chosen embedding function for text queries
Application → existing model or user interface

Proposed Jylus architecture

Frozen source copy → Chroma-to-Jylus tool → verified Jylus records
Shadow application reads → Jylus query/text analysis → original IDs and metadata
Application → existing model or interface; switch only after the workload passes

Compatibility, migration and verification requirements

What can disappear after verification

A passing workload can move its record retrieval or search to Jylus. Returned source text and metadata can remove an extra lookup where your application currently performs one. Keep the original collection until correctness, filters, quality and load checks pass.

What remains

Keep your application, authorization, chosen model and unverified Chroma workloads. Chroma SDK calls, dense embeddings, distance thresholds, batched result shapes and embedding functions are not advertised as compatible Jylus interfaces.

How to move a sample

Run the local Docker tool to assess Chroma Cloud. After reviewing compatibility, approve a frozen record-copy evaluation. Export IDs, text, metadata, vectors and configuration locally; copy supported records into a separate Jylus workspace and verify every receipt and record. External dense-vector, fork and specialised hybrid behaviour is not reproduced.

How to verify the result

Use saved Chroma query vectors and explicitly adapted Jylus text queries. Compare original IDs, metadata, filters, completeness, measured client latency and independent relevance judgments. Partial results remain partial; matching IDs alone do not establish answer quality or identical ranking.

Example architectures for one workload; compare your actual components. Scope checked against documented product surfaces, 21 October 2026. Chroma query and retrieval documentation. This is not a blanket feature or performance comparison.

Know the operating boundaries before you switch.

Data behaviour: JSON events over HTTPS, source-ID and time queries, bounded history and analysis. The records quickstart uses those ID/time filters; verify every other required business-field filter on your workload. Acceptance is separate from query readiness: verify the receipt and read back IDs. Corrections are new linked events. This is not a claim of multi-record ACID transactions or existing database-driver compatibility.
Retention: Choose expiry or no expiry in workspace settings. Expiry removes eligible records; it is not just a search filter. Keep an independent source copy for your evaluation.
Access controls: Workspace isolation, scoped read/write API keys, key revocation, team roles and account MFA. Keep secret keys on your backend. Security details.
Export and recovery: Read source records through bounded query windows and save them in your own archive. The quickstart saves a receipt and responses locally. A one-click full-database export, customer point-in-time restore, three-machine deployment or contracted recovery objectives are not included promises; agree requirements with support before migrating.
Limits and cost: Free Developer includes 1 GB. At the storage cap, new ingest pauses; retained data is not deleted and permitted reads continue. Paid expansion needs an available billing option, your approved rate and spending cap. Buying storage preserves throughput and query limits. Compare plans.
Support: Use support@jylus.ai for evaluation questions. Confirm plan support, SLA, regional capacity, recovery and migration arrangements before moving critical traffic. API limits and retry behaviour.