Is open source a business model?

No. Open source is a licensing and distribution choice, not a revenue mechanism. Revenue comes from a separate model layered on top — managed hosting, a commercial edition, support contracts, or certification — and the licence choice mainly determines how cheaply the product reaches users.

Why did several major projects move to source-available licences?

The common trigger was cloud providers operating the open version as a managed service in direct competition with the maintainer. Licences such as the Server Side Public License and the Business Source License restrict that specific use, and the changes have repeatedly prompted community forks.

What sets the price ceiling for a commercial product built on open source?

Roughly the internal cost of running the open version, including the engineering time required to operate it. Customers always retain the option to self-host, so pricing above that ceiling requires a defensible reason such as compliance guarantees, liability transfer, or accumulated switching costs.

How open source shapes software markets

Guide · Market Growth · 4 min read · last verified 2026-07-21

Reviewed before publication Editorial board Independent commercial review

In shortOpen source collapses the cost of distribution and the price of the layer it occupies, pushing commercial value upward into layers that remain scarce — operations, compliance, and integration.

Open source shapes software markets by collapsing the cost of distribution and the price of whatever layer it occupies, which pushes commercial value upward into the layers that remain scarce. The economic effect is not that software becomes free — it is that the point at which money changes hands moves.

Distribution without permission

A commercial product reaches an engineer through a purchase decision. An open source project reaches the same engineer through a package manager, and the engineer needs no budget, no procurement review, and no manager's approval to try it. That difference in friction is the single largest advantage open source confers, and it operates before any question of price.

The practical consequences compound:

Evaluation happens during real work rather than in a trial environment, so the adoption decision is made by the person who will live with the consequences
Adoption is bottom-up, which means the vendor discovers demand inside an account rather than manufacturing it
The commercial conversation starts after the product is already load-bearing, which inverts the usual negotiating position
Documentation, community answers, and third-party tutorials accumulate as a distribution asset the vendor does not fully pay for

This is a distribution channel with unusual properties rather than a pricing strategy, and it behaves like other channels in that it shapes what can be built — how distribution channels shape software markets covers that dynamic more generally.

Commoditisation moves up the stack

When a capable open source implementation of a layer exists, the price of that layer trends toward the cost of operating it. Operating systems, web servers, databases, container runtimes, and orchestration have each followed this path — the layer did not disappear, but selling it as a licensed product stopped being viable.

Value then relocates to whatever the free layer does not solve. Historically that has been operations, integration, compliance, and the managed service that removes the burden of running the thing. The pattern behind this is old enough to have a name: firms have a standing incentive to commoditise their complements, because cheaper complements increase demand for what they sell. Cloud providers offering managed versions of open source databases are doing exactly that, and so are hardware vendors funding free operating systems.

For anyone assessing a market, the question is not whether an open source alternative exists but which layer it occupies and which layer it makes scarce by comparison. A moat built on a layer that open source is approaching is on a timer — what is a market moat is worth reading against that test.

Open-core economics and the boundary problem

Open core keeps a functional product under a permissive or copyleft licence and reserves specific capabilities for a commercial edition. The commercial line is usually drawn around things a large organisation needs and an individual developer does not: single sign-on, fine-grained access control, audit logging, high availability, multi-tenancy, and support commitments.

The model's difficulty is that the boundary has to be redrawn continuously. Put too much behind the paywall and the free product stops being good enough to build the adoption base the model depends on. Put too little and the commercial edition has no pull. The boundary is also contested from outside: community contributors may implement the reserved feature, and cloud providers may operate the open version as a managed service without contributing back.

That last pressure produced a visible wave of licence changes. Several widely used projects moved from established open source licences to source-available terms — the Server Side Public License and the Business Source License being the common destinations — specifically to restrict competitive hosting. Those changes have repeatedly triggered community forks, and the forks are the real cost: a licence change buys protection against one competitor at the risk of losing the distribution advantage that made the project valuable.

What it does to pricing power

Open source does not eliminate pricing power, but it changes where it comes from. Pricing power built on the software being unavailable elsewhere is fragile. Pricing power built on operational burden, data gravity, integration depth, or contractual guarantees survives, because the free alternative does not remove the underlying cost of running production systems.

The asymmetry is that the customer always has a visible alternative: run it themselves. That sets a ceiling on price, and the ceiling is roughly the internal cost of operating the open version, including the engineers required. Vendors that price above it need a defensible reason, which usually means the switching cost of migrating away has grown — how switching costs shape market share covers how that accumulates.

It also compresses the value of ordinary feature differentiation. A feature that can be reimplemented in the open version has a short commercial life, so durable differentiation tends to concentrate in things that are hard to replicate socially rather than technically: certification, liability, ecosystem, and the accumulated trust of running critical workloads.

What to watch

Which layer is being commoditised next. The layer directly below a product is the one to monitor; when a credible open implementation of it matures, the product's pricing rationale has to move up.
Licence changes in projects a business depends on. A move to source-available terms signals the maintainer is under competitive pressure and changes what downstream users are permitted to do.
Fork viability. A fork with independent maintainers, multiple corporate contributors, and a foundation home is a genuine alternative; one with a single sponsor is a negotiating position.
Where the paying customer's pain actually sits. If the answer is operations and compliance rather than capability, the free tier can be generous. If it is capability, open core is structurally difficult to hold.
Contribution concentration. A project where most commits come from one employer carries the same vendor risk as proprietary software, whatever the licence says.