Perpetual License

A perpetual license lets an organization use a piece of software forever, or at least for as long as it chooses, after paying for it once. The license covers the version purchased, and the organization keeps the right to run it even if it stops paying the publisher anything further. Most perpetual licenses are paired with an optional maintenance and support agreement, typically charged annually, that provides upgrades, patches and technical help.

Perpetual licenses were the dominant way to buy business software for decades. Many publishers have since moved to subscriptions, and some no longer sell perpetual licenses at all, but they remain common for on-premises software, specialized applications and organizations that prefer to own their software rights. For IT financial management, perpetual licenses raise distinctive questions about capitalization, maintenance costs and when it makes sense to stop paying for support.

Definition of Perpetual License

A perpetual license is a type of software license with no expiry date. The licensee pays a one-time fee for the right to use a specific version of the software under the license terms, such as a set number of users or processor cores, indefinitely.

Perpetual does not mean unrestricted. The license still limits how the software may be used, and the organization must remain within its entitlement. It also does not automatically include new versions: upgrades usually require active maintenance or a new purchase.

Maintenance and Support

Maintenance agreements, sometimes called software assurance or support and subscription, typically cost 15 to 25 percent of the license price each year. They provide access to new versions, security patches, bug fixes and technical support, which most organizations need for business-critical software.

If maintenance lapses, the organization can keep using the version it has, but loses upgrades and support. Reinstating maintenance later often requires paying back fees for the lapsed period or buying new licenses, so the decision to stop paying should be made deliberately. Some organizations use third-party support providers as an alternative, which can cost less but usually means giving up access to new versions.

Perpetual vs Subscription

A subscription license grants the right to use software only while payments continue, usually with updates and support included. When the subscription ends, the right to use the software ends too.

Perpetual licenses have higher upfront costs but lower ongoing costs, and the organization retains usage rights. Subscriptions spread costs evenly and include updates, but cost more over long periods and create ongoing dependence on the publisher. The comparison is covered under software licensing models.

Importance of Perpetual Licenses in IT Financial Management

Perpetual licenses affect how software costs are recorded, how they are budgeted and how flexible the organization is in the future.

They also represent assets that need to be tracked and managed over long periods.

Many organizations hold perpetual licenses bought years ago that are still in use, often with maintenance contracts that have renewed automatically ever since.

Accounting and Budgeting

Perpetual licenses are usually capitalized as intangible assets and amortized over their expected useful life, often three to five years. Maintenance fees are operating expenses recognized over the maintenance period. This places the purchase in the capital budget and the maintenance in the operating budget, a split described under capex vs opex.

Because the purchase is a large one-time cost, perpetual licenses require capital approval and planning. Maintenance creates a recurring cost that continues for as long as the organization wants support and upgrades, and is often overlooked when comparing options. Over a long period, maintenance can cost more in total than the original license purchase.

Ownership and Flexibility

Owning perpetual rights gives organizations some independence. They can keep running the software if the publisher raises prices, changes terms or discontinues the product, and they can choose when to upgrade.

Perpetual licenses can also become a constraint. Organizations may keep using old versions to avoid upgrade costs, accumulating technical debt and security risk. And as publishers move to subscriptions, they may reduce support for perpetual customers or encourage migration with pricing incentives.