Pick the track by where your system is. The price comes from the current table β measured, not estimated.
Start by where your system is:
Models 1 (code on your machine) and 2 (on the server where it runs). In both, the price comes from the measured size: you run a read-only meter, it writes a manifesto.json, and the quote comes out on that number.
Haven't measured yet? Measure first β a few minutes, and the guide has screenshots.
Only the manifesto β it carries file names and counts, never your code's content. Open and check it first; it is readable JSON.
No code is measured here β the price is from the table. Pick the model, the level and (for the whole server) the number of domains, and the value shows right away.
3 β Host: your application on a server that is not yours. Only it is in scope β the host stays out and is not mentioned in the report. Each domain is a full audit: price per domain.
4 β MultiHost: the server is yours and goes in whole β system, firewall, remote access, updates and every service, plus the applications. Host work is done once: price by domain band.
5 β Share: the public service seen from outside. Fixed, recurring price.
The value appears on screen, from the current table β with the link to place the order. The same link goes to your e-mail; the order is only created when you confirm.
If you already got your quote number, the order page is where you confirm and pay.