Overview
RethinkDB’s commercial company shut down in October 2016, while its database continued as an open-source project. Members of the engineering team joined Stripe. The subsequent purchase of the source-code rights by the Cloud Native Computing Foundation was a separate transaction, announced in February 2017. Treating these events as one acquisition obscures what happened to the company, its people, and its software. [1] [2]
The technical proposition was a database that pushed changing query results to applications. A developer building a live application could subscribe to updates rather than repeatedly ask whether data had changed. RethinkDB’s website still presents that capability and provides the database for download. [3]
People and product
YC lists Michael Glukhovsky and Slava Akhmechet as founders and places RethinkDB in its Summer 2009 batch. Its profile describes a query language with joins and grouping, parallel execution, and tools for managing clusters. These were parts of a database product, rather than evidence that the company had already solved the commercial task of selling it. [4]
Live queries connect database changes to user-visible behavior. A scoreboard, collaborative interface, or monitoring screen needs fresh state. Polling makes an application ask repeatedly for that state; a changefeed sends changes as they occur. This changes how the application handles updates, but does not remove its need to manage permissions, disconnects, recovery, and the correctness of the underlying data. The project’s own examples demonstrate the update mechanism; they are not a comparative performance benchmark. [3]
A commercial shutdown
On October 5, 2016, Akhmechet announced that the company could not build a sustainable business. He also said RethinkDB and Horizon would remain available under open-source licenses and that the team was working on continuity arrangements. The announcement describes members of the engineering team moving to Stripe. It does not say Stripe acquired the database project. [1]
The strongest supported commercial conclusion is the founder’s own account of an unsustainable business. The announcement does not provide a profit-and-loss statement, annual burn, customer acquisition cost, or a breakdown of why individual prospects did not buy. Technical popularity and commercial sustainability are different outcomes, but the available evidence cannot assign precise financial effects to each competitive pressure.
A preserved reproduction of Akhmechet’s later post-mortem offers a more specific explanation. He argued that the team entered a difficult developer-tools market and prioritized correctness, interface simplicity, and consistency while users valued timely availability, immediate performance, and a clear use case. He also described the work of developing RethinkDB, Horizon, and Horizon Cloud as too much for a small team; the cloud offering did not ship before the money ran out. This is the founder’s retrospective explanation, not an independent allocation of financial causation. [6]
The account complicates a recommendation to solve the business merely by adding managed hosting. The team had already considered hosting and was developing a broader cloud product. A proposed successor therefore needs evidence of a specific customer and distribution advantage, rather than assuming that a different delivery model removes the commercial problem.
The software changes hands
In February 2017, CNCF purchased the copyright and assets for $25,000 and contributed the project to The Linux Foundation under the Apache License, Version 2.0. CNCF said investors had provided $12.2 million to the former company. These figures measure different things: historic venture investment and the later purchase of software rights. The asset purchase price is not a valuation of the team’s move to Stripe or a complete accounting of investor returns. [2]
CNCF argued that a more permissive license would make adoption and contribution easier. That is the buyer’s explanation for the relicensing decision. It should not be turned into proof that the earlier license alone caused the company’s shutdown. The transfer created a legal and institutional route for continued community development. [2]
Timeline and continuing availability
- 2009: RethinkDB joins YC’s Summer batch. [4]
- October 2016: The commercial company announces its shutdown and the engineering team’s move to Stripe. [1]
- February 2017: CNCF announces the source-code rights purchase, relicensing, and contribution to The Linux Foundation. [2]
- December 2023: The project announces RethinkDB 2.4.4, with Data Explorer and platform-compatibility fixes. [5]
The current website continues to offer downloads and documentation. Availability establishes that the software survives the company; it does not by itself establish a support service level or a particular pace of maintenance. A team considering adoption should evaluate those operating requirements directly. [3]
RethinkDB therefore offers two lessons with different evidence. The company’s own announcement documents a failure to sustain the business. The later rights transfer and releases document a continuity path for useful open-source software. Neither outcome should erase the other.