Methodology

How we research and compare

Comparisons are built from what vendors document: product docs, OpenTelemetry guides, region and data-residency pages, trust centres and public licences. We do not run trials and present them as tests.

The capability matrix

Each product gets one row. For every row we record:

• which signals it covers (APM, tracing, metrics, logs, error tracking, real user monitoring, session replay, infrastructure, profiling, synthetic checks), as yes, partial/add-on, no, or not stated;
• how it ingests OpenTelemetry data and what instrumentation it expects;
• whether it runs as SaaS, self-hosted or in your cloud account, and its open-source licence if any;
• data regions, whether a free tier or trial exists, how it bills (per host, per GB, per user and so on) and the compliance reports it publicly states;
• the source pages and the date we verified them.

We show how products bill, never their prices. A missing fact is marked "not stated", never assumed.

Decisions

Comparisons end in "choose this if" conditions tied to a stack, a constraint or a team, not a winner. When a claim depends on performance or experience, we attribute it to the named source that reported it.

Updates

We update a page when its sources change: a new capability, a change to OpenTelemetry support, a new region, a licence or pricing-model change, a certification, a rename, acquisition or shutdown. A check that finds no change does not change the public date.

Tools

Research and drafting are tool-assisted. The editorial desk checks every published claim against its source before publication.

Money

We may earn affiliate commissions and accept clearly labelled sponsorship. Nobody can buy a "choose this" verdict, a ranking, a matrix value or the removal of a competitor. See the disclosure policy and partner policy.

Corrections

If a capability is wrong or out of date, use the contact form with the page and the documentation link. Corrections are free.