Debate Grows Around Open Source Funding After Drupal Infrastructure Analysis

The debate over how open-source infrastructure is funded is expanding following a recent analysis of Drupal’s operating costs. What began as a breakdown of numbers has now moved into a wider discussion about sustainability, responsibility, and long-term viability.

In a blog post by Dries Buytaert, founder of Drupal and co-founder of Acquia, the cost of running Drupal’s infrastructure was outlined alongside the risks of uneven funding. The analysis has since prompted responses from developers, organisations, and contributors across the open source ecosystem.

Much of the discussion centres on a structural issue. Open source infrastructure is widely used, but its funding is not tied to usage. Large organisations often depend on shared systems without contributing proportionally to their upkeep. Contributors note that this pattern extends beyond Drupal to package registries, CI systems, and other shared services.

In a LinkedIn discussion following the post, Ryan Szrama, CEO of Centarro, pointed out that major technical decisions are often made without considering long-term financial sustainability. He referred to earlier ecosystem shifts where technical merit guided decisions, while funding models remained secondary.

The discussion also reflects growing pressure on shared infrastructure. Automated systems, security scanners, and AI-driven workflows are increasing demand on package registries and distribution networks. These systems now operate at a scale that existing funding models were not designed to support. Brian Fox of Sonatype, involved in OpenSSF discussions, described the situation as a “tragedy of the commons,” where shared systems are heavily used but insufficiently funded.

Several approaches are being considered. Corporate sponsorship offers immediate stability but can introduce dependency on a small number of stakeholders. Usage-based models aim to connect infrastructure costs to organisations that rely on them, though they would require both technical changes and cultural shifts within open source communities.

Concerns about funding concentration were also raised. Chris Kelly, a Drupal contributor, pointed out that relying on a narrow funding base—whether corporate or institutional—can introduce political and strategic risks, particularly if support is withdrawn or influenced by external factors.

Other models are also emerging. Some projects are exploring paid hosted services while keeping core software open. Yaw Anokwa, CEO of ODK, highlighted this approach as a way to sustain infrastructure while continuing open source development. At the same time, structured corporate contribution models are gaining attention. Norah Schrum pointed to efforts by companies such as Canonical to support open source foundations and contributors through more systematic funding mechanisms rather than discretionary support.

Not all approaches rely on structured models. Some contributors highlighted the limits of voluntary participation. Namith J., involved in the FAIR project, noted that while community backing is often visible, it does not always translate into sustained financial commitment when required.

The discussion highlights a broader shift. Infrastructure is no longer seen as just a technical concern. It is also an economic and governance issue, shaping how open source projects are maintained and who influences their direction.

No single solution has emerged. However, the conversation suggests a change in approach. Rather than treating funding as secondary, contributors are beginning to examine how financial models can align with the scale and importance of the systems they support.

Read the earlier report: Dries Buytaert Examines Costs and Funding Risks of Drupal Infrastructure.