Perpetual licence or subscription: which makes sense for HR software
The models differ in more than price: what you own, who carries the risk, what happens if the vendor changes. Including when subscriptions win.
Almost all business software was sold under perpetual licences until about 2012. You paid once, you owned that version forever, and you paid again when you wanted the next one. Then subscriptions became the default, for reasons that had at least as much to do with vendor revenue predictability as with customer benefit.
Both models still exist. For HR software in particular, the choice is worth making deliberately rather than by default.
What each one actually is
A subscription grants the right to use software while you keep paying. Stop paying and access ends. The vendor hosts it, updates it continuously, and typically prices per user per month.
A perpetual licence grants the right to use a version of the software permanently, for a one-time fee. It usually comes with a period of updates and support included — commonly twelve months — after which continued updates require an optional renewal. Crucially, declining that renewal does not switch anything off. You stay on the version you have.
The distinction people miss: a perpetual licence with an optional maintenance renewal is not a subscription in disguise. The test is what happens when you stop paying. If the software stops, it is a subscription. If the software carries on and only the updates stop, it is a licence.
If you are evaluating something described as perpetual, that is the question to ask, in writing.
Where the real differences are
Price gets the attention, but three other differences matter more over a five-year horizon.
Who carries the continuity risk
With a subscription, the vendor's continued existence is load-bearing. If they are acquired, pivot, discontinue your tier, or fold, you have a migration on their timetable rather than yours. This is not hypothetical — the HR software category has consolidated heavily, and products get sunset after acquisitions routinely.
With a perpetual licence, particularly one that includes source code, the vendor disappearing is an inconvenience rather than an emergency. The software keeps running because it is running on your infrastructure. You lose future updates, not the system.
For payroll specifically this asymmetry is significant. Payroll cannot have an outage in November because a vendor made a decision in October.
Who controls the upgrade
Subscriptions update continuously, whether or not the timing suits you. Mostly this is a benefit — security patches arrive without effort. Occasionally it is not: an interface change lands the week you are onboarding twenty people, or a workflow you depend on is redesigned.
With a licence you choose. That is genuinely better, and it is also genuinely more work, because nothing happens unless someone does it. An installation left unpatched for two years is a security problem you own.
How the cost behaves as you grow
Per-seat subscriptions scale with headcount. A perpetual licence priced per organization does not. Whether that matters depends entirely on whether you expect to grow — which makes it a question about your business rather than about software.
The honest case for subscriptions
Perpetual licensing is not universally better, and it is worth being direct about when it is not.
You are small and staying small. Under about fifteen people, per-seat pricing is cheap and the operational overhead of self-hosting is disproportionate to the saving.
You have no technical capacity. Perpetual licences for self-hosted software require someone to run the server. If that person does not exist and cannot be hired or contracted, this is settled — take the subscription.
Cash flow beats total cost. A one-time fee is a larger cheque today. For an organization where that is genuinely difficult, spreading the cost is worth paying more overall for. That is a legitimate financial decision, not a mistake.
You are still exploring. If you do not yet know whether this class of tool fits how you work, renting is the cheap way to find out.
The product genuinely changes. Where a vendor ships meaningful new capability every year, the subscription buys something real. Apply some scepticism here — the core of HR software has been stable for a long time — but it is sometimes true.
The honest case for perpetual
You expect to grow. The whole argument is the shape of the cost curve.
You have data obligations. Perpetual licences for self-hosted software put the data on your infrastructure, which is often the only clean answer to a residency requirement.
Your processes are unusual. With source code, an approval chain that matches your organization is development work rather than a feature request that gets declined.
You want to remove a dependency. Some organizations simply prefer not to have a third party in the critical path of paying their staff. That is a defensible position on its own.
You are budgeting capital rather than operating expense. A licence can be treated as an asset in a way a subscription cannot. Ask your accountant how that lands in your jurisdiction; it sometimes changes the answer.
What to ask before signing either
For a subscription:
- What is the renewal price, and what is the cap on annual increases?
- Which tier contains every module we need, and what does that cost per user?
- Are there minimum seat counts?
- What exactly can we export, in what format, and how long is it available after we leave?
For a perpetual licence:
- Does the software keep working if we never renew? Get this in writing.
- What does the licence cover — one installation, one legal entity, non-production environments?
- Is source code included, and what may we do with it?
- What does renewal cost, and what happens if we let it lapse and rejoin later?
- What are the actual system requirements, and who installs it?
The decision in one line
If your organization will be roughly the same size in five years and has nobody to run a server, subscribe.
If you expect to be meaningfully larger, or you have data obligations, or you would rather not have a third party between you and your payroll — buy the licence, and make sure "perpetual" means what you think it means.
Ace HR is a perpetual licence: one payment, unlimited employees, full source code, and an optional annual renewal for updates. Not renewing changes nothing about your installation. The licence agreement says so in plain language.