Is pricing based on machines or data volume?

Both models exist — your choice. Option 1: per-machine licensing (per agent), for maximum budget predictability regardless of data volume. Option 2: pricing on volume actually stored, **after deduplication** — identical blocks are billed once, which favors fleets of many small servers. In both cases, consumption is visible continuously in the console, and backups never stop on quota overrun: you are alerted and the excess is billed per your contract.

Both models exist — you choose.

Option 1: per-machine licensing. A licence per protected server, whatever its volume. Maximum budget predictability: the cost follows your fleet’s size, not your data growth.

Option 2: volume-based pricing. You pay for data actually stored, measured after deduplication — identical blocks across snapshots and servers are billed once. This typically favors fleets of many small servers, or environments with highly redundant data.

Two principles apply in every case: your consumption is visible continuously in the console, and backups never stop when a quota is exceeded — you are alerted and the excess is billed per your contract terms, because an interrupted backup is a risk no one should carry.