Gabriel Mahia Systems · Power · Strategy

Technology and Power VIII — Open Source as Institutional Architecture

Open source software is not a free alternative to commercial software. It is a different model of institutional control over technological capability.

What Open Source Changes

Open source software — software whose source code is publicly available, modifiable, and redistributable — is typically characterised in terms of its cost: it is free, or nearly free, which makes it an attractive alternative to proprietary commercial software for cost-constrained institutions. This characterisation is accurate but misses the more strategically significant dimension of what open source changes: the control relationship between the institution and its technology infrastructure.

The institution that runs on proprietary commercial software is dependent on the vendor for every significant modification, security fix, and capability extension. The vendor's priorities, the vendor's roadmap, and the vendor's pricing decisions all constrain what the institution can do with its own technology infrastructure. The institution that runs on open source software has access to the source code — can modify it for institutional purposes, can fix bugs without waiting for vendor releases, and can extend capabilities in directions that the original developers did not prioritise.

The Governance Dimension

Open source software also has a governance dimension that proprietary software does not. The open source project is governed by a community of contributors whose interests include the project's technical quality, its alignment with diverse use cases, and its long-term sustainability — interests that are not identical to a single vendor's commercial interests. The institution that contributes to the open source projects it depends on participates in that governance, gaining influence over the project's direction in proportion to its contribution.

This governance participation is not available for proprietary software. The institution that depends on a commercial vendor's software is subject to the vendor's governance of the product — its prioritisation, its architectural decisions, and its end-of-life timelines — without the ability to influence those decisions beyond the leverage that its purchasing volume provides.

The Strategic Choice

The strategic choice between open source and proprietary software is not primarily a cost question. It is a question about the institution's desired relationship with its technology infrastructure: whether it prefers the support structure and predictability of a commercial vendor relationship, or the control and adaptability of an open source relationship that requires more internal capability to manage. Institutions with significant technical capability and strategic interest in controlling their own infrastructure direction should weight the open source option more heavily than the cost comparison alone would suggest.

Open source software is not free — it costs the internal capability required to manage it. But it purchases something that proprietary software cannot provide: the institutional control over the technology that determines what the institution can do and on whose terms.

Discussion