Dovetail
Dovetail lets admins choose which connectors members can plug into the workspace.
A side-by-side editorial comparison of OpenMetadata and OpenReplay — release velocity, themes, recent moves, and the top alternatives to consider.
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
OpenMetadata is still in 2.0.x maintenance mode, shipping a release every one to two weeks. 2.0.8 on November 13 is the broadest yet: Hex and Sigma ingestion now build data models and column lineage, BigQuery date-sharded tables can be grouped into one logical table, Power BI and Snowflake ingestion stop leaving stale or runaway jobs, and MCP authentication and access controls were tightened. The 2.1.0 line sits at rc2, whose only published change is a tag-resolution fix.
OpenReplay's feed is Helm chart bumps behind its asset-cacher deny list.
OpenReplay's entries since November 4 are automated backup tags on the 1.26 and 1.27 lines that only increment Helm chart versions for chalice, assist-api and assist-stats. The last functional change remains the November 3 ASSETS_DENY_HOSTS option, which lets self-hosters block hosts the asset cacher may fetch, alongside a fix for EE 1.26 images that crashed on start.
OpenMetadata is still in 2.0.x maintenance mode, shipping a release every one to two weeks. 2.0.8 on November 13 is the broadest yet: Hex and Sigma ingestion now build data models and column lineage, BigQuery date-sharded tables can be grouped into one logical table, Power BI and Snowflake ingestion stop leaving stale or runaway jobs, and MCP authentication and access controls were tightened. The 2.1.0 line sits at rc2, whose only published change is a tag-resolution fix.
Each 2.0.x release repairs connectors and lineage that 2.0 left incomplete, and the fixes increasingly touch accuracy (correct table identity, lineage that ends at the right model) rather than crashes. MCP keeps appearing in the security sections, which suggests OpenMetadata expects AI tools to read the catalog and is locking that path down before 2.1.
A 2.1.0 final is the next visible step, since two release candidates are out; the entries do not yet say what features 2.1 adds beyond the fixes backported to 2.0.x.
OpenReplay's entries since November 4 are automated backup tags on the 1.26 and 1.27 lines that only increment Helm chart versions for chalice, assist-api and assist-stats. The last functional change remains the November 3 ASSETS_DENY_HOSTS option, which lets self-hosters block hosts the asset cacher may fetch, alongside a fix for EE 1.26 images that crashed on start.
The project is in a maintenance stretch, backporting fixes across 1.25 to 1.27 and repackaging charts. Nothing in recent entries points to new user-facing features.
Unclear from these entries; more chart-bump backup tags are likely until a 1.27.x release with notes appears.
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 OpenMetadata or OpenReplay.
Dovetail lets admins choose which connectors members can plug into the workspace.
Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.
OpenHouse adds time-zone-aware retention and per-database table caps.
Countly 25.03.59 defaults to Node 26, supports MongoDB 9 and tightens app scoping.
Kubecost cuts three 3.3.2 release candidates in two days, still without notes.
RStudio opens the 2026.11 train with another NOTICE file update.
See all OpenMetadata alternatives → · See all OpenReplay alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenMetadata and OpenReplay are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenMetadata and OpenReplay are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top OpenMetadata alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenMetadata alternatives" section above for the current picks, or visit /alternatives/openmetadata for the full list with editorial commentary on each.
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.