The Two Models, Priced Honestly
The perpetual vs subscription licensing decision starts with an honest accounting of what each model actually costs over time, not what the first invoice shows. A perpetual licence is a one-time fee that grants indefinite usage rights to a specific version. A subscription licence is a recurring fee — annual or multi-year — that bundles the right to use, ongoing updates, and support for as long as you keep paying. The headline contrast is simple; the total cost of ownership is not.
The reason perpetual looks cheaper in year one and rarely is over a decade comes down to maintenance. A perpetual licence almost always carries an annual support contract priced at 20–22% of licence value. Oracle's support runs at 22% and increases 3–8% each year by default; on that trajectory you have effectively re-paid the original licence fee within four to five years, and you keep paying. Version upgrades, where they are even offered, commonly cost 25% or more of the original purchase price. Perpetual ownership is real, but it is ownership of a depreciating, increasingly unsupported asset unless you keep funding it.
Side-by-Side TCO Comparison
The table below models a representative enterprise application with a £200,000 perpetual licence versus an equivalent £70,000-per-year subscription, including support on the perpetual side. The figures are illustrative but reflect the cost structures we see across real engagements.
| Factor | Perpetual + Support | Subscription |
|---|---|---|
| Year 1 cash cost | £200,000 licence + £44,000 support = £244,000 | £70,000 |
| Annual ongoing cost | £44,000 support, rising 3–8%/yr | £70,000, rising at contracted uplift |
| 5-year TCO | ~£440,000 | ~£385,000 |
| 10-year TCO | ~£680,000 | ~£815,000 |
| Updates / new versions | Often extra (~25% of licence) | Included |
| Flexibility to reduce | Low — licence is sunk | High — adjust at renewal |
| Audit / compliance model | Entitlement true-up | Continuous usage metering |
| Balance-sheet treatment | Capital asset, depreciated | Operating expense |
The crossover is not a single date. Subscription is cheaper in the early years and perpetual pulls ahead only if you keep the software unchanged long enough — usually beyond year five to seven — and resist the upgrade and re-platforming pressure that vendors apply precisely to prevent that outcome.
The Five-Year Break-Even — and Why It Misleads
The figure most often quoted is a five-year break-even: after roughly five years of subscription payments, you have paid what a perpetual licence would have cost up front. It is a useful rule of thumb and a dangerous one, because it compares a perpetual licence against subscription as if the perpetual licence had no ongoing cost. Once annual support at 22% is added, the perpetual line is not flat — it climbs, and it climbs faster each year as the maintenance uplift compounds.
The honest version of the question is narrower: will you run this software, broadly unchanged, for long enough to justify owning it? For a compliance-heavy core system — an ERP module, an actuarial engine, a control system on a factory floor — the answer is often yes, and perpetual plus capped support wins. For collaboration tools, security products, or anything that needs continuous feature and patch delivery, the perpetual asset decays and the subscription's bundled updates are worth the premium. This same logic drives the annual vs multi-year SaaS commitment decision and the BYOL vs license-included trade-off in the cloud.
The Hidden Costs Buyers Miss
Two costs distort the comparison and rarely appear in the business case. The first is the disappearing perpetual option itself. Vendors have moved decisively to subscription because recurring revenue is predictable and easier to grow. Autodesk stopped selling perpetual licences in 2017 and later closed its maintenance programme entirely; Adobe withdrew Acrobat 2020 perpetual licences from its volume programmes in July 2024, with end of support in June 2025. When perpetual is removed, the replacement subscription is the only path — and that is exactly when buyers have least leverage, which is why price-lock and exit terms must be negotiated into the first subscription, not the third.
The second is audit exposure, which changes shape rather than disappearing. Subscription and cloud-metered models shift compliance from a one-off entitlement check to continuous usage measurement, so over-deployment is billed automatically and quickly. Perpetual estates are not safe either — Autodesk and Oracle have both raised audit activity specifically against customers who declined to convert to subscription. Whichever model you run, disciplined entitlement tracking is the control that keeps the audit lever out of the vendor's hands. The structural questions here mirror those in our reseller vs direct purchasing analysis, where the contracting path shapes who carries compliance risk.
Which Model to Choose
Choose perpetual when the software is a stable, long-life core system you will run with minimal change for five-plus years; when capital budgeting is preferred to operating expense; and when you can negotiate a hard cap on annual support increases — push for 3% or lower against Oracle's default 3–8%. Choose subscription when headcount and requirements are dynamic, when continuous updates carry real value, when M&A or divestiture is likely, or when the vendor has already withdrawn the perpetual option and the only question left is how to structure the subscription. Most large estates end up hybrid — perpetual for the slow-moving core, subscription for everything that changes — and the discipline is matching each workload to the right model rather than letting the vendor default the whole estate to recurring revenue. For benchmarks on what comparable enterprises actually pay across both models, see our price benchmarking report, the broader Microsoft and Oracle licensing playbooks, and the full pricing and licensing models guide. When a model change is being forced on you mid-contract, request a confidential briefing before you sign.