Document
The alarm that wakes you, the system that processes your payment, the platform through which you communicate, the database that holds your medical history — none of this is neutral machinery operating in the background.
It is infrastructure under active ownership, and that ownership is exercised. The data these systems extract is not merely stored; it is analysed, monetised, and used to shape behaviour — what you see, what you buy, what you believe. The dependence is not passive; it is harvested.
Governments administer citizens through software. Hospitals sustain life through software. Courts, schools, power grids, water supplies — the operational skeleton of modern society is code running on machines owned by particular people under particular arrangements.
That this is largely invisible does not make it less determining. The less visible the infrastructure, as a rule, the more complete the extraction. What is observed can be predicted; what is predicted can be manipulated; what is manipulated ceases to be the autonomous action of a citizen and becomes the managed response of a subject.
What is genuinely new in the present moment is not that infrastructure has owners — it always has — but the scale, the intimacy, and the deliberateness of this particular ownership. Software follows you inside the home, inside the conversation, inside decisions about work and health and association. It observes, it records, it shapes what is visible and what is not.
Those who build and control these systems set the operative rules of daily life — not by decree, but by design, and increasingly by algorithmic intervention whose logic is known only to its architects. The purpose of this architecture is not merely efficiency; it is the systematic conversion of human attention, behaviour, and political disposition into extractable value.
Technology is not inherently good or bad. It has never been neutral. The question that matters is not whether software shapes the conditions of human existence — it does, and with a thoroughness that earlier forms of infrastructure rarely achieved — but who controls it, and in whose interest that control is exercised.
Democracy and the commons
These corporations do not merely own the platforms through which people shop, communicate, organise, and participate in civic life. They actively work to ensure that no alternative can flourish.
Through lobbying, regulatory capture, strategic litigation, and the drafting of trade agreements, they have constructed a legal and technical environment in which libre software is systematically disadvantaged — deprived of public funding, excluded from procurement, rendered legally precarious.
This is not negligence; it is strategy. The enclosure of the digital commons is actively maintained by interests that understand, correctly, that unrestricted access to infrastructure would dissolve their capacity to extract rent from every transaction, every communication, every byte of behavioural data.
The power thus concentrated is unprecedented in scale and unaccountable by design. A dozen individuals now control communication systems used by billions, commerce platforms that determine which businesses survive, and cloud infrastructure upon which governments themselves depend.
This is not merely economic dominance; it is the accumulation of capacity to shape political discourse, to elevate or silence particular voices, to determine what information is visible and what is buried.
These individuals are accountable neither to electorates nor to the jurisdictions in which they operate. They purchase the legislative outcomes they require, secure regulatory forbearance through the threat of capital flight, and treat democratic institutions as obstacles to be managed rather than authorities to be respected.
The consequences are concrete and observable. Surveillance is not merely a capacity but a business model — the detailed recording of behaviour, location, association, and sentiment, sold to advertisers, insurers, employers, and state agencies.
Manipulation is not an aberration but a feature — algorithmic systems designed to maximise engagement by exploiting psychological vulnerability, regardless of the social or political consequences.
Suppression is not theoretical — the same infrastructure that connects dissidents also identifies them, the same platforms that enable organisation also provide the data by which it is disrupted.
When governments seek to control their populations, they do not need to build new systems; they rent access to those already built by corporations whose interests align with authority.
Libre software is one of the few structural responses to this concentration that does not depend on the forbearance of the powerful. It creates a digital commons — infrastructure that cannot be enclosed because its terms of use are irrevocable.
A small enterprise in rural Portugal operates on the same foundation as a research institution in Berlin. A journalist or an activist uses tools whose behaviour cannot be altered by a government or a company at a moment of inconvenience.
The commons is not merely an alternative; it is a form of resistance against the privatisation of the public sphere.
This is not a minor consideration. The capacity to communicate, organise, and conduct commerce without the infrastructure of that activity being turned against you is a precondition of meaningful participation in public life.
Supporting libre software is, in consequence, an act with political dimensions that its quiet and technical character tends to obscure. The tools and organisations building democratic digital infrastructure are described elsewhere.
The logic of the commons
There is an economic argument for libre software that is distinct from the philosophical one, and it is worth examining on its own terms.
When a business commissions an improvement to a libre software system — a new integration, a security fix, a feature that addresses a specific operational need — that improvement, by the terms of the licence, returns to the common pool. Every other business using the same system benefits from that investment without bearing its cost. The logic runs in both directions: every improvement that others have funded or contributed is equally available, at no further charge.
This is sometimes described as a commons model, and it has consequences that compound over time. A problem that costs a single business five thousand euros to solve costs a hundred businesses sharing the same software fifty euros each — or nothing, if someone upstream has already solved it. The quality of the software improves with each contribution, which draws more users, which produces more people identifying problems, more developers addressing them, more businesses investing in further improvements. No single party extracts the whole of the value created — it is distributed, by design, across everyone who participates.
The contrast with proprietary software is instructive. In a proprietary model, every improvement is owned by the vendor and monetised in every sale. The user pays not once but continuously, for access to improvements that were partly funded by the aggregate of previous payments. In a commons model, the investment circulates rather than accumulates at a single point.
When you support a project of this kind — through use, through funding, through honest feedback — you are acting as a patron of infrastructure that serves not only your immediate interests but everyone who depends on the same foundation. The libre business tools that operate on this logic are described in more detail elsewhere.
Why licences matter
Every piece of software arrives with terms — explicit or assumed — that determine who holds authority over it and what everyone else is permitted to do. Those terms, taken together, fall into three categories that are not merely technical distinctions but different settlements between the people who make software and the people who depend on it.
- Closed (proprietary) software
- The source code is withheld. The logic of the system — what it does, what it records, what it transmits — is known only to its makers. You may use it under conditions they set, for as long as they permit, at a price they determine. If those conditions change, or the product is discontinued, or the company is acquired, you have no recourse other than compliance or departure. The operational knowledge you have built around the system is, in effect, hostage to their continued goodwill. Most of the business tools that carry familiar names — Microsoft Office, Salesforce, Shopify — are held on exactly these terms.
- Open source software
- The source code is visible, which is not without value — security researchers can examine it, developers can learn from it. But visibility is not the same as freedom. A project can be open source while remaining under the effective control of a single corporation, which retains the authority to change direction, alter licensing, or close the commons whenever it becomes commercially convenient. The term has been adopted by marketing with sufficient enthusiasm that it no longer reliably signals anything about governance or user rights.
- Libre (free/freedom) software
- The distinction here is not of degree but of kind. Libre software — the word taken from the Spanish and French for freedom, to avoid the ambiguity of the English "free" — guarantees four specific rights: to use the software for any purpose, to study how it works, to modify it, and to distribute modified versions. These rights are not granted conditionally or revocably. They are embedded in the licence and hold regardless of who owns the company that originally wrote the code. No single entity controls libre software. Those rights, once granted, cannot be withdrawn. The licences and organisations that protect these rights are examined in more detail elsewhere →
Owning your infrastructure
Consider what it means to build a business on infrastructure you do not own. The terms can be changed without your consent. The data you have accumulated can be held, examined, or transferred according to someone else's policies.
The tools you have become operationally dependent on can be withdrawn, degraded, or repriced according to considerations entirely unrelated to your situation. You are not a customer in any meaningful sense — you are a tenant whose lease contains clauses you have not read, governed by a landlord you cannot negotiate with.
This is the ordinary condition of most businesses today, and it is accepted largely because the alternative has seemed technically demanding. It need not be.
Running your operations on libre, self-hosted infrastructure means, with some precision:
- Your data remains yours. It resides on hardware under your control, subject to jurisdictions you understand, accessible only to those you have explicitly authorised.
- No third party holds a switch over your operations. You are not subject to another organisation's terms of service, their policy changes, their financial difficulties, or their decisions about which customers are worth retaining.
- Costs are determined by what infrastructure actually costs — servers, maintenance, support — not by a vendor's assessment of what the market will bear this quarter.
- When your requirements change, the software can change with them. You are not waiting on a roadmap written for someone else's priorities.
None of this is an ideological position. It is the same practical logic that leads serious businesses to own their premises rather than rent indefinitely, to maintain their own records rather than trust a single intermediary, and to avoid concentrating their supply dependencies in a single point of failure. How to build your own sovereign infrastructure is addressed in more detail elsewhere →
Sovereignty Models
Three distinct arrangements exist, each corresponding to different levels of operational maturity, capital availability, and risk tolerance. An organisation may select the model appropriate to its current circumstances; transition between models is supported but never required.
- Shared Infrastructure
- Operation proceeds on the OpenBSD tilde community — production-grade servers where teams may learn administration in live environments with minimal initial investment. Suitable for evaluation, training, and low-criticality operations.
- Hosted Sovereignty
- Deployment on dedicated virtual machines or bare metal within managed facilities, maintaining full root access and custom configurations. The client controls the software stack while physical security and network operations remain managed by the provider. Suitable for production workloads without immediate capital expenditure or facilities management.
- Complete Autonomy
- Deployment on client premises with comprehensive documentation, training programmes, and automated tooling that enable the team to assume total control. The client owns the complete stack — hardware, software, and operational expertise. Suitable for organisations requiring full custody and long-term independence.
The appropriate model is determined by organisational readiness rather than any prescribed sequence. Further detail on each arrangement is available here.
The broader ecosystem
This project does not exist in isolation. Across Europe, public administrations, critical-infrastructure operators, research institutions and private enterprises have already moved substantial portions of their operational stack to libre foundations. Hardened OpenBSD deployments protect high-assurance environments in several member states; national and EU-level initiatives for sovereign cloud and AI infrastructure continue to expand; and countless organisations — from small enterprises to large governmental bodies — operate on self-hosted systems whose improvements return to the commons. The solution space is mature, documented, and populated. This project participates in that wider movement rather than claiming to originate it.
<< | Why | >>