Verification

How we verify each listing

Every listing is built from the same twelve structured facts, sourced from the vendor's own pages and reviewed by a person before a verification date is written.

Browse the directory Read the editorial standards

Twelve structured facts per listing

A listing is not a description written by the vendor. It is a record of twelve facts in the same format for every tool, so two listings can be compared without reading two different brochures.

Categories: The directory categories the tool is listed under.
Official website: The canonical product page on the vendor's own domain.
Pricing model: Free, freemium, subscription, usage-based, enterprise or open source.
Pricing details: Pricing in the vendor's own wording. Where pricing is not published we record that, instead of estimating.
Free tier: Whether a free plan or free tier is documented publicly.
Platforms: Web, cloud, API, on-premise or marketplace deployment.
Region support: The regions the vendor states it serves.
Compliance: Only frameworks the vendor documents publicly. If none are published, the field reads Not stated.
API available: Whether a documented API exists.
Use cases: What the tool is used for, taken from the vendor's own description.
Sources: The official pages each fact was taken from, linked so the claim can be checked.
Last verified: The date a reviewer last checked the record against those sources.

Where the facts come from

Every number, price, compliance framework and region must appear on a vendor page that was opened during verification.

Each fact is linked in Sources to the official page it was taken from, so the claim can be checked without a sales call.
Vendor emails, marketing decks and third-party summaries are not accepted as the source for a recorded fact.
When a field is not published anywhere official, it is left empty rather than filled with an estimate.

What a reviewer checks by hand

Three fields always receive a manual check before the verification date is written:

Pricing: the model, the details and whether a free tier exists.
Compliance: the framework name against its public documentation.
Region support: the regions the vendor states it serves.

The same pass confirms that the sources load, that they support the claim, and that they sit on the vendor's own domain. A listing is published only after that pass.

Freshness and the 180-day rule

A record has a shelf life of 180 days. Once its verification date is more than 180 days old, the listing enters the re-verification queue and is checked again against the vendor's pages.

The date published on every listing tells you how old the facts are, so an older record is visibly older rather than silently stale. It does not promise that nothing changed after it was checked; it records exactly what was checked, and when.

How procurement teams use the record

Filter to the platforms and regions an evaluation requires, then compare the same fields side by side.
Open the sources behind a compliance claim before it goes into an RFP, a bid response or a vendor questionnaire.
Check the verification date against the procurement calendar, and ask the vendor about anything published after it.
Treat an empty field as unknown, not as a negative answer. Not stated is not the same as not supported.