Open source software is free to download, but it is not free to produce. Someone has to fix bugs, answer security reports, update dependencies and pay for servers and domains. When a project becomes popular, this work grows far faster than its maintainers' spare time. Financial sustainability is therefore not a side issue: it is what decides whether a component used by thousands of systems will still receive updates three years from now.
The main sources of funding
There is no single model. Most sustainable projects combine several sources.
Individual donations
Recurring donation platforms let users contribute small monthly amounts. They are easy to set up and create no obligations. The limitation is that they rarely cover a salary: they work well for infrastructure costs or as a symbolic thank-you.
Corporate sponsorship
Companies that depend on a project can sponsor it with larger amounts, often in exchange for visibility (a logo in the README or on the website). It is one of the most effective sources, but it requires someone in the project to spend time contacting companies, explaining the project's value and renewing agreements.
Time paid for by an employer
Many maintainers are paid by their company to spend part of their working hours on the project. It is an indirect but very widespread form of funding, especially in infrastructure projects. The risk is dependence: if the company changes priorities, the time disappears.
Paid services
The code stays free, but the project or its maintainers sell services:
- support and maintenance contracts with guaranteed response times;
- consulting and integration for complex installations;
- training for teams adopting the software;
- managed hosting of the same application.
This model aligns interests well: those who pay get concrete value, and those who do not keep using the software freely.
Grants and public funding
There are public and private programmes that fund specific work on free software, for example security, accessibility or features of general interest. They require a written proposal with goals and timelines, and a final report. They are excellent for well-defined pieces of work, less so for ordinary maintenance.
Bounties on individual issues
A user or company offers a sum to solve a specific problem. It can work for isolated features, but it tends to reward novelty rather than maintenance, and it can create friction if several people work on the same problem.
Comparing the sources
| Source | Stability | Strings attached | Effort to obtain |
|---|---|---|---|
| Individual donations | Medium | None | Low |
| Sponsorship | Medium | Visibility | Medium |
| Employer time | Variable | Company priorities | Low |
| Paid services | High if there is demand | Contractual commitments | High |
| Grants | Limited to the project | Goals and reporting | High |
| Bounties | Low | Tied to one issue | Low |
Who manages the money
An underrated question is who actually receives the money. If it lands in a maintainer's personal account, tax and trust questions arise: who decides how to spend it? What happens if that person leaves the project?
The cleanest solutions are:
- relying on a fiscal sponsor or foundation that administers funds on the project's behalf;
- using platforms that make income and expenses public;
- writing into the governance how decisions on the use of funds are made.
Frequent mistakes
- Asking for money without saying what for: «support us» is less convincing than «we need funds for a security audit of the authentication module».
- Promising priority to those who pay without saying so publicly: it undermines community trust.
- Depending on a single sponsor: when it pulls out, the project is left exposed.
- Neglecting maintenance in pursuit of funding tied to new features.
What users of the software can do
If an organisation depends on an open source project, contributing to its sustainability is also a form of risk management. The simplest options are an annual budget to sponsor critical dependencies, allowing its developers to contribute during working hours, and buying commercial support where it exists.
In short
- Producing and maintaining open source software has real costs that grow with popularity.
- The main sources are donations, sponsorship, paid time, services, grants and bounties.
- Combining several sources reduces dependence on a single funder.
- Funds should be managed transparently, ideally through a fiscal sponsor.
- Users can support the software through sponsorship, their developers' time and paid support.
