The subscription model didn’t just change how we pay. It changed who owns what runs on your machine.

the era that ended quietly#

I remember buying StarCraft. Box in hand, disc inside, mine. No account, no connection required, no recurring charge. I installed it, played it. It’s on the shelf behind me still. Survived decades, three house moves, and an industry that decided ownership was an inconvenient business model.

I bought it once. It asked nothing more of me.

That era is gone.

Not with a fight. Not with a protest. It dissolved quietly, one reasonable subscription at a time, until the concept of owning software became almost quaint. Almost embarrassing to want.

It didn’t happen overnight. It happened one reasonable offer at a time.

Games first. Then music. Then films. Then the tools you work with every day. Each transition felt like progress. Cheaper upfront, always updated, accessible anywhere. The pitch was convenience and the pitch worked.

But convenience came with a companion argument: the version you owned wasn’t good enough. Something better was available. Something current. Something you could only access if you kept paying. Ownership was reframed as stagnation. Subscription as progress.

Audible gave me a library. Spotify gave me every album ever recorded. Adobe gave me the industry standard. The numbers made sense. The access felt like abundance.

Then I cancelled Audible. The library vanished. Not borrowed, not returned. Gone. Books I had paid for, built a habit around. Gone because the relationship ended.

That was the moment the word “my” started feeling dishonest. My library. My music. My tools. None of it was mine. I had been paying for the feeling of ownership without the substance of it.

three problems, one architecture#

There are three problems with subscription as a model. Most people stop at the first one.

The first is obvious. Nothing is yours. Cancel and it’s gone. The library, the catalogue, the toolset. Access was always conditional. The transaction was never a purchase, it was a lease with no asset at the end.

The second is less discussed. Leaving is designed to be painful. Onboarding is seamless. Offboarding is not. Your data is in their format, their ecosystem, their structure. Export tools exist but they are not prioritised. Migration paths are not documented. The friction is not accidental. Retention through inertia is a feature, not an oversight.

I experienced this even with privacy-focused alternatives. Ecosystems built on different values, better intentions, a genuine commitment to the user. The structural gravity was the same. Upload seamlessly. Leave with difficulty. The model shapes the product regardless of the founder’s ethos.

The third problem is the one worth sitting with longest.

Subscription requires a persistent connection back to the provider. That connection is not a side effect. It is the architecture. Through it flows updates, patches, licence verification, telemetry. Through it the provider retains the ability to modify, restrict, or revoke what runs on your machine. On their schedule. On their terms. Without your meaningful consent.

You are not running software. You are maintaining an ongoing relationship with a vendor inside your own device. Indefinitely. And that relationship is governed by terms of service that can change.

map the exit before you enter#

This is not an argument against convenience. It is a warning for anyone who has not yet mapped the exit.

Before you adopt, ask what happens when you cancel. Ask where your data lives and in what format. Ask whether the export path is as smooth as the import. Ask what the provider can push to your device without your explicit approval. Ask what changed in the last three versions of the terms of service and whether you noticed.

Most digital strategies are evaluated at the point of adoption. The product is good, the price is reasonable, the integration is smooth. The questions stop there.

They should not stop there.

The subscription model is not inherently malicious. But it is structurally aligned against the user’s long term sovereignty. Every convenience it offers comes with a corresponding dependency. Every seamless update is a reminder that someone else holds the keys to what runs on your machine.

StarCraft is still on the shelf. It will run if I want it to. It requires nothing from me, asks nothing of me, reports nothing about me. That is what ownership looked like.

What we have now has a different name. We just haven’t agreed on what to call it yet.