Philosophy · Digital Ownership
The Right to Repair (and Host)
Self-hosting isn't just a technical choice — it's an assertion of digital ownership in a world where "buying" software increasingly means renting access to someone else's computer.
Self-hosting isn't just a technical choice — it's an assertion of digital ownership in a world where "buying" software increasingly means renting access to someone else's computer.
★ Why This Matters
In 2026, most people don't own the software they depend on. They rent access to it — revocable at any time, subject to price changes, terms-of-service updates, or outright shutdown. The Right to Repair movement won the battle for tractors and smartphones. The next frontier is the server: the right to run the software that handles your data, on hardware you control, without asking permission.
If you've followed Right to Repair at all, you know the playbook. John Deere tells farmers they don't actually own their tractors because the software is licensed. Apple uses weird screws and serializes parts so replacements don't work. HP pushes firmware that bricks your printer for using third-party ink. I've watched this pattern repeat for years.
Then one day I realized: cloud services do the exact same thing, just without the screws. The pattern is identical:
Now swap "physical object" for "your data." Swap "software inside" for "the cloud service holding your files." Swap "authorized repair" for "monthly subscription you can't cancel without losing everything."
It's the same fight. Self-hosting is just Right to Repair for the digital stuff — your email, family photos, notes, calendar, all of it.
Most people under 30 have never actually "installed" software. They've created accounts. Downloaded apps. Clicked "accept" on terms of service they didn't read. The idea that you could buy a program once, with actual money, and run it forever on your own machine — no permission needed — sounds almost fictional to them.
This wasn't an accident. It was a business model. Here's how I watched it happen:
Software came in boxes. You bought a copy. You owned it. Install it, reinstall it, use it forever. The company might release version 2.0; you could ignore it if version 1.0 still did what you needed.
"Activation" showed up. Your software phoned home to verify it was "legitimate." The disc was still yours, but now there was a remote kill switch. I remember the first time my Adobe suite refused to open because the activation server was down. That was a warning I didn't heed.
SaaS took over. You stopped installing things and started logging into websites. The software was "free" — which meant you weren't the customer, you were the product. Your data, your attention, your eventual upgrade. Adobe went subscription-only in 2013. I remember that too, because I paid for it.
Hardware got subscription-tethered. Smart home devices that need cloud accounts to function. Car manufacturers experimenting with heated seats as a monthly subscription. I bought a thermostat that stopped working during an internet outage. That was the moment I started questioning everything.
Average household: $200–$600/month in digital subscriptions. Most hold irreplaceable data. If any one of them shuts down, changes terms, or decides you violated a policy, your data goes with it — and sometimes your physical devices stop working too. I've helped people recover from this. It's never fun.
The software industry has messed with our vocabulary on purpose. "Buy" doesn't mean buy anymore. "Your library" doesn't mean you own the books. "Lifetime license" means lifetime of the product, not your lifetime. I've read the fine print. You should too.
Here's how I actually define ownership. You own software when all five of these are true:
By that standard, almost nothing I pay for actually qualifies as "owned." SaaS fails all five. Most "perpetual license" desktop software fails at "no remote kill switch" — try running it offline for a month and see what happens. Even some open-source projects fail "you can run it" because they deliberately cripple the self-hosted version unless you also connect to their cloud.
This isn't abstract. I've helped people through these situations, and they're devastating:
These aren't edge cases. They're what happens when your data lives on someone else's computer, under someone else's rules, and the only interface you have is the one they choose to give you.
I'll never forget sitting with that friend while she processed the journal loss. There's this look people get — not anger, not sadness, but a kind of hollow disbelief. She kept opening the app, closing it, opening it again, as if the data might reappear. I wanted to fix it. That's my reflex — give me a terminal, I'll find something. But there was nothing to find. So I just sat there, handed her coffee, and let it be awful. That's when I realized: data recovery is emotional labor first, technical labor second. Before you can rebuild, someone has to witness what you lost. If you're reading this and you've had that "hollow disbelief" moment, I see you. It sucks, and it's not your fault.
I don't use the word "political" lightly here. But when you self-host, you're making a statement about who gets to make decisions about your data:
This isn't just me being picky about my setup. It adds up. Every person running their own file sync or home automation is one less data point getting vacuumed up and sold. You don't need to change the whole system. You just need to pull yourself out of it.
★ The Practical Reality
Full disclosure: I don't self-host email. It's genuinely hard, and the deliverability problems aren't worth it for me. But self-hosting most other things — files, notes, calendar, contacts, RSS, passwords, home automation, media — I've done all of that on a Raspberry Pi, a weekend, and enough patience to read documentation when something didn't work. The bar is lower than most people think. See our 30-Day Exit Strategy guide if you want the step-by-step.
Right to Repair has actually won some battles. As of 2026:
But here's what's missing: none of these laws touch the hosting side. There's no requirement that cloud services provide a self-hostable export. No rule saying smart devices must work offline. No disclosure requirement for how long the cloud service backing your physical device will actually exist.
Those gaps matter. But here's the thing: you don't need to wait for legislation. The most effective advocacy I've found is just doing it — proving self-hosting works, writing down how you did it, and making the next person's path easier.
Continue the Series
This article is part of TechLounge's Tech Philosophy & Digital Wellness series. Read The Case for Slow Tech for the philosophical framework, or Combatting App Fatigue for practical strategies to consolidate your digital life.
Your perspective shapes our future content.
Share your experiences with SaaS shutdowns, data lock-in, or the moment you decided to take control.