Open Core

An open-source product with paid features, hosting or support on top.

Also known as: open core, open-core model, commercial open source

Open core gives away the core product as open source and charges for what surrounds it: hosted/managed versions, enterprise features (SSO, audit logs, SLAs), support contracts. Developers adopt freely, prove value inside companies, and convert to paid when production needs arrive — distribution and trust built in.

open core (free, self-hosted) → team depends on it → needs SSO/uptime/support → paid tier

It works best for infrastructure developers choose themselves: databases, dev tools, data stack. Adoption is bottom-up and global from day one — no sales team required to start. The tension is permanent: every feature’s placement (open vs paid) is a fight between community goodwill and revenue.

The classic mistakes:

Open-sourcing too little to matter. A crippled “community edition” nobody adopts generates no funnel. The open core must be genuinely useful standalone — useful enough that withholding the paid layer stings.
License confusion. Permissive vs copyleft vs source-available changes who can use it and how competitors behave. Choose deliberately with a lawyer (licenses), and understand relicensing limits once contributors exist.
Cloud providers as competitors. A successful open core gets hosted by giants who contribute little back. Have a view on this before it happens (license choice, trademarks, managed offering of your own).
Monetizing too late. Years of pure adoption with no paid motion trains the market that it is free. Ship the commercial tier early, even small — the motion needs learning too.

Founder fit: developers who live in open source and can nurture a community for years. It is a slow-burn model: distribution compounds, revenue lags, and patience is the strategy.