You Don't Own It: The Quiet Theft of Digital Ownership

There's a word for what Amazon did to Luna this month, and it isn't "evolving."

In April 2026, Amazon told Luna customers they could no longer buy games through the service. Worse, the games people had already bought would stop working in June. No refunds. The official explanation was that Amazon had "heard user feedback" and wanted to prioritize "easy access to great games" — a sentence that means nothing while implying everything. A day earlier, the same company cut off older Kindles from downloading new books, and arranged things so that anyone who factory-resets one of those devices ends up holding a brick.

This is not a story about Amazon. Amazon is just the company that happened to send the email this week. It's a story about a lie we've all quietly agreed to believe: that clicking "Buy" gives you something to own.

The "Buy" button that doesn't buy

When you purchase a digital game, an ebook, a movie, or a song from a major platform, you are almost never buying the thing. You are buying a license — a revocable permission to access the thing, on the platform's terms, for as long as the platform feels like honoring it. The button says "Buy." The contract says "Lease, terminable at our discretion, no refunds."

The gap between those two has always been there. It only becomes visible when the platform decides to close a service, change a strategy, or simply walk away from a product line. Then your library evaporates and you discover that the thing you "owned" was never on your hard drive, never in your hands, and never really yours.

This is the digital ownership dilemma in one sentence: convenience that you rent always beats ownership that you don't actually have, right up until the day it doesn't.

SaaS is the same trap, wearing a tie

What happens to games and books happens to everything delivered as a service. Software-as-a-Service is the same arrangement applied to the tools you work with every day.

• The note-taking app that held five years of your thinking raises its price, gets acquired, or shuts down — and your notes are trapped in a format only it can read.
• The cloud photo service "sunsets" a feature, re-compresses your images, or starts charging for storage you assumed was permanent.
• The productivity suite changes its terms, and overnight your documents live somewhere you can't reach without a subscription.
• The smart-home hub's company folds, and your lights, locks, and thermostats become expensive plastic because the servers they phoned home to no longer answer.

In every case the pattern is identical: someone else owns the thing your life runs on, and "ownership" for you means a monthly invoice and a hope that they don't change their mind. You are not the owner. You are the product's tenant, and the lease has a termination clause you never read.

The cloud is just someone else's computer

We've been told "the cloud" for so long that we forgot what the word is hiding. The cloud is not a place. It is someone else's computer, in someone else's building, governed by someone else's terms. When you run your company on it, the question is never just "is it up?" The question is "who owns what, and what happens to me when they decide differently?"

The infrastructure your business depends on can change its pricing overnight, deprecate the API your product was built on, lock your account during a billing dispute, or get acquired by a competitor. None of these are edge cases. They're Tuesdays. And in each one, the thing you thought was a capability you had turns out to be a capability you rented — and the landlord just changed the locks.

In-house is the opposite arrangement. It costs more up front: hardware, setup, the engineer-hours to run it. But the ownership is real. The servers are yours, the data never leaves, and no third party can reach in and switch you off because their roadmap changed. You trade a low monthly fee for actual control. Most companies make the opposite trade without ever noticing they made it.

The deepest dependency: you outsourced the expertise too

Here's the part almost nobody talks about, and it's the most dangerous of all.

When you adopt AI coding tools as a service — GitHub Copilot, hosted assistants, cloud-based pair programmers — you're not just renting a tool. Over time, you're quietly renting your team's competence.

Ask the uncomfortable question: if the service went dark tomorrow, could your developers still ship?

Not "would it be slower." Could they do it at all? If half the codebase was written by an assistant that explained nothing, and the engineers learned to prompt instead of to understand, then the day the API key stops working is the day your delivery capability stops working. The features dry up. The bugs pile up. And you discover that the knowledge to run your own product was never in your building — it was in someone else's data center, and you were leasing access to it one autocomplete at a time.

This is the ownership dilemma at its sharpest. You don't own the tool. You don't own the data. And now you don't even own the expertise — the one asset you assumed was unquestionably yours, because it lived in your own people's heads. Except it didn't. It got offloaded, prompt by prompt, until the org carried a dependency it couldn't see and couldn't survive losing.

The fix isn't to ban the tools. It's to stay the owner of the capability while using them. Use AI to go faster, but make sure your engineers still understand what was written and why. Run models you control — local LLMs through Ollama and Open WebUI on your own GPU — so the assistant can't be revoked, rate-limited, or turned into a subscription line item that holds your roadmap hostage. The goal is a team that uses the tool, not a team that is the tool's output.

If you can't function without it, you don't own your work. You're just borrowing it.

The alternative isn't paranoia — it's open source

The answer isn't to unplug and move to a cabin. It's to shift where the control lives. The opposite of renting your digital life from a megacorp is owning it through open source and self-hosting — and in 2026, that path is more accessible than it has ever been.

Consider the swaps:

• Instead of a cloud office suite you don't control, there's LibreOffice or OnlyOffice — files in open formats, on your machine, readable in ten years without anyone's permission.
• Instead of a photo service that can re-compress or paywall your memories, there's Immich or PhotoPrism running on a box in your home.
• Instead of a notes app that owns your second brain, there's Obsidian (plain Markdown files you can read with anything) or Joplin.
• Instead of a cloud drive, there's Nextcloud, syncing your files to hardware you can put your hand on.
• Instead of a chatbot whose provider logs, trains on, and rate-limits your every prompt, there's a local model running on your own GPU through Ollama and Open WebUI — private, free, and yours.

The trade is real and worth naming honestly. Self-hosting asks for time, a little learning, and the occasional evening spent reading documentation. SaaS asks for none of that — until it asks for everything. The difference is who holds the kill switch. With open source, it's you. With SaaS, it's a stranger optimizing a quarterly metric you'll never see.

What ownership actually means

Real ownership has properties that no "Buy" button on a closed platform can give you:

• The data is on hardware you control. Not "in the cloud" — on a disk you can hold.
• The format is open. You can read your files with more than one program, today and in a decade.
• No remote kill switch. No company can reach across the internet and disable what you have.
• You can leave. Export, migrate, fork the code, host it elsewhere. The exit door is never locked.

That's the whole point. Open source isn't about ideology or saving a few dollars on subscriptions. It's about the difference between access and ownership — between a thing that works because someone permits it to, and a thing that works because it's yours.

The takeaway

Amazon didn't steal anyone's games. Legally, it took nothing, because legally those games were never yours to take. That's exactly the problem. The Luna email and the Kindle bricking aren't aberrations; they're the system working as designed, just with the curtain briefly pulled back.

So the next time a "Buy" button promises you ownership, read it as a lease. And when you can — for your files, your photos, your notes, your tools, your AI — choose the version you actually own. Run it yourself. Keep it open. Hold the kill switch.

Because the only digital thing you truly own is the one nobody else can turn off.