ERP Migration & SelectionFree calculatorPDF, Excel, Word exportEurope

ERP Named vs Concurrent User Licence Calculator

Many European mid-market ERPs offer named-user, limited-user and concurrent-user models, and the right mix depends on how people actually work. This calculator shows which model costs less for your population and where the break-even sits.

Your numbers

users
users

Shop floor entry, approvals, time booking, read-only.

EUR
EUR
sessions

Peak simultaneous sessions from login logs.

EUR

Your results

Annual saving with concurrent
-EUR 69,900
Negative means the named model is cheaper.
Break-even concurrent sessions
32.5962
Concurrent pool size at which both models cost the same.
Named licence cost per year
EUR 101,700
Concurrent licence cost per year
EUR 171,600
Total named users
105
Peak concurrency ratio
52.4%

Licence metrics differ by vendor and contract. Confirm definitions of full, limited and concurrent users with your vendor before using the result in negotiation.

Save results:

Concurrent vs named annual cost by session count

Sweeps Concurrent licences needed from 0 to 120, holding your other inputs fixed.

Optional licence usage analysis

We can outline how to extract peak session and role usage from your ERP logs to size licences with evidence. No obligation.

Optional. The tool and every export work without this. No spam.

How to use it

Count named users by role: full users who work in the ERP all day, and limited users who book time, approve or view. Pull peak simultaneous sessions from login logs for several weeks, ideally including month-end. Enter vendor prices and compare. The chart shows how the concurrent cost climbs as the pool grows against the flat named cost.

  • Use login logs, not headcount
  • Include month-end and quarter-end peaks
  • Separate shop floor terminals from office users
  • Check whether API or integration users consume licences

The break-even logic

The named model costs (full times full price plus limited times limited price) times 12. The concurrent model costs sessions times concurrent price times 12. Break-even sessions equal named annual cost divided by 12 times concurrent price. If your measured peak is below the break-even value, concurrent licensing is cheaper. A peak ratio above roughly half of total users often favours named licences.

Reading the result

A positive saving means the concurrent pool wins on cost. But factor in risk: if the pool is exhausted, users are locked out at the worst time, such as an inventory count or month-end close. Add a buffer of 10 to 20 percent to the measured peak and test again. Also consider that limited licences often cover most occasional users cheaply.

Common mistakes

People size concurrency from average, not peak, usage and forget scheduled jobs or integrations that hold sessions open. Another error is assuming every vendor treats shop floor terminals the same way. Some count a shared kiosk as one named user per person, others as one device.

Frequently Asked Questions

Which model is usually cheaper?

It depends on usage patterns. Large populations with low simultaneous use often favour concurrent licences, while small teams who are all logged in all day favour named licences.

How do I find peak concurrent sessions?

Export login and logout timestamps from the ERP or application server for at least a month, and count the maximum overlapping sessions in any five-minute window.

Do API users consume licences?

Often yes, or they need a separate integration licence. Check your contract, because several scheduled interfaces can quietly hold sessions.

Can I mix models?

Some vendors allow it. Enter the named part in the named fields and the rest as concurrent, then add the two costs yourself.

If you want licence consumption analysed from your real ERP audit logs, Netray can build a read-only report of peak sessions by role.