Methodology
Compare the data stores a platform reaches, where it processes data, the work it requires and the evidence for its price.
The current preview
The directory contains 50 platform records. Public sources have been reviewed for 50 profiles. Every listed profile links its public sources and review date. Counts describe this directory, not measured market coverage.
Source review checks a claim against published vendor material. It does not establish performance in a customer deployment. Profiles link claims to the relevant documentation or product page. Confirm capabilities, permissions, costs and limits in an evaluation.
Evidence required for publication
Factual claims must trace to dated public sources a buyer can check, including product documentation, release notes, marketplace listings, procurement records, regulatory filings and attributable practitioner reports. A source must support the specific claim. Unsupported claims are omitted.
A reported figure needs a checkable source and an inline qualification. A label such as “reported” does not replace evidence. “Not published” means the information was not established in the sources reviewed. It does not mean the vendor cannot provide it.
Reading coverage
Full means documented, first-class support within the stated scope. Partial means limited support with a material caveat, including incomplete store coverage or a custom integration. None requires evidence of no support. Unconfirmed means the reviewed sources do not establish coverage. It is not a negative capability claim.
Broad environment marks are a starting point. Snowflake and Databricks share the Warehouses column, while profiles can distinguish individual stores. Environment coverage does not establish that every listed capability works in every store.
Capabilities are recorded at platform level. Selecting DLP and AWS finds platforms with documented DLP and recorded AWS coverage. It does not establish that their DLP controls operate on AWS data. Check the specific store, action, deployment and licensed product together before treating a platform as a candidate.
Where researched, Store and control evidence describes a named workflow with sources for its action and limitations. These entries are authored from the documents, not generated from coverage marks. A missing entry means this workflow has not been established in our research. Use the coverage evaluation guide to turn a claim into a test.
Azure infrastructure is outside these six columns. Microsoft 365 support does not imply Azure coverage. On-prem refers to file shares, not every locally hosted database or endpoint. Google Workspace support belongs under SaaS, not Google Cloud. A vendor hosting its own service on AWS does not establish AWS data coverage. Database-focused products can be relevant even when these six columns leave much of their scope unconfirmed.
How selection works
Select environment headings to highlight those columns and bring relevant coverage first. Every environment remains visible. Selection alone keeps every platform in the comparison, including those with gaps. “Full coverage only” hides platforms without a full mark in every selected environment. Capability and search filters also narrow the list.
Records are alphabetical by default. With environments selected, platforms with full coverage across the selection come first, followed by platforms with partial coverage and no gaps, then those with a gap or unconfirmed coverage in any selected environment. Within each group, more full marks come first, with alphabetical ties. This ordering describes recorded coverage and is not a quality rating or purchase recommendation.
Expand a row to read its summary, notes on selected environments and an evaluation question. The full profile includes architecture, operational work, pricing and source records where available.
Dates and ownership
Profiles carry an update date. An update date alone is not verification. The acquisition tracker records ownership changes for review alongside the platform.
Paid visibility
Payment cannot change inclusion, ordering, coverage marks or critical findings. Any sponsored placement must be labeled. The sponsorship policy sets out the boundary.