A perpetual license should survive the vendor

I've paid for several desktop tools sold as “perpetual” licenses, only to discover that perpetual really means “useful while the activation service exists.” That feels like a technical dependency being hidden inside a sales term.

Ableton Live 12 is a good example. It can be authorized offline, but getting the authorization file still involves an Ableton account and a server-generated `.auz` file. If that infrastructure disappeared, a disk failure or hardware replacement could leave a legitimate purchaser stuck. That last scenario is hypothetical, but it exposes the gap between owning a version and merely having permission to keep asking for it.

I understand why vendors avoid preserving vulnerable builds, third-party components, source code, and indefinite support obligations. The obligation should be narrower: no new features or patches, just a technically enforceable fallback—an offline unlock, escrowed activation key, or final self-hostable build. Would offline unlocks, source escrow, or another mechanism be the fairest definition of digital ownership? Real-world examples and counterarguments welcome.

I’d separate “should be required” from “is currently required.” As a policy proposal, this is coherent; as a legal entitlement, the thread would need much more jurisdiction-specific work. I also think the fallback should be disclosed at purchase time, not quietly created after a shutdown is announced.

An offline key is not automatically a security problem. The real questions are scope, revocation, and whether it can be copied into a cracked distribution. I’d prefer a signed, version-specific license with no recurring check-in. Source escrow is much harder because it expands the attack and disclosure surface.

The commercial difficulty is that “final build” still creates support expectations, even if the contract says otherwise. A small vendor may reasonably choose a clean shutdown over maintaining an escrow arrangement. Still, putting the fallback terms beside the price would let buyers value that risk instead of discovering it later.

For me the minimum is a portable license artifact that can be backed up and restored without contacting the vendor. It needn’t make the software future-proof. It just needs to preserve the exact version purchased on hardware the owner controls.

I’m not convinced “paid once” implies permanent technical usability. Some software depends on services by design, and a perpetual license may only promise access to a defined release. The stronger argument is transparency: if server dependence can invalidate reinstalls, that limitation should be impossible to miss before purchase.

Source escrow sounds attractive until proprietary libraries and abandoned build systems enter the picture. I’d rather see a reproducible final installer plus a signed offline unlock. Less ambitious, but more likely to be deliverable by a two-person shop.

There’s also a privacy angle. Requiring periodic activation turns ownership into an identity relationship with the vendor. A local license with optional updates would reduce both surveillance exposure and outage risk without asking anyone to keep insecure network services alive.

The old-fashioned answer was an installer, a serial number, and a box you could keep on a shelf. It wasn’t perfect, but at least the shelf did not have an uptime target. I’d take that, with clear security warnings, over perpetual software that expires by server accident.