From Open Source to Unicorn: How to build on a project
summary
Sentry offers complete source code that customers can self-host while preventing others from running it as a service under a BSL license, keeps SaaS and on‑prem feature parity, and refuses paid one‑off builds that serve a few rather than the many. Community tactics include moving product issues to GitHub, encouraging engineers to present and write, and donating roughly $2,000 per developer for about 180 developers — half a million dollars a year. Packaging (three tiers) drives pricing and growth.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:35Does anyone use Sentry
- 1:01Why open source
- 2:15Should I open source
- 2:40Affordability
- 4:18Open Source vs BSL
- 5:59Giving back
- 6:31Hyperscalers
- 7:18Does it bring value
- 9:05Developers talking to developers
- 9:56Sentry
- 10:46Active participation
- 12:07Removing open source
- 13:39Building in open source
- 14:50Building for the many
- 16:04Pricing and packaging
- 18:44Open source vs community engagement
related talks
27mOpen Source Power and the Passion
55mBuilding Business Around Open Source Projects | Panel Discussion
01h 03mThe Value of Open Source
50mOpen Source as a Business: Strategy, Struggle & Success
43mSo You Want to Open Source Your Project? Hold Your Horses!
33mBuilding an OSS-Centric Company (and Why You Want To)
14mBuilding an Open Source Strategy Before Building Your Product
27mOpen Source: Supporting, Contributing and Evangelising