A perpetual license is bought once and used indefinitely; a subscription license is paid monthly or annually and ends when payments stop.
A perpetual license is bought once, for a one-off fee, and grants the right to use that version of the software indefinitely; a subscription license is paid monthly or annually and grants the right to use the software only while payments continue. The difference sounds like a payment plan, but it changes who owns what, how upgrades arrive, how the cost hits the budget - and what you need to record about each model in an asset register.
How perpetual licenses work
You pay once and keep the right to run the licensed version for as long as you like. Support, security patches, and new versions are usually a separate annual maintenance contract; let it lapse and the software keeps running, it just stops evolving. Perpetual licensing was the default for decades and survives today in desktop tools, engineering software, and on-premise server products. Finance typically treats the purchase as a capital cost: an asset bought once, then written down over its useful life.
How subscription licenses work
You rent access. Updates are included, the version is always current, and the cost is a predictable operating expense - but the meter never stops, and cancelling means losing access rather than keeping an old version. Subscriptions are usually scoped per user or per device, so the bill rises and falls with headcount, which is convenient for growing teams and easy to ignore for shrinking ones.
Cost and ownership over time
The honest comparison is total cost over the period you will actually use the tool. A perpetual license front-loads the spend and rewards keeping software for years; a subscription spreads it and rewards flexibility. Where the crossover lands depends on the vendor’s pricing, but the pattern is consistent: long-lived, stable tools favour perpetual, while fast-moving needs, fluctuating headcount, and cloud-delivered products favour subscription.
Ownership differs too. A perpetual license is something you hold - it can outlast the vendor relationship and, subject to its terms, sometimes be transferred. A subscription is a service contract: when it ends, nothing is left behind except the data you remembered to export.
Which model fits when
- Perpetual suits software that changes slowly, machines that outlive upgrade cycles (a workshop PC driving one instrument), and environments where recurring billing is impractical.
- Subscription suits collaboration and cloud tools, anything needing constant security updates, and teams whose size changes faster than a procurement cycle.
- Most estates mix both - which is precisely why they need tracking in one place rather than two habits.
Tracking both models in one register
Each model fails differently when untracked: perpetual licenses are forgotten because nothing recurs to remind anyone they exist, while subscriptions auto-renew because nobody owns the date. Record every license with its model, seat count, cost, renewal or maintenance date, and the agreement attached, alongside the hardware it runs on through the IT asset lifecycle. In AMPthilly, licenses live in the same register as physical equipment, so renewal dates, owners, and purchase documents stay on the record rather than in someone’s inbox.
Related terms
- Per-User (Seat) Licensing - the scope model most subscriptions are priced on
- IT Asset Lifecycle - where license purchases, renewals, and retirements belong
- Hardware Refresh Cycle - device replacements that trigger license reinstalls and transfers
- Golden Image - the standard build that bakes licensed software into every deployment
- Asset Agent - software that inventories what is actually installed on each device