Self-Hosting Is Political
Running your own infrastructure is a small assertion of autonomy against platforms built to make autonomy impossible.
Lorenzo ScaturchioLos AngelesAbout the author →
ExplorePower & institutionsTechnology & attention

Beyond the hobby
When someone mentions they run their own email server, the typical reaction is bemusement. Why bother? The major providers are free, reliable, and convenient. Self-hosting looks like a hobby, something technically inclined people do for fun or stubbornness, without practical justification.
That framing misses everything.
Self-hosting isn't primarily a technical practice. It's a political one. Running your own infrastructure, email or cloud storage or communication tools, is an assertion of autonomy in a digital environment built to make autonomy impossible.
And yes, it's difficult. The difficulty is the point. Not because suffering is virtuous, but because it reveals how thoroughly our digital lives have been captured by entities whose interests diverge from ours.
The material basis of digital freedom
Freedom isn't abstract. It has a material basis.
In physical space this is intuitive. Owning your home means something different than renting it. These material conditions don't guarantee freedom, but their absence constrains it.
Digital space works the same way.
If your email flows through someone else's servers, they can read it, analyze it, terminate your account and make a decade of correspondence vanish. If your files live in someone else's cloud, they exist at that someone's pleasure. If your communications depend on a platform, that platform controls the conditions of your speech.
Self-hosting changes the equation. Not completely. You're still dependent on ISPs, on the broader internet, on the companies that manufacture hardware. But you've moved up the dependency chain, into a position where your digital existence doesn't ride on any single entity's continued goodwill.
That's not nothing. It's sovereignty. Limited, contested, but sovereignty nonetheless.
Why platforms don't want this
Major technology platforms have spent years making self-hosting harder. Not through technical limitations, since the technology has never been more accessible, but through design choices, market power, and the creation of ecosystem dependencies.
Email is the clearest example. I build software for a living, and running an email server that actually works, where your messages get delivered instead of filtered as spam, is one of the more thankless things I know how to do. Not because the protocols are complex; they're ancient and well-documented. It's that the major providers have built a web of authentication requirements, reputation systems, and filtering rules that systematically disadvantage small independent servers.
Is this about fighting spam? Partially. It's also about consolidation, about making independent operation so difficult that people give up and use the big providers, who can then mine their communications for advertising data.
Similar dynamics play out everywhere else. Closed protocols, proprietary formats, APIs that get restricted or shut down the moment they enable competition. Ecosystems designed around lock-in, where leaving means losing years of accumulated data and connections.
Independence is discouraged because dependence is the business model.
The knowledge gap as control mechanism
There's another barrier beyond the technical. It's the knowledge gap, and the gap is maintained deliberately.
Most people don't know self-hosting is possible. They've never encountered the idea that alternatives to major platforms exist. Their mental model of the internet is platforms all the way down: you use services, you don't run them.
This ignorance isn't natural. It's produced.
Consumer technology is designed to hide its own mechanics. Interfaces are simplified to the point of abstraction, and users interact with friendly facades that obscure the systems underneath. The goal is a frictionless experience, which in practice means rendering users passive consumers rather than active participants.
Schools don't help. Digital literacy curricula focus on how to use platforms, not how to understand or replace them. The skills needed for autonomy, system administration and networking and security, get treated as specialist knowledge rather than general competence.
So most people never realize there's a choice. They accept platform dependence as the natural order of digital life, unaware that another way exists.
Self-hosting as resistance
In this context, self-hosting becomes resistance. Not metaphorical resistance, but actual resistance to specific power structures.
Start with surveillance. Your data lives on machines you control, so nobody's mining your communications for advertising profiles or building behavioral models out of your cloud storage. The information that platforms convert into profit stays out of their reach.
Then there's continuity. You can't get banned from your own server, and no algorithm can suspend your account. The work you've built and the data you've accumulated don't hang on some company's content moderation decisions or its next change of strategy.
The process also teaches you how digital systems actually work. It demystifies the technology and builds a capacity for independence that outlasts any particular service. People who understand systems adapt when conditions change. People who only understand interfaces are trapped when those interfaces disappear.
And every self-hosted server is a node in a more distributed internet. The more nodes, the more resilient the network, and the harder it becomes for any single entity to control digital space.
The collective dimension
Individual self-hosting has limits. Not everyone has the time, skills, or resources, and expecting universal self-hosting as a solution to platform power is unrealistic and slightly callous.
But self-hosting doesn't have to be individual.
Small groups can pool resources to run shared infrastructure. Communities can host services for their members. Collectives can offer alternatives to corporate platforms without requiring every user to become a system administrator.
This is how the internet worked before platform consolidation: not individual self-hosting but distributed hosting by institutions, communities, and organizations of various sizes. Universities ran servers, businesses ran servers, nonprofits ran servers, and the infrastructure was spread across countless independent operators, none of them dominant.
That model can return. It needs people with technical skills sharing them, building accessible tools, standing up organizations dedicated to alternatives. It's already happening in pockets, in community mesh networks and collectively-run communication platforms and cooperative cloud services. It just needs to scale.
The politics made explicit
So: self-hosting is political.
It challenges platform power, creates alternatives to surveillance business models, and demonstrates that another way of organizing digital life is possible. It's political the way the platforms themselves are political. They aren't neutral infrastructure. They're private governments that set the rules for digital life according to their own interests, and opting out of that governance, to whatever extent you can, is a choice with a politics to it.
Underneath all of it sits one question: who controls digital infrastructure? A handful of corporations, or many independent operators? Publicly owned, cooperatively managed, individually held? Those are questions about power, and questions about power are political by definition.
The path forward
None of this means self-hosting is easy or accessible or appropriate for everyone as it stands. The barriers are real, the learning curve is steep, the time investment is substantial.
But those barriers aren't fixed. They can be lowered through better tools, better documentation, better community support. The goal isn't to shame people who use platforms, since everyone does, out of necessity if nothing else. The goal is to expand what's possible, to create options where none exist, to show that dependence is a choice rather than a fate.
Every person who self-hosts makes the practice slightly more normal. Every tool that makes it easier widens the pool of people who can participate.
The internet wasn't always captured by platforms, and it doesn't have to stay that way. But returning it to something more distributed takes people willing to do the unglamorous work of maintaining alternatives, and not only for themselves. For whoever decides, some morning, that platform dependence is intolerable and goes looking for another way. The other way only exists if someone kept it running.
Enjoyed this?
An email when I publish something new. That is the whole list; I have never sent it for any other reason.
Get notified when I publish new articles. Unsubscribe anytime.