TestingBudget

Licensing & Infra

Licences needed

How many licensed units the organisation needs across every application in the workspace.

Unit
count
Where you enter it
Licensing & Infra tab, per vendor — once for the whole workspace.

What it means

The number of seats, runners or units to buy — a vendor-level figure, because a licence is bought once for the organisation, not once per application. Multiplied by the cost per licence it gives the yearly licence cost, which the model counts once and allocates to applications by their case counts.

Getting the unit right matters: named-user, concurrent-user and parallel-runner licensing produce very different counts for the same team.

Why it matters to the cost

Summing licences per application would bill the same seats four times over for a four-application estate — a mistake that flatters whichever tool has the cheapest licence. Entering the true organisational count once, and letting the model apportion it, is what keeps the per-app views honest.

Typical values

Five to twenty for a single team; the number of parallel runners rather than people for execution-based licensing.

Typical values describe a category of tool — AI-native, codeless, script-based, homegrown, manual — never a named product. Why we do not price named products.

Try it with your numbers

Licences needed is a row in the calculator. Change it and every total on the page moves with it — free, in your browser, nothing to install.

See how licences needed impacts the calculation of test automation costs

Last reviewed 2026-09-15. All terms.