Where product data comes from

What a listing contains

• Documented features. The product's capabilities, recorded per Category with consistent names, so the same feature means the same thing on every listing that carries it. These are the unit of evidence the matching system scores.
• Compliance certifications and integrations. Recorded the same way, and usable as requirements in your brief.
• Deployment and implementation context. How the product runs and what adopting it involves. This is context for reading a listing, not evidence: it never affects a ranking.

What counts as evidence

A field is recorded because vendor-published material supports it: product documentation, technical pages, and published certifications, not slogans or a diagram's ambitions. If the documentation does not support a claim, the listing does not carry it. The same bias to precision governs how products are classified.

How the catalog stays current

We revisit each Category regularly, refreshing listings and picking up new products and capabilities as markets move. Every change to the catalog is reviewed by a Security Stack researcher before it goes live.

Corrections follow the same standard as everything else: we verify them against the documentation and update the listing.