Capability is not what is for sale.
Every capability works with no licence on up to 25 hosts per scan. What a licence buys is scale, automation, more than one person, integration with what you already run, and the submission formats an authority will accept. Each tier below is a job someone is doing, not a feature list.
- All ten offline scanner modules
- Scoring across every framework
- Challenge Coins and selective disclosure
- The web dashboard and the REST API
- PDF, HTML, CBOM and executive briefings
- Everything above, at estate scale
- Drift between scans, so posture becomes a trend rather than a snapshot
- Accounts and roles, for more than one person
- Scheduled scans and webhooks
- SIEM forwarding and Prometheus metrics
- Cloud scanning across AWS, with CSP auto-detect
- Vendor supply-chain analysis
- Everything in Enterprise
- ATO package assembly
- eMASS integration
What is a host?
One machine or endpoint you point a scan at. It is not an asset. A single TLS host commonly yields sixty or more assets, because every cipher suite and certificate is one, so twenty-five hosts is a real handful of systems rather than a token.
What is the catch on the free tier?
The scope, and only the scope. Nothing is watermarked, nothing expires, no feature is disabled to make a point, and no capability is held back to force a conversation. Twenty-five hosts is enough to watch the whole evidence chain work end to end and too few to be a deliverable, which is the property we wanted.
Can I pilot at a realistic size before deciding?
Run pqcat license trial. Fourteen days, 250 hosts, with the Enterprise feature set, so you can answer the questions the free bound cannot: does it hold up across the estate, does it run on a schedule, does it land in our SIEM. It is hardware-bound, signed with ML-DSA-65 and validated entirely offline, so it works on a disconnected machine.
When it lapses the product keeps working, back at twenty-five hosts. It does not lock you out of evidence you already produced.
Do you see my scan data?
No. There is no account, no telemetry, no licence server and no callback. The binary talks to the hosts you point it at and nothing else. Licence validation is a signature check against a key compiled into the binary, which is why it works air-gapped.
Why is cloud scanning the one capability behind a licence?
Because it reads a whole cloud account rather than a host you named, so it is not bounded by a host count in any meaningful way. It is also a compile-time build: a licence alone cannot switch it on, you need the Cloud build. Those are two separate things and it is worth keeping them straight.
Do you publish prices?
Not yet. Tiers and what they include are above, and they are enforced in the product rather than described in a table. For a number, mail labs@soqu.org and say roughly how many hosts and how many people.
What happens to licences issued under the old edition names?
They keep working. A licence carries its own entitlement list, so a change to what new licences grant does not alter what an issued one allows.
Start with the free tier rather than a conversation. Download it, point it at something you own, and read the report. If it is not useful at twenty-five hosts it will not become useful at five hundred, and you should find that out without talking to anyone.