What Is Open Source Software?
Open source software is software whose source code is publicly available. Anyone can read it, study it, modify it, and distribute it — usually for free, and usually without permission from the original authors, as long as they comply with the license terms.
This is the opposite of proprietary software, where the source code is secret, owned by a corporation, and distributed under restrictive licenses that control how you can use it.
The distinction matters enormously for sovereignty. Proprietary software is a relationship of dependency: you are allowed to use the tool, at a price the vendor sets, on terms they can change, until they decide to stop supporting it. Open source software is a relationship of ownership: you have the code, you can run it yourself, you can fix it, you can fork it, and no corporation can take it away from you.
The History Is Intentional
Open source software is not an accident. It emerged from a deliberate political project.
In 1983, software pioneer Richard Stallman launched the GNU Project with an explicit philosophical position: software that controls important social functions must be free — free to use, free to study, free to modify, free to redistribute. He called this “free software,” using “free” to mean freedom, not price.
The Free Software Foundation, which Stallman founded in 1985, articulated four essential freedoms:
- The freedom to run the program as you wish
- The freedom to study how the program works and change it as you see fit
- The freedom to redistribute copies
- The freedom to distribute copies of your modified versions
These are not technical specifications. They are political commitments. The argument was — and remains — that software is infrastructure, and infrastructure that controls people’s lives must be accountable to those people, not to private corporations.
The term “open source” emerged in 1998 as a more business-friendly framing of the same fundamental idea, emphasizing practical benefits over political philosophy. Most of what people call open source today descends from this tradition.
What Open Source Powers Today
If you have used the internet today, you have used open source software. The evidence:
- Linux powers over 90% of the world’s web servers, all Android phones, and virtually all supercomputers
- Firefox is an open source web browser
- Apache and Nginx serve a majority of websites globally
- Python, PHP, Ruby, and JavaScript (Node.js) are all open source programming languages
- MySQL and PostgreSQL are open source databases
- WordPress powers 43% of all websites on the internet
- Kubernetes orchestrates containers across cloud providers
- The Linux kernel is the core of Android, ChromeOS, and countless embedded systems
The infrastructure of the modern internet was built primarily by open source contributors — many of them unpaid, working from principle.
Why It Matters for Sovereign Builders
For builders who prioritize economic and technological sovereignty, open source is not a preference. It is a requirement.
Auditability: Proprietary software can do anything to your data — collect it, sell it, encrypt it, report you to law enforcement — and you would never know. Open source code can be read and audited. You know exactly what it does.
No vendor lock-in: When you build your business on an open source database like PostgreSQL, no company can raise your prices arbitrarily, change their terms, or shut down and take your data with them. The software exists independent of any company.
Community maintenance: When a single company stops supporting proprietary software, it dies. When an open source project loses its primary maintainer, the community can fork it and continue development. The code does not die with the company.
Cost: The most powerful databases, web servers, programming languages, content management systems, and development tools in the world are free. Proprietary software has historically been used to extract rent from builders who cannot access equivalent free alternatives. Open source eliminates that rent.
Customizability: You can modify open source software to suit your exact needs. If a feature is missing, you can add it. If a behavior is wrong for your use case, you can change it.
Understanding Open Source Licenses
Not all open source is the same. The license determines what you can do with the code:
GPL (GNU General Public License): If you use GPL code in your product and distribute it, you must release your modifications under the same GPL license. This ensures that improvements flow back to the community. Linux uses GPLv2.
MIT and BSD licenses: Very permissive. You can use, modify, and distribute the code — even in proprietary products — with minimal restrictions. You just have to include the original copyright notice.
Apache License 2.0: Similar to MIT/BSD, adds explicit patent rights and requirements around notating changes.
AGPL (Affero GPL): Like GPL, but extends the copyleft requirement to network use. If you run modified AGPL software as a service, you must release your changes. This is increasingly popular for preventing cloud providers from building proprietary services on top of community-developed code.
For sovereign builders, the GPL family aligns most closely with the underlying values. Permissive licenses allow Big Tech to take open source code, improve it internally, and return nothing to the community — which is exactly what Amazon, Google, and Microsoft have done repeatedly.
How to Participate
Using open source is the entry point. Contributing deepens your stake.
Contributing does not require writing perfect code. Open source projects need documentation, bug reports, translations, design work, and testing. If you find a bug, report it. If the documentation confused you, write a clarification. If you add a feature for your own use, share it upstream.
Platforms for finding and contributing to open source: GitHub, GitLab, Codeberg. Many projects also have mailing lists, IRC channels, and Matrix rooms.
The open source ecosystem is one of the largest examples in modern history of collective production for shared benefit. Learn it. Use it. Contribute to it. And when you build, build in the open when you can — so that the next person does not have to start from scratch.