OpenCompare

Methodology / v1.1.0

How the evidence
becomes a benchmark.

A reproducible method for comparing software capabilities from dated public evidence without assigning a generic winner or weighted overall score.

No overall scoreNo paid placementVersioned snapshots

01 / Scope

Selection and exclusion

Included when

  • Include products that address the same primary buyer problem and have enough current public evidence to assess every selected dimension.
  • Define the product set and decision dimensions before interpreting individual findings, then preserve that scope in the published snapshot.
  • Treat audience, use cases and product emphasis as narrative context rather than scored benchmark dimensions.

Excluded when

  • Exclude inventory-only products when their public evidence has not yet been normalized into the current capability contract.
  • Document named exclusions and their reason on the report instead of silently removing products from the evaluated set.
  • Do not infer absent capabilities from missing public documentation; use unknown when evidence is insufficient.

02 / Evidence

Source hierarchy and conflicts

  1. Official product documentation, product pages and integration directories
  2. Official pricing, security and regional-availability documentation
  3. Vendor changelogs and dated first-party customer or implementation material
  4. Independent editorial, community and review-platform evidence when the report explicitly includes sentiment

Prefer the most specific and current first-party source. When credible sources conflict, retain the narrower claim, lower confidence and explain the conflict or limitation.

OpenCompare did not perform hands-on product testing for this benchmark. Findings describe documented public evidence, not laboratory or customer-environment validation.

03 / Normalization

What each status means

supported

Current public evidence directly documents the capability for the reviewed product or service scope.

partial

Public evidence supports part of the capability, but material scope, regional or edition constraints remain.

not supported

Current public evidence explicitly states that the capability is unavailable in the reviewed scope.

unknown

The reviewed public evidence is insufficient to determine support; this does not mean the capability is absent.

Unknown is not absent. Unknown means insufficient public evidence at the observation date. It must never be rendered or interpreted as proof that a product lacks a capability.

04 / Governance

Independence and versions

No paid placement

Coverage, product order, statuses and findings are not paid placements. OpenCompare does not sell placement or a favorable result in this research layer.

No universal winner

The benchmark publishes dimension-level evidence and conditional decision views. It does not calculate a weighted overall score, universal rank or generic winner.

Versioning

Published reports are immutable versioned snapshots. Evidence changes are reviewed through an explicit diff and released as a new semantic version with a public revision note.

05 / Reuse

License and citation

Cite the report title, OpenCompare Research, edition, version, publication date, canonical URL and access date. Cite vendor sources separately for vendor-owned claims.

OpenCompare's original benchmark text and structured observations are offered under CC BY 4.0. Vendor names, marks and source materials remain the property of their respective owners.

Last reviewed
2026-08-07