Open source is not a business model. It's a distribution strategy. This distinction sounds obvious when stated directly, but it's a distinction that founders frequently blur — and the blurring produces predictable failures when a company with excellent open-source adoption tries to convert that traction into enterprise ARR. The dynamics are worth examining in detail, because we see the confusion often enough in the companies we meet that it warrants a clear-eyed analysis.
Open-source distribution works because friction is near zero for a developer who wants to try your tool. Clone the repo, run docker-compose, have a working instance in thirty minutes. That frictionless adoption creates a pipeline of users who understand your product, advocate for it within their organizations, and create the inbound demand that feeds an enterprise sales motion. The best infrastructure companies of the past decade — HashiCorp, Confluent, Elastic, Grafana Labs — used this pattern with remarkable consistency. Open source fills the top of the funnel better than any other channel at the developer-tools category.
Where the model breaks
The conversion problem emerges when the open-source product is complete enough that most users never hit a reason to upgrade to the enterprise tier. If your self-hosted deployment covers 90% of the use cases that a $50k enterprise contract covers, the marginal value of paying for enterprise support is hard to justify to a CFO. The companies that navigate this correctly build their open-source tier around individual and small-team usage — enough to demonstrate value and create champions — while designing the enterprise tier around requirements that are structurally absent from self-hosted deployments: multi-tenancy, SSO, audit logging, SLA-backed support, compliance documentation, and the managed service economics of not running infrastructure yourself.
The companies we back with open-source-first go-to-market motions have a clear, defensible answer to the question: "What does a large enterprise get in the paid tier that they genuinely can't get by running the open-source version?" If the answer is "mostly the same thing, but managed," the unit economics rarely work out. If the answer is "a fundamentally different capability layer designed for enterprise operational requirements," the conversion path is real. Tiptap in our portfolio illustrates the latter: the open-source editor framework captures developer adoption broadly; the enterprise tier adds the collaboration server, the management plane, and the support structure that production deployments at scale require.