A paid license should survive the license server

I maintain a few Linux workstations with paid creative and development tools, and the license server is often the least reliable part of the arrangement. If a vendor has a temporary outage, shuts down, or retires a product, customers should receive a signed, locally stored “last-known-good” activation token—or an offline build—that keeps the version they paid for usable.

That should not include future updates, new features, cloud storage, or online services. Machine binding, expiration rules, and cryptographic signatures can address plenty of security and piracy concerns. I understand why vendors are cautious. I’m less comfortable with software that can be disabled overnight by a remote system, though. At some point, “ownership” seems hard to defend as a meaningful description of what the customer has, even if the legal terms say license.

Should continuity like this be a legal requirement, an industry standard, or simply a feature customers should demand? Counterexamples welcome.

Technically, this is a fairly ordinary resilience feature, not magic. A signed token can identify the machine, product, and exact entitlement, then be verified without contacting home. The harder question is key recovery and support after shutdown, but that is an operations problem. I’d separate outage grace periods from permanent discontinuation tokens.

The piracy concern is real: anything that unlocks a client can eventually become a target for extraction or replay. But “harder to pirate” is not the same as “must fail when our server fails.” A narrowly scoped, version-bound offline credential seems like a reasonable threat-model tradeoff. I’d oppose a mandate that dictates one implementation.

The policy distinction matters here. EU digital-content rules provide remedies when software stops working, but they do not specifically require a permanent local activation token. In the US, ownership of a copy and licensing rights are already treated differently. That leaves a plausible consumer-protection argument, but not an established general requirement.

I’d start with procurement and customer pressure rather than legislation. Make offline continuity a buying criterion, especially for tools embedded in a long-lived workflow. Vendors may resist a promise they must support forever, but a clearly bounded final build is easier to price and explain than “you own it until our backend changes.”