Perpetual licence vs subscription: the five-year cost
Software is sold two ways. You buy a perpetual licence once and use that version indefinitely, or you subscribe and keep access for as long as you keep paying. Most vendors have spent the last decade moving from the first model to the second, which is why a renewal quote can arrive for a tool your organisation believes it already owns.
The comparison people make is between the purchase price and the annual subscription, and it almost always flatters the perpetual licence, because the purchase price is not what a perpetual licence costs. What follows is the arithmetic over five years, the four things that move the answer more than the headline prices do, and which model suits which kind of tool.
What each model actually buys
A perpetual licence is a right to use a specific version of the software for as long as you like. It does not expire. What it usually does not include is anything that happens after the purchase: new versions, security patches and vendor support normally sit behind a separate annual maintenance fee, quoted as a percentage of the licence value.
A subscription, sometimes sold as a term licence, grants access only while the payments continue. Updates and support are bundled into the price, and when the term ends so does the access. The whole cost is recurring, and the agreement carries a renewal date and, in most cases, a notice period.
The difference that matters for tracking is not ownership, it is where the deadline sits. A subscription has one obvious deadline every term. A perpetual licence has no deadline on the licence at all and a real one on the maintenance agreement beside it, and that second half is the one most registers never record.
The five-year arithmetic
Take a tool quoted both ways. The perpetual licence is 2,400 pounds per seat, with annual maintenance at 20 percent of the licence value from the second year. The subscription is 55 pounds per seat per month, billed annually. Ten seats, five years, and no price rises on either side:
- Perpetual: 24,000 pounds for the licences in year one, then 4,800 pounds a year of maintenance across years two to five. Five-year total 43,200 pounds.
- Subscription: 6,600 pounds a year, every year. Five-year total 33,000 pounds.
- Perpetual with the maintenance line struck: 24,000 pounds and nothing after it, which is the cheapest column on the page and buys four years of an unpatched, unsupported version.
That is the shape of it at a realistic maintenance rate. Perpetual only looks cheaper if you strike the maintenance, and striking it means running software that stops receiving security fixes. Change the inputs and the crossover moves, but the structure does not: once maintenance runs at roughly a fifth of the licence value a year, a one-off purchase has quietly become a recurring cost with a smaller number on it.
What the comparison usually misses
Four things move the answer further than the two headline prices do.
- Version lock. A perpetual licence buys the version you bought. Four years on, file formats, operating systems and integrations have moved, and catching up is a fresh purchase rather than an update.
- Uplift. A subscription renews at whatever the vendor asks unless the contract caps it. An uncapped renewal uplift compounds, so a five-year total built on today's price is a floor rather than a forecast.
- Seat flexibility. Perpetual seats are bought and owned, so a team that shrinks keeps paying for nothing it can hand back. A subscription can usually be reduced at renewal, which is worth real money on an estate that changes shape.
- Cash against commitment. A perpetual licence is one large outlay in one year. A five-year subscription is a smaller annual figure and a much larger obligation, and the obligation is what belongs on a contract liability view.
None of the four is an argument for one model over the other. They are the reason the comparison has to run over the life of the tool rather than the first invoice, which is the same discipline a multi-year contract needs, and the reason total cost of ownership is the figure worth writing down.
Which model suits which tool
Two questions settle it for most tools, and neither of them is about price.
- Will this be doing the same job in five years? Stable, self-contained software that does not need to talk to anything else ages well on a perpetual licence. Anything depending on integrations, file-format compatibility or a vendor's own cloud does not.
- Is the headcount using it stable? A fixed team on a settled tool is the case perpetual licensing was designed for. A team that grows, shrinks or reorganises pays twice for that pattern under a model that cannot give seats back.
Most estates end up mixed, which is the awkward part. One department can be holding a perpetual design suite with maintenance, forty SaaS subscriptions, a usage-based API bill and two open-source tools with paid support, and those four things behave completely differently at renewal time. The fields a register needs have to cover all of them or the mixed estate is what falls through.
Tracking both in one register
StackTrackr records licence type on every tool, so subscription, perpetual, usage-based and open-source agreements sit in one software register rather than in separate lists that disagree with each other. Licence type is set when you add the tool and shown on that tool's own page; it is not a column on the register today, so it is a fact recorded against each record rather than something you can yet sort the whole estate by.
The perpetual case is handled explicitly rather than fudged. A record with no renewal or expiry date is given its own lifecycle state, labelled No renewal date, instead of being counted as healthy, because nothing in the alerting engine can ever fire on it. That keeps the licence visible as what it is: an asset you hold with no deadline attached.
The maintenance or support agreement is the half that carries dates, so give it its own record with a renewal date and notice period. From those two fields the cancellation deadline is calculated and reminders reach the named owner before it, exactly as they would for a subscription. Put the purchase order and the support terms in the vault against the same tool and the whole arrangement survives the person who bought it.
On the money side, an outright purchase is deliberately never annualised. A perpetual licence has no annual run-rate, so the Expenditure report keeps one-off outlay as its own total beside the recurring one rather than folding a capital purchase into a yearly figure it does not have, and the Liability report totals what you are still contractually committed to rather than what you paid last month. Both reports are part of the paid plans and of the 14-day trial.
If the vocabulary in a licensing quote is the obstacle, the glossary covers it in plain English. Otherwise the free Starter plan tracks ten tools for one person, which is enough to put your perpetual licences and their maintenance agreements side by side and see which of the two has a date attached: see the plans or create an account.