← Back to home
Comparison · Analytics

Evidence vs OpenReplay

A side-by-side editorial comparison of Evidence and OpenReplay — release velocity, themes, recent moves, and the top alternatives to consider.

Evidence vs OpenReplay: at a glance

FeatureEvidenceOpenReplay
SectorAnalyticsAnalytics
Velocity score0.05.0
Sparks · 30d00
Top themesbi-as-code, sql, dependencies, securitysession replay, self-hosted, go, dependency upgrades
Last editorial update10d ago22h ago
WebsiteVisit →Visit →

What is Evidence?

Evidence's last release was a February CVE sweep that also removed Evidence Cloud references.

Every tracked Evidence release is from a single day, February 6, 2026: a coordinated patch across the SDK, preprocessor, universal SQL layer and database connectors to pick up dependency updates for CVEs. The SDK patch also removes references to Evidence Cloud.

Read the full Evidence trajectory →

What is OpenReplay?

OpenReplay moves its Go backend to pgx v5 and patches vulnerable deps across 1.25–1.27.

On Oct 28 OpenReplay pushed backup tags on the 1.25, 1.26 and 1.27 lines that migrate the Go backend to pgx v5, bump vulnerable Go dependencies such as golang.org/x/net, and then fix a replay query that broke under the migration by casting issue_types to text. The previous days moved the assist and sourcemap-reader services to Node 26 LTS on the same lines and on 1.22.

Read the full OpenReplay trajectory →

Evidence vs OpenReplay: editorial side-by-side

E
Evidence
ANALYTICS
0.0

Evidence's last release was a February CVE sweep that also removed Evidence Cloud references.

◆ Current state

Every tracked Evidence release is from a single day, February 6, 2026: a coordinated patch across the SDK, preprocessor, universal SQL layer and database connectors to pick up dependency updates for CVEs. The SDK patch also removes references to Evidence Cloud.

◆ Where it's heading

Nothing has shipped in the eight months since, so the open-source BI-as-code framework looks to be in maintenance mode. Removing Evidence Cloud references suggests the hosted offering has been dropped or separated, though the entries do not say why.

◆ Prediction

It is unclear from the entries whether active development will resume; the next release is more likely another dependency or security patch than new features.

O
OpenReplay
ANALYTICS
5.0

OpenReplay moves its Go backend to pgx v5 and patches vulnerable deps across 1.25–1.27.

◆ Current state

On Oct 28 OpenReplay pushed backup tags on the 1.25, 1.26 and 1.27 lines that migrate the Go backend to pgx v5, bump vulnerable Go dependencies such as golang.org/x/net, and then fix a replay query that broke under the migration by casting issue_types to text. The previous days moved the assist and sourcemap-reader services to Node 26 LTS on the same lines and on 1.22.

◆ Where it's heading

The release feed is all maintenance: dependency and runtime upgrades backported to several self-hosted lines at once, published as timestamped backup tags without feature notes. The quick follow-up fix shows the pgx migration is touching real query paths.

◆ Prediction

Expect more backup tags as the pgx v5 change reaches 1.22 and any further query fixes land; nothing in the entries points to a feature release.

Alternatives to Evidence and OpenReplay

Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Evidence or OpenReplay.

See all Evidence alternatives → · See all OpenReplay alternatives →

Recent activity from Evidence and OpenReplay

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoOpenReplay1.25: replay query fix after pgx v5 migration
  2. 1d agoOpenReplay1.26: replay query fix after pgx v5 migration
  3. 1d agoOpenReplay1.27: replay query fix after pgx v5 migration
  4. 1d agoOpenReplay1.25: pgx v5 migration and Go dependency patches (re-cut)
  5. 1d agoOpenReplay1.25: pgx v5 migration and Go dependency patches
  6. 1d agoOpenReplay1.26: pgx v5 migration and Go dependency patches
  7. 8mo agoEvidenceSQLite connector picks up CVE-patched shared dependency
  8. 8mo agoEvidencePreprocessor package updates to resolve CVEs
  9. 8mo agoEvidenceTrino connector picks up CVE-patched shared dependency
  10. 8mo agoEvidenceSDK patches CVEs and removes Evidence Cloud references
  11. 8mo agoEvidenceRedshift connector picks up CVE-patched dependencies
  12. 8mo agoEvidenceSnowflake connector picks up CVE-patched shared dependency

Frequently asked questions

What is the difference between Evidence and OpenReplay?

They serve adjacent needs but don't currently overlap on shipped themes. OpenReplay is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Evidence better than OpenReplay?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenReplay is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to Evidence?

Top Evidence alternatives in Analytics are ranked by recent ship velocity. Browse the "Evidence alternatives" section above for the current picks, or visit /alternatives/evidence for the full list with editorial commentary on each.

What are the best alternatives to OpenReplay?

Top OpenReplay alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenReplay alternatives" section above for the current picks, or visit /alternatives/openreplay for the full list with editorial commentary on each.