Open source drove CockroachDB adoption

Open source was not a branding choice here, it was the distribution wedge that made teams willing to try a new database in production. A database sits under live apps and years of data, so buyers are allergic to getting trapped in a vendor specific stack. CockroachDB lowered that fear by letting engineers start free, run it themselves, and only pay later for support, security features, and managed cloud operations.

• Cockroach Labs built a classic open core motion. Teams can self host CockroachDB Core for free, test it on their own infrastructure, and expand into paid enterprise features or CockroachDB Cloud once the workload is large enough. That makes the first adoption decision an engineering test, not a procurement event.
  1 sacra
• The contrast with MemSQL, now SingleStore, shows the tradeoff clearly. SingleStore chose not to be open source, and that slowed developer adoption versus databases like CockroachDB, MongoDB, Redis, and CouchDB, even though SingleStore built strong technology and meaningful ARR.
  3 sacra 4 sacra
• This matters more in databases than in most software categories because switching is painful. Once app code, schemas, and operations are built around one system, moving later is expensive. Open source gives developers a feeling of exit rights, which makes them more comfortable taking the initial bet on a newer architecture.
  1 sacra

The next leg of the market favors vendors that turn open source adoption into managed cloud revenue. As more production databases move to cloud services, the winners will be the companies that let developers start with code and end with a fully operated service, without ever forcing a hard jump into a closed system.