Open Source Sustainability: How Projects Stay Alive

90% of open source projects are maintained by 1-2 people in their spare time. Most die within 2 years. Here's how the successful ones survive.

The Sustainability Problem

The Numbers

Metric	Reality
OSS projects started annually	~1 million
Projects active after 2 years	~10%
Projects with >1 maintainer	~15%
Maintainers who burn out	~60% report burnout
Maintainers who are paid	~25% receive any compensation

The Paradox

Open source powers $8.8 trillion in economic value globally. Yet the people who create it are often unpaid, overwhelmed, and one life event away from abandoning the project.

The 6 Sustainability Models That Work

1. Venture-Backed Company

How it works: Raise VC funding, hire a team, build a business around OSS.

Company	Funding	Employees	Revenue Model
Supabase	$200M+	~150	Cloud hosting + enterprise
n8n	$55M+	~80	Cloud + enterprise
Cal.com	$40M+	~30	Cloud + enterprise
PostHog	$80M+	~50	Cloud + enterprise
Plane	$30M+	~40	Cloud + enterprise

Pros: Full-time team, fast development, professional support Cons: VC pressure to monetize, potential license changes, possible acqui-hire

Survival rate: High (while funded). Risk is what happens when growth doesn't meet VC expectations.

2. Bootstrapped Company

How it works: Build a profitable business without VC funding.

Company	Product	Revenue	Model
Plausible	Analytics	Profitable	Cloud hosting subscriptions
Listmonk	Email marketing	Community-funded	Donations + services
Uptime Kuma	Monitoring	Community-funded	Sponsorships

Pros: No VC pressure, sustainable pace, aligned incentives Cons: Slower growth, smaller team, may not reach scale

Survival rate: Very high (profitable = sustainable).

3. Foundation Governance

How it works: A non-profit foundation stewards the project. Corporate sponsors fund it.

Foundation	Notable Projects	Annual Budget
Linux Foundation	Linux, Kubernetes, Node.js	$200M+
Apache Foundation	Kafka, Spark, Superset	$5M+
CNCF	Prometheus, Envoy, containerd	Part of Linux Foundation
Eclipse Foundation	Jakarta EE, Theia	$10M+

Pros: Neutral governance, corporate funding, long-term stability Cons: Slow decision-making, bureaucracy, only works for infrastructure

Survival rate: Very high for established foundations.

4. Corporate Sponsorship

How it works: One or more companies sponsor the project because they depend on it.

Project	Primary Sponsor	Arrangement
Grafana	Grafana Labs (created it)	Full-time team
Mattermost	Mattermost Inc (created it)	Full-time team
VS Code	Microsoft	Part of Microsoft's strategy
Chromium	Google	Chrome's engine

Pros: Stable funding, full-time development Cons: Sponsor controls direction, risk if sponsor loses interest

5. Community Funding

How it works: Individual donations and sponsorships via platforms.

Platform	How It Works	Examples
GitHub Sponsors	Monthly donations to maintainers	Individual projects
Open Collective	Transparent collective budgets	webpack, Babel
Patreon	Monthly creator support	Vue.js (early days)
Tidelift	Enterprise subscriptions for OSS maintenance	Libraries and tools
thanks.dev	Distribute funding based on dependency tree	Ecosystem-wide

Pros: Community-aligned, diverse funding Cons: Usually insufficient for full-time work, unpredictable

Typical income: $500-5,000/month for popular projects. Not enough to hire.

6. Dual Employment

How it works: Maintainer works at a company that lets them maintain the OSS project as part of their job.

Situation	Example
Company uses the tool	Engineer maintains it during work hours
Company sponsors the maintainer	Part-time maintenance as "giving back"
"Open source time" policy	20% time for OSS contributions

Pros: Maintainer gets paid, project gets attention Cons: Depends on employer, could change with job change

What Makes Projects Die

The Top 5 Killers

Killer	How It Happens	Prevention
Maintainer burnout	Endless issues, no appreciation, no pay	Co-maintainers, boundaries, funding
Single maintainer dependency	"Bus factor" of 1	Recruit co-maintainers early
Scope creep	Trying to be everything for everyone	Clear scope, say no often
No funding	Can't justify the time	Explore funding models early
Better alternative appears	New tool does it better	Iterate, don't stagnate

Warning Signs a Project Is Dying

Signal	What It Means
No releases in 6+ months	Development has stalled
Issues pile up with no response	Maintainer is overwhelmed or gone
README says "looking for maintainers"	Current maintainer wants out
Dependencies are severely outdated	No active maintenance
Core contributor graph shows decline	Community is shrinking

What Users Can Do

Direct Impact

Action	Effort	Impact
Star the repo	1 second	Low (vanity metric, but visible)
File quality bug reports	30 minutes	Medium (helps prioritize)
Answer others' questions	15 minutes	Medium (reduces maintainer burden)
Write documentation	1-4 hours	High (most needed contribution)
Submit bug fix PRs	2-8 hours	High (direct code improvement)
Sponsor financially	$5-50/month	High (enables dedicated time)
Blog about the tool	2-4 hours	Medium (marketing, adoption)

Choosing Sustainable Projects

When picking OSS tools for your stack, evaluate sustainability:

Factor	Sustainable	Risky
Maintainers	3+ active	1 person
Funding	Company or foundation backed	Unfunded hobby
Release cadence	Monthly or better	Last release 6+ months ago
Issue response time	< 1 week	Months or never
Contributor diversity	Many companies represented	Single-company contributors
License	Clear, stable	Recently changed or unclear

The Bottom Line

Open source sustainability isn't solved — it's managed. The most reliable projects have:

Multiple revenue streams (not just donations)
Multiple maintainers (not a single person)
Clear governance (who decides what)
Active community (users who contribute back)
Business model (open core, managed cloud, or foundation)

As a user, the best thing you can do is choose sustainable projects and contribute back — whether through code, docs, bug reports, or sponsorship.

Find sustainable, well-maintained open source alternatives at OSSAlt.