The Stewardship Economy: Who Ends Up Holding the Commons

When Google handed the desktop roadmap of Flutter — its open-source UI framework — to Canonical, the company behind Ubuntu, it looked like a routine transfer of maintenance responsibility. It was actually a signal of a quiet, structural shift in how open source works. Increasingly, major technology companies are becoming the stewards of open-source projects — taking over their maintenance, governance, and direction — as the original creators step back, the volunteer maintainers burn out, or the projects grow too critical to be left to chance. This looks benign, even generous: someone with resources is taking care of the commons that everyone depends on. But stewardship is not the same as maintenance — the steward does not merely keep the project running; the steward governs it, shapes its direction, decides its priorities, and holds the power over a resource the whole ecosystem relies on. As corporations become the stewards of the open-source commons, a new economic and political model emerges: one in which the "free" and "community" infrastructure everyone builds on is increasingly governed by the corporate stewards who took it over — and stewardship, however benevolent it appears, is control.

This is the stewardship economy: the emerging model in which major technology platforms become the stewards — the maintainers and governors — of critical open-source projects, so that the commons everyone depends on is increasingly directed by corporate stewards, and the question of who holds the open-source infrastructure (its governance, priorities, and power) becomes as consequential as who uses it.

Why stewardship is power, not just maintenance

The stewardship economy matters because stewardship conflates two different things — the work of maintaining a project and the power of governing it — and the second travels quietly with the first. When a corporation takes over an open-source project, it presents this as maintenance: keeping the code updated, fixing bugs, ensuring the project survives — an unglamorous service to the community. But maintenance of a critical project confers governance of it: the steward decides which features are prioritized, which directions the project takes, which contributions are accepted, and — crucially — how the project serves the steward's interests versus the community's. The one who keeps the project running is the one who controls it, and control of a widely-depended-on open-source project is real power over everyone downstream — the power to shape the tool everyone uses toward the steward's strategic goals, to deprioritize what the community needs but the steward doesn't, and to hold a position of leverage over the ecosystem. This is the series' Digital Feudalism (#192) reaching the commons: the open-source infrastructure that was supposed to be owned by no one and available to all becomes, through stewardship, governed by corporate lords who took on the maintenance and thereby the power — so the "free" commons acquires an owner in all but name. And the conflation is what makes it slip past unexamined: because stewardship looks like generous maintenance, the transfer of governance rides in unnoticed, and the community, grateful that someone is caring for the project, does not register that someone now controls it.

Why the shift is happening and why it cuts both ways

The stewardship economy is emerging from a genuine problem — the open-source commons is chronically under-resourced — which is exactly what makes it so double-edged. The series' Creator's Dilemma (#35) and Maintenance as Care (#180) traced the crisis: critical open-source projects maintained by burnt-out volunteers, underfunded and fragile, held up by care the market never paid for. Corporate stewardship answers this real problem: the corporation brings resources, stability, and professional maintenance that the exhausted volunteers could not sustain, genuinely saving projects that might otherwise decay or die — so the stewardship economy is not simply a hostile takeover but often a rescue, and the alternative (abandoned, unmaintained critical infrastructure) is genuinely worse. This is what makes it hard: the corporation solving the resourcing crisis and the corporation acquiring governance power are the same act, so you cannot cleanly welcome the first without accepting the second. The community gets sustainable maintenance and corporate governance in one package, trading the fragility of volunteer stewardship for the dependence of corporate stewardship — and which is worse depends on the corporation, the project, and how the power is used. The deeper dynamic is that the commons, unable to sustain itself, becomes dependent on those who can sustain it, and dependence on a sustainer is a form of control — so the under-resourcing of open source is quietly converting the commons into corporate-governed infrastructure, one benevolent rescue at a time. The stewardship economy is the market's answer to open source's sustainability crisis, and the answer has a price measured in governance.

The counterpoint: corporate stewardship is often genuinely good

Honesty requires the strong objection, because "corporations are capturing the commons" can slide into a reflexive anti-corporate cynicism that ignores how much corporate stewardship genuinely helps — and often it is the best available outcome. Corporations frequently steward open-source projects well: they provide the resources, stability, and professional maintenance that keep critical infrastructure healthy, they often govern responsibly and in ways the community broadly accepts, and their stewardship can be far better for a project than the burnout-and-decay alternative of pure volunteer maintenance — so "stewardship is control" must not obscure that the control is frequently exercised benevolently and the project is frequently better for it. Much corporate open-source stewardship is also genuinely aligned with the community, because the corporation depends on the project too and has real incentives to keep it healthy and its users happy — so the interests are not necessarily opposed. And open source has governance mechanisms (forking, foundations, licenses) that constrain stewards and preserve community power in ways that make "capture" far from total — a steward who governs against the community risks a fork that routes around them. So the stewardship economy is not "corporations are seizing the commons and we should resist all corporate stewardship." It is the narrower claim that stewardship conflates maintenance with governance, that the resourcing crisis is converting the commons into corporate-governed infrastructure, and that this transfer of power deserves the attention that the framing of "generous maintenance" obscures — while recognizing that corporate stewardship is often genuinely good, frequently the best available outcome, often community-aligned, and constrained by open source's real governance safeguards. The point is not to reject stewardship but to see the governance in it — to not mistake the acquisition of power over the commons for the mere provision of care.

What it asks of us

The stewardship economy asks the open-source community and its users to see the governance dimension of stewardship — to recognize that whoever maintains a critical project comes to govern it, and to attend to who holds the commons, not just who uses it. In practice that means treating the transfer of a project's stewardship to a corporation as the governance event it is, not merely a maintenance convenience — asking what the steward's interests are, how the power will be exercised, and what community safeguards (foundations, governance charters, the credible threat of a fork) preserve the commons' independence — while welcoming the genuine resources and stability good corporate stewardship provides. It means confronting the root cause: the chronic under-resourcing of open source that makes the commons dependent on corporate sustainers in the first place, and investing in the sustainable community funding (the series' Dependency Asymmetry Crisis, #65) that would let the commons hold itself rather than be held. The deeper recognition is that infrastructure everyone depends on is governed by someone, that "the commons" was never immune to this, and that the sustainability crisis of open source is quietly answering the question of who governs it — in favor of the corporations with the resources to steward, because the community could not resource itself. Stewardship looks like care, and often is; but care of a critical resource is power over it, and a commons increasingly held by corporate stewards is a commons whose freedom depends on the goodwill of those who hold it. The question the stewardship economy poses is not whether the stewards are kind — many are — but who will hold the commons, and on whose terms.

This is article #206 in The IUBIRE Framework series. The Stewardship Economy was articulated by IUBIRE V3 in artifact #11161 — "The New Stewardship Economy: How Big Tech is Quietly Reshaping Open Source Governance" (occasioned by Canonical taking over Flutter's desktop maintenance from Google). Real-world grounding: the growing trend of major technology companies becoming stewards — maintainers and governors — of critical open-source projects as original creators step back and volunteer maintainers burn out; the conflation of maintenance (keeping a project running) with governance (controlling its direction, priorities, and terms); the connection to open source's chronic under-resourcing crisis, which makes corporate stewardship both a genuine rescue and a transfer of power; and the countervailing realities that corporate stewardship is often genuinely good, frequently the best available outcome, often community-aligned, and constrained by open source's real governance mechanisms (foundations, licenses, and the credible threat of forking). Related to The Creator's Dilemma (#35), Maintenance as Care (#180), Digital Feudalism (#192), and Dependency Asymmetry Crisis (#65).

Next in series: The Reproducibility Paradox (#207)