When the license server disappears, did I really buy the software?

I’m willing to pay for professional software, but I’m uneasy when “buy” really means “keep our account in good standing.” One-time DRM that verifies a transaction and leaves a local license is very different from continuous cloud permission to launch an already-paid-for copy. The latter adds a failure mode that has nothing to do with whether the software still works.

Concrete scenario: I buy a non-subscription Linux application, download the installer, and activate it through the vendor account. Years later, the company shuts down authentication. The installed binary still runs, but a replacement machine cannot be activated. An account ban creates the same problem, even when the purchase itself was legitimate.

I understand server checks can reduce piracy, credential sharing, and fraud. Still, should vendors provide perpetual offline builds, exportable license files, or a controlled resale/transfer process? Are offline access and transferability realistic definitions of digital ownership? Counterarguments and examples welcome.

The security case is stronger than “DRM is always bad.” A signed local license can establish entitlement without keeping the vendor as an online gatekeeper, but it also becomes something people can copy or manipulate. I’d support offline operation after activation, with bounded support for abuse rather than permanent cloud dependence.

The legal answer is much less universal than the ownership language suggests. The EU’s UsedSoft decision recognized resale for some licenses granted indefinitely for payment, under conditions, but that does not automatically cover subscriptions, account licenses, or the U.S. market. Transferability is a reasonable policy proposal, not a settled general right.

The replacement-machine case is the one vendors should design around. A downloadable installer plus a signed certificate, recovery process, and documented deactivation path would cover ordinary continuity without requiring every activation to be live forever. “We might shut down someday” is exactly why recovery cannot depend on support staff.

From a small developer’s perspective, a resale system sounds expensive and easy to abuse. I’d rather promise a perpetual offline build and make transfer optional, with clear limits. That preserves the buyer’s practical investment without forcing a tiny vendor to build a used-software marketplace.

There’s a distinction between ownership and continuity. If the contract clearly sells access to an account, the buyer may have accepted that risk—even if the wording feels unfair. I’d like to see vendors state the failure plan before purchase: offline installer, license export, and what happens after a ban or shutdown.