Subscriptions are everywhere. The software industry has spent the last decade framing recurring billing as the default and perpetual licensing as a relic. But perpetual licensing has its place in the market, and it’s an important one.
What is a perpetual license?
A perpetual license is a specific type of software license where the vendor provides a one-time purchase price that grants the buyer the right to use a specific version of the software indefinitely with no renewal fees, no expiration dates, and no dependency on vendor servers. For buyers operating in offline, regulated, or security-sensitive environments, it’s often the only model that actually works. For software vendors, perpetual licensing is a commercially viable, and often strategically essential, option to offer.
This article covers how perpetual licensing works, what it includes, why it continues to make sense for specific buyers, and what vendors should weigh when deciding whether to offer it.
Key Takeaways
The mechanics of a perpetual license are deliberately simple. Unlike subscriptions with auto-renewals, usage tiers, and conditional access, the perpetual license model follows a clear, one-time transactional sequence:
License keys and activation codes are the primary ways that perpetual licenses are enforced. Modern implementations often support offline activation as well, where the customer generates a request file, sends it through a secure out-of-band channel, and receives a license file in return with no live connection required at any point. This is the standard workflow for air-gapped deployments in industries such as defense, healthcare, and industrial environments.
Optional maintenance and support (M&S) agreements (also sometimes called Software Assurance agreements) are annual add-ons that provide access to new versions, patches, and vendor support. They’re not part of the perpetual license itself, so if a customer stops renewing M&S, the software keeps working; only access to new releases and vendor support ends.
Rights typically granted: installation and use on a defined number of devices or seats; indefinite use of the licensed version; backup copies as permitted by the license terms.
Rights typically not granted: redistribution or resale, reverse engineering or decompilation, and sublicensing to third parties.
Licensing structures vary by deployment model. Single-user (node-locked) licenses tie the software to a specific machine or user identity. Multi-user or floating licenses allow a defined number of concurrent users across a network. Enterprise perpetual agreements often cover site-wide deployment under volume pricing.
Perpetual licensing isn't a relic; it's the right model for a significant portion of the software market, and the industries that rely on it are not going away.
Before SaaS, software was purchased with the viewpoint that it was a capital expenditure with a predictable useful life, no vendor server dependency, and no monthly line item subject to cancellation or price hikes. That model suited IT departments because once software was deployed, in theory, its behavior wouldn’t change unless there was a deliberate decision to change it.
That logic hasn't disappeared. Manufacturing floors run engineering software on isolated operational technology (OT) networks. Government agencies manage classified systems that can’t connect to external servers by policy or law. Healthcare environments face governance requirements that restrict cloud-based data processing. Field operations in utilities, mining, and energy work where connectivity is absent.
For these organizations, perpetual licensing is a technical and regulatory requirement. SaaS licensing models typically require a live connection for authentication; when that connection is unavailable by design, the license fails. Perpetual licenses with offline activation eliminate this failure mode entirely.
The theoretical permanence of a perpetual license is only as reliable as the vendor honoring it. A growing number of vendors have moved to discontinue, deactivate, or effectively undermine perpetual licenses in ways that have drawn significant backlash, and in some cases, legal action.
Nitro PDF is a recent example. In May 2025, Nitro notified holders of perpetual licenses predating version 13 that their licenses would be deactivated unless they migrated to a subscription plan. The reason for this was security compliance, and that older versions couldn’t be patched appropriately. However, users pointed out that the perpetual license agreement means that Nitro doesn’t have the right to deactivate their licenses, even for “security compliance” reasons. Regardless, Nitro did indeed deactivate older licenses, leading to complaints across the internet.
Here’s another example. At the enterprise level, the Broadcom acquisition of VMware produced one of the highest-profile perpetual license disputes in recent memory. Broadcom announced it would end perpetual licensing and move all customers to subscription-only bundles. AT&T—holding existing VMware perpetual licenses—refused, sought a mandatory injunction, and argued that without continued support it couldn’t guarantee stable services for customers, including critical national infrastructure. The parties settled, but the point remains that perpetual licenses may not always be forever, particularly when a vendor changes hands.
Another high-profile example is Unity. The game development community saw a parallel rupture in 2023, when Unity announced a retroactive runtime fee, which is a per-install charge on games already built and shipped under the existing license terms. The Unity pricing controversy triggered a wave of migrations to Godot and Unreal. Unity cancelled the fee in 2024, but trust in the platform suffered lasting damage.
These cases carry clear lessons for both audiences. Buyers should be careful to verify whether the agreement explicitly prohibits deactivation of the core perpetual right, confirm what happens to support terms if the vendor is acquired, and check for a clear order-of-precedence clause across contract documents. On the other hand, vendors should understand that unilaterally deactivating perpetual licenses—or forcing migrations under threat of deactivation—produces controversy, regulatory attention, and accelerated churn that typically outweighs any short-term revenue gain.
See our article on perpetual license vs.subscription license for a full comparison. Key differences at a glance:
Perpetual License | Subscription License | |
Cost structure | One-time upfront fee | Recurring monthly or annual |
Software access | Indefinite, unconditional | Conditional on active payment |
Version updates | Version-locked; upgrades cost extra | Always current version included |
Offline use | Supported; minimal connectivity needed | Often requires periodic validation |
Risk if vendor closes | Low—software continues to function | High—access may be lost |
A perpetual license grants rights to a specific release, not the product in general. Buy a perpetual license for version 2019 of an application and you own the right to run version 2019 indefinitely, not any newer release. Buyers used to subscriptions, where the latest version is always included, frequently forget this fact about perpetual licensing.
Of course, the implication is that the licensed version may eventually become incompatible with newer operating systems, hardware, or file formats. However, many organizations treat version stability as a feature: a fixed version delivers consistent behavior, no forced UI changes, and no surprise feature deprecations. In regulated environments where software changes require formal revalidation, version lock is often seen as a compliance requirement, not a drawback.
M&Ss are optional annual add-ons. With active agreement, customers receive new major releases, making the combination behave somewhat like a subscription in terms of version currency, but with a key safety net: if the M&S lapses, customers retain full use of the last version they were running.
For customers who let M&S lapse and later want to upgrade, the typical paths are a one-time upgrade fee or a new perpetual license for the current version.
Feature | Perpetual License Only | Perpetual + Active M&S |
Use of licensed version | Yes, indefinitely | Yes, indefinitely |
Access to new versions | No | Yes, during M&S term |
Vendor support & patches | No | Yes, during M&S term |
Access if M&S lapses | N/A | Retain last version used |
Upgrade path | Upgrade fee or new perpetual license | Included during active M&S |
The cost/benefit ratio looks different depending on which side of the transaction you're on.
Advantages:
Disadvantages:
For independent software vendors ISVs, offering perpetual licensing is as much a market access decision as a pricing one. Customers in defense, healthcare, government, and industrial sectors often can’t purchase software requiring ongoing cloud-based validation. Subscription-only vendors may be locked out of these markets entirely.
Advantages:
Disadvantages:
As the Broadcom/VMware and Nitro PDF cases illustrate, unilaterally deactivating perpetual licenses or forcing migrations under threat of deactivation can produce legal disputes, regulatory complaints, and lasting reputational damage. Honoring existing perpetual commitments, with transparent communication and an adequate migration runway is both an ethical and commercial obligation.
The question isn't whether perpetual licensing is better than subscription, it's whether your target customers can use a subscription model at all.
Perpetual licensing tends to be the right offer when your target customers operate air-gapped or on-premises infrastructure; when connectivity is unreliable, restricted, or prohibited; when your software solves a stable problem that doesn't require continuous updates; when competitors have moved subscription-only and buyer frustration creates a differentiation opportunity; or when your sales cycles involve capital budgets and formal procurement processes.
Perpetual licensing doesn't have to be either/or. Common hybrid approaches include:
Implementing these licensing models requires infrastructure that handles activation without a live connection, tracks entitlements across deployment types, and manages upgrade paths across versions. LicenseSpring's perpetual licensing platform supports perpetual, subscription, metered, and floating models from a single API, with full offline and air-gapped activation support.
Perpetual licensing is the right fit when software is mission-critical, used long-term, and deployed in environments where connectivity or data sovereignty constraints apply. Strong candidates include organizations running air-gapped or offline environments, businesses with stable workflows that don't require cutting-edge features, teams with capital budget cycles better suited to one-time purchases, and industries with strict data sovereignty requirements, including government, defense, and healthcare.
A subscription-based license tends to be a better fit for teams needing continuous feature access, organizations operating fully in cloud-native environments, and buyers who prefer lower upfront costs with the flexibility to cancel.
Perpetual options persist across several software categories despite the subscription shift: CAD and engineering tools, enterprise security and IT management software, specialty vertical software in construction, legal, and medical imaging, and open-source projects with commercial perpetual license options. Buyers should verify offline behavior before purchasing—some products marketed as one-time purchases still require periodic online validation.
No. A perpetual license grants rights to the specific version purchased. Updates and major upgrades often require an active M&S agreement or a separate upgrade purchase, but the software continues to work regardless.
The software keeps working exactly as it did before the lapse. What ends is access to new releases, vendor support, and any patches issued after the lapse date.
Yes, and a hybrid model is often the most commercially effective approach. It expands your addressable market, serves different buyer profiles, and lets you capture both upfront and recurring revenue. The key requirement is licensing infrastructure that can manage both models and their respective activation and entitlement scenarios.
Through offline activation. The customer generates a license request file on their isolated system, transmits it through a secure out-of-band channel, and receives a license file that activates the software without any internet connection. LicenseSpring handles this workflow natively, including entitlement tracking and version management for offline deployments.
That depends on the vendor's license agreement, but technically it's achievable. Most vendors allow reassignment within the same organization, such as when an employee leaves or a device is replaced, through a deactivation and reactivation workflow. Transfers to a different legal entity (e.g., following an acquisition) typically require vendor approval and a formal license reassignment process.
The terms are often used interchangeably, but there's a subtle distinction. A perpetual license grants ongoing use rights in exchange for a one-time fee, sometimes with optional M&S. A paid-up license specifically signals that no further payments are due under any circumstances (including maintenance) and is more common in OEM or embedded software contexts where the agreement is fully settled at signing.
Some software is licensed to a specific machine or hardware fingerprint, meaning it activates against a device ID, CPU signature, or dongle. If the hardware changes, the license must be transferred or reissued. Node-locked perpetual licenses follow this model. Floating or site licenses are less hardware-dependent and easier to manage across hardware refresh cycles, though both still require activation infrastructure that can handle reactivation requests cleanly.
The most common starting point is the "years-to-parity" method (the number of years a customer would need to subscribe to a service before the total cost equals the upfront price of a perpetual license plus maintenance fees). The first step is to set the perpetual price at roughly three to four times the annual subscription price, so a customer who would otherwise renew indefinitely breaks even within that window. Beyond that baseline, factor in your customer's buying context—enterprise buyers with procurement cycles and capital budgets often tolerate higher upfront figures than SMB buyers do—and your own revenue targets. M&S should typically be priced at 18–22% of the perpetual license fee annually, which keeps renewal attractive without cannibalizing the upfront deal. If you're offering both models, the perpetual price should feel like a meaningful but finite premium over the subscription, not an arbitrary multiple, otherwise buyers default to subscription simply because the math might be a bit murky.
The perpetual license model has outlasted subscription-era pressure not because the market is slow to change, but because a substantial portion of software buyers genuinely cannot operate on subscription terms. Air-gapped infrastructure, capital budget cycles, data sovereignty requirements, and the need for version stability are not going away, and neither is the demand for perpetual licensing.
For buyers, the decision comes down to usage duration, connectivity, and budget structure. For vendors, it comes down to market access: offering perpetual licensing, either by itself or alongside subscription or metered options, opens doors in regulated and security-sensitive markets that subscription-only competitors cannot enter. The infrastructure to do this well is what LicenseSpring's perpetual licensing support within our comprehensive licensing platform is built to provide.
Manage your software’s entire licensing lifecycle effortlessly with LicenseSpring. Get started today.
8 Minutes
Guide
