RethinkDB: the company closed, the open-source project survived

What it is

RethinkDB is an open-source database for realtime applications, including live queries that push changes to an application. The database project and the original commercial company had different outcomes (Foundation transition).

Timeline

• 5 October 2016: Slava Akhmechet announced the company was closing after more than seven years of development, saying it had not built a sustainable business (Shutdown announcement).
• October 2016: the company said its engineering team would join Stripe while it worked with the community on continuity for RethinkDB and Horizon (Shutdown announcement).
• 6 February 2017: Mike Glukhovsky announced that CNCF had bought source-code rights and contributed them to The Linux Foundation under the permissive ASLv2 license (Foundation transition).

Why it worked

The company did not succeed as a sustainable business, by its own account. The continuity effort did achieve something distinct: the source-code rights moved into community hands with institutional support (Shutdown announcement, Foundation transition).

The transition post describes former employees and community members forming an interim leadership team and organizing the legal transfer. Open licensing helped preserve options, but governance and asset ownership still needed work (Foundation transition).

What to learn

1. Test a paid business model separately from whether developers like the software. Compare Ghost’s paid hosting loop. (Evidence informing this lesson).
2. Know who owns the code, name and distribution assets before a crisis. (Evidence informing this lesson).
3. Plan for maintainers, governance and funding—not only a public repository—if customers depend on your product. (Evidence informing this lesson).

Risks and what didn't work

• The shutdown post explicitly says the team could not build a sustainable business. It does not disclose a complete revenue or burn history, so we do not supply one (Shutdown announcement).
• Creditors held the code and other assets after closure. The transition account says the team preferred securing those rights and a permissive license over merely forking under the existing AGPL (Foundation transition).
• The foundation post’s optimism concerns the transition at that historical moment. It is not evidence of today’s support capacity, release cadence or commercial viability (Foundation transition).