You’ve felt it. That knot in your stomach when the open source tool you’ve been contributing to for free suddenly announces a “premium tier.”
At first, it’s fine. Cloud hosting, managed updates, maybe some analytics. Reasonable. But then the paywall creeps closer to the core. Features that used to be free get “deprecated.” The roadmap pivots toward enterprise buyers. And suddenly, the code you wrote on weekends is fueling someone’s Series B.
The open core model isn’t a compromise between freedom and revenue. It’s a toll booth built on unpaid labor.
Let’s be honest about what’s happening. A company takes an MIT-licensed project, wraps it in a SaaS layer, and charges for the cloud version. The community builds the core for free. The company monetizes the convenience. Sounds fair, right? But here’s the twist: the “open” part is the bait. The “core” is the trap.
One Hacker News commenter nailed it: “I love when an open source SaaS provider attaches cool cloud/AI based features onto my subscription. I hate when an open source SaaS provider bakes locked features into the open sourced code.”
That distinction is everything. Build NEW value on top of the open core? The community cheers. Lock AWAY value that was already open? The community revolts. And yet, most companies drift toward the second approach because it’s easier to monetize what already exists than to build something genuinely new.
The moment you paywall what was once free, you’re not selling software. You’re selling back the community’s own work.
Here’s what nobody wants to say out loud: most open source maintainers will never make a living from their projects. The economics don’t work. Cloud providers can run your code cheaper than you can. Enterprise customers want SLAs, not GitHub issues. And the community? They’ll fork your project the second you get too greedy.
So what actually works? The honest path is brutal in its simplicity. If you want to monetize, build something that didn’t exist before. AI-powered insights. Managed infrastructure that saves real engineering hours. Integrations that connect your tool to the enterprise stack. These are things people will pay for because they represent NEW labor, not recycled community contributions.
Don’t charge for the road everyone built. Charge for the gas station you constructed at the intersection.
The projects that survive this tension are the ones that respect the line between community property and commercial value. Plausible Analytics did this well. They open-sourced their core analytics engine and built a hosted version that adds genuine convenience. The community can self-host forever. The company sells speed and simplicity. Nobody feels exploited.
But for every Plausible, there are ten companies that start with noble intentions and end up rent-seeking. The pressure from investors is relentless. “Just close this one feature.” “Just add this enterprise module.” “Just make the free tier a little worse.” Each decision is small. The trajectory is catastrophic.
If you’re a maintainer reading this, here’s the uncomfortable truth: your community is not your customer. Your community is your co-creator. The moment you confuse those two roles, you’ve chosen a path that ends with a fork and a boycott.
Treat your contributors like partners, not product. Everything else is just a slower way to die.
FAQ
Q: Isn't open core just a legitimate business model like any other?
A: Legitimate, yes. But legitimacy and alignment aren't the same thing. Plenty of legitimate models extract value from unpaid contributors. The question isn't whether it's legal — it's whether it's sustainable without alienating the people who built your core.
Q: So should I just never monetize my open source project?
A: No. Monetize aggressively — but monetize NEW value. Cloud convenience, AI features, enterprise integrations, managed infrastructure. Build things that didn't exist in the open core. If the only thing you can charge for is access to what the community already built, you don't have a business model. You have a toll booth.
Q: What about companies like MongoDB or Redis that changed their licenses to protect against cloud providers?
A: That's a different conversation. License changes to stop AWS from reselling your code is self-defense. Paywalling features your own community contributed is exploitation. The first protects creators. The second exploits them. Don't confuse the two.