Open-Core vs. Closed-Core Business Strategies
summary
Panelists compare concrete outcomes of open-core vs closed-core: RethinkDB open-sourced after ~3.5 years of development because distribution beat proprietary control, community becomes the company’s biggest asset, and unexpected contributors fix and extend features. They cite Apache-style foundation tradeoffs, a trademark split over Node’s name, and practical metrics like a 16-week release cadence to align engineering with Hacker News-driven adoption. Lessons stress shipping, community governance, and when to keep a closed core for security or monetization.
AI-written summary · about
chapters (5)
- 0:00Introduction and hosts
- 1:51Open source evolution
- 9:32Scaling community challenges
- 14:07RethinkDB open-source journey
- 20:22Sustainable business models
related talks
15mOpen Core vs Open Source
10mOpen Source vs Open Core
20mBuilding an Open Core Business Model
15mLessons learned: Guidance on how to make open source development a success
47mHow to Turn Your Open Source Project Into a Company
29mUnderstanding Corporate Open Source Strategy
46mThe Business Of Open Source: How Big Money, Investors, and Greed are Changing Ope...
55mBuilding Business Around Open Source Projects | Panel Discussion