Greedy vs Generous: Open-source that keeps its soul

Every open-source project that survives has to answer one question: where does the money come from? The bad answers and the good answers look the same on paper — donations, hosted services, paid support, open core, dual licensing, complementary products. What separates the projects you trust from the projects you've already left isn't the pattern, it's the posture.

The six classic shapes (a quick map)

Every open-source business pulls from the same small toolbox:

1. Donations — Patreon, Open Collective, GitHub Sponsors. Lovely, unreliable.
2. Hosted services — you sell the convenience of not running it yourself.
3. Paid support, training, courses — you sell the expertise of the people who built it.
4. Open core — the OSS is the on-ramp; the paid tier adds enterprise features.
5. Dual licensing — free under a copyleft license, paid for commercial use.
6. Complementary products — themes, plugins, hardware, hosting around the open core.

None of these are corrupt on their own. What matters is the answer to one question: who is the paid product for? Generous projects answer "people who would gladly pay." Greedy projects answer "everyone we can corner."

The four archetypes below each give a different generous answer, in the form of a "you only pay if…" promise. The qualifier tells you who the project sees as a customer and who it sees as a community member.

Directus: "You only pay if you're big enough."

Directus sits on the Business Source License. Free for anyone under a revenue/funding threshold; paid above it. The bargain is honest: solo devs, startups, and indie agencies use the whole thing forever; companies past the threshold pay because they can.

The threshold is a fence, not a trap door. There's no anxiety about "will this feature disappear next quarter?" because the feature set isn't the gate — your accounting is. That's a clean line, and the people on the free side of it never have to think about it.

Sentry: "You only pay if you trust us to run it for you."

Sentry self-hosting is free under the Functional Source License (which Sentry itself coined). You can run the entire product on your own infra, in production, for any company of any size. The only thing the license forbids is launching a competing hosted Sentry.

The paid product is Sentry's cloud — convenience, not capability. The self-hosted version isn't a stripped demo; it's the real thing. The line between "user" and "customer" is operational, not feature-gated. If you have the operational appetite to run it, you owe Sentry nothing. If you don't, their cloud is the obvious answer — and you're glad to pay.

And this isn't an idealist's model — it funds a venture-scale business. Sentry has raised over $200M across multiple rounds while keeping the SDKs and the self-hosted product fully free. The 2021 Series D put $60M behind the company at unicorn valuation, led by Accel with NEA and BOND. The Series E that followed added another $90M, framed as scaling R&D and developer-first monitoring — not raising the price of the things people already had for free. Generosity at the core, revenue at the convenience layer, capital markets along for the ride.

Ghost: "You only pay if you're tired of running servers."

Ghost is MIT-licensed and owned by a non-profit foundation. There's no enterprise tier, no source-available license, no asterisk on the LICENSE file. Ghost(Pro) is just managed hosting at a fair price — backups, updates, CDN, the things you'd otherwise be doing at 2am.

The product is identical whether you run it or they do. The foundation structure removes the "what happens at the next funding round?" question entirely — there isn't a next round. The trust this buys is a quiet superpower; people who chose Ghost five years ago haven't had to re-evaluate that choice since.

Payload: "You only pay to smooth the rough edges."

Payload is MIT, and Payload Cloud is genuinely optional polish — Git-backed deploys, file storage, preview environments. The OSS is the product; the cloud is the convenience tax for not setting up the infrastructure yourself.

It's the same answer Ghost gives, in a different shape. The community version isn't a teaser for a "real" version that sits behind a paywall. If you stay self-hosted forever, Payload has lost nothing — you're a reference customer, an issue reporter, a contributor, a recruiting funnel. The cloud is for the people who'd rather pay than fiddle, and that's an honest pitch.

The cautionary tale: Strapi

Strapi started in the same neighbourhood as Payload — open-core headless CMS, big community, fast adoption. Then the gravity of VC-style growth started showing through the floorboards.

Features that used to live in the community edition drifted toward the Enterprise tier. Strapi Cloud arrived less as a side door for the operationally allergic and more as a turnstile. The v3-to-v4 migration cost the community real money in re-platforming work. Each move was defensible on its own. Together they changed the relationship.

That's the inflection point. Once the community feels like a stepping stone to a paid product they were never going to buy — once the OSS reads as a sales funnel rather than a gift — trust evaporates. Users don't migrate because of a feature comparison; they migrate because the posture changed. A non-trivial slice of Payload's adoption story is, in part, this story.

The pattern under the patterns

The six classic monetization shapes all still work. None of them is corrupt on its own. What gets you in trouble is the posture: whether the paid thing is offered to people who'd be glad to pay, or extracted from people who feel they have no choice.

Generous projects treat their users as owners of the software. Greedy projects treat their community as a sales funnel for the software. The licenses, the pricing pages, the cloud announcements, the v-major migrations — they're all downstream of that one question.

If you're building open source and you want to know which side you're on, audit one thing: what does the person who never pays you get? If the answer is "a complete, working tool they can run forever," you're generous. If the answer is "a demo that funnels them toward a sale," you're not — and the community will notice long before the metrics do.