The Paradox
Most critical infrastructure runs on open source software. Linux runs 90% of cloud. Apache runs much of the web. Yet the developers maintaining these projects are often unpaid volunteers.
This creates precarious situations. When a solo developer maintains a critical library they no longer have time for, security issues remain unfixed. Organizations depending on that library are vulnerable.
Sustainability Models
Sponsorships: Individuals and companies sponsor developers. GitHub Sponsors, Patreon, and others enable this. Works well for visible projects with enthusiastic supporters.
Enterprise support: Companies offer paid support contracts for open source software. Red Hat’s business model around open source proved this works at scale.
Grants and foundations: Organizations like Apache Software Foundation, Linux Foundation, and GNOME Foundation provide funding for maintained projects.
Employment: Companies hire open source developers to work on projects. Maintainers become employees.
Dual licensing: Offer software under open source license (free) and commercial license (paid). Companies needing commercial terms pay.
The Challenge for Corporations
Large companies benefit tremendously from open source. Yet many contribute minimally. A company using 1,000 open source libraries should contribute to at least some of them.
Time: Developers are expensive. Contributing is seen as expensive.
Legal concerns: Companies worry about open source licenses affecting their own software.
Priority misalignment: Internal priorities don’t align with project needs.
What Works
Sponsored developers: Companies sponsoring developers to work on critical projects benefits everyone.
Bug fixes and contributions: When companies find bugs in open source, contributing fixes back is excellent.
Usage in products: Some companies promote open source in their products, giving projects visibility.
Infrastructure and tooling: Some companies donate infrastructure (cloud computing, CI/CD) for projects.
The Individual Perspective
Maintaining popular open source is rewarding but exhausting. Thousands of users create expectations. Bug reports, feature requests, and pull reviews require time. Popular projects generate support requests from users.
Many maintainers burn out from the burden. Supporting maintainers—financially, emotionally, professionally—is critical for sustainability.
The Linux Kernel Example
The Linux Kernel sustains thousands of contributors because:
- Institutional backing: Companies benefit from Linux and fund contributors
- Clear governance: Established processes for contributions and decisions
- Distributed leadership: Not dependent on single maintainer
- Long-term perspective: Everyone understands Linux is permanent infrastructure
This model shows how open source can sustain at scale.
Forward Paths
Increase corporate contribution: Companies should contribute to projects they depend on.
Support foundations: Funding organizations that support open source creates sustainability.
Paid open source: More companies should adopt models where they fund open source development.
Recognize maintainers: Culturally, we should treat open source contributors as professional work worthy of compensation.
Balance open and proprietary: Organizations can use open source for foundations while building proprietary differentiation on top.
Open source is critical infrastructure. Sustainable open source requires commitment from individuals, companies, and institutions. The alternative—unsupported, unmaintained software—is worse for everyone.