On October 23, 2026 (Beijing time), Chroma announced it signed a definitive agreement to join Replit and will wind down the existing Chroma Cloud service over about 60 days. Writes are disabled November 22, 2026 (read-only for 30 days); reads stop December 22, 2026. Open-source ChromaDB remains under Apache 2.0.
Before November 22, Cloud customers should stop or redirect write workloads, move active work to another Chroma deployment or database, and start exporting data they need to keep. Existing data stays readable through the following read-only window. Before December 22, finish exports, confirm apps no longer hit Cloud endpoints, and remove or rotate Chroma Cloud credentials.
The company blog frames the deal as continuing ChromaDB and Foundation work inside Replit’s agent platform. For operators, what matters is the Cloud write／read cutoff dates and that open-source ChromaDB continues under Apache 2.0. Related reading: Replit Monitoring Agent Can Investigate, Fix and Auto-Publish Production Issues, Replit Makes OpenAI the Default in Replit Agent. You Can Still Pick Claude, and AWS Opens Infinity, a Research Runtime for Extreme Agent Concurrency.
As for migrating Cloud collections end to end, how exports behave at scale, and what breaks if credentials linger past December 22—we have not tested that. Feedback can go through the site-owner contact link in the footer. For account timeline questions, Chroma points to support@trychroma.com.