What our labels mean

A directory entry may combine vendor-published facts with editorial organization and analysis. A dated source check means we reviewed the cited primary material; it does not imply that every product was installed on every operating system or measured in a controlled benchmark.

When we have direct product-use evidence, we describe the specific workflow tested. When we do not, we attribute the claim to the vendor and avoid presenting it as an independent performance result.

Research process

Start with primary sources

We check official pricing pages, product documentation, release notes, security pages, and public repositories before relying on secondary summaries.

Record the scope and date

Product details change quickly. Articles use publication and review dates, and time-sensitive claims should identify the plan, region, or product version they describe.

Separate facts from evaluation

Published prices and supported platforms are treated as sourced facts. Recommendations are editorial judgments and should explain the workflow or constraint behind them.

Label hands-on evidence honestly

We mention direct use only when a tool or workflow was actually exercised. A documentation review is not presented as a benchmark or a multi-platform lab test.

Correct material changes

When a pricing, availability, or capability claim becomes inaccurate, we update the article and its review date. Readers can report errors through our corrections process.

What we compare

The criteria depend on the product and available evidence. Common checks include:

Pricing, limits, and plan eligibility

Editor, language, and platform support

Deployment and data-handling options

Repository context and workflow scope

Administrative and security controls

Documented integrations and dependencies

Sources, freshness, and limitations

We prefer vendor-owned documentation and link to it when a claim could affect a purchase or deployment decision. Prices may exclude tax, vary by billing cycle, or change after publication. Product names and model availability can also change without notice, so readers should confirm critical details with the vendor.

We do not claim a fixed six-month retest schedule for every page. Updates are prioritized by material product changes, reader reports, search demand, and the age of important claims.

Editorial Research Methodology