Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of Holistics and OpenMetadata — release velocity, themes, recent moves, and the top alternatives to consider.
Holistics is adding governance to the AI layer it spent the summer building.
Holistics ships small, frequent notes - often one or two sentences - covering three strands at once: AI features in Explore and Chat, as-code control over presentation through AML, and workspace hygiene like file history and dark mode. The August entries turn to the AI layer's edges rather than its capabilities, with an AI user attribute for restricting what the assistant can reach. Several entries are barely a line long, so scope frequently has to be read from the headline.
A second 2.0 release candidate lands while 1.13 keeps absorbing governance and CVE fixes.
OpenMetadata is running two lines at once. The 2.0.0 major is on its second release candidate, both explicitly marked dev and test only with no stated changes. The 1.13 line continues as the shipping product: 1.13.3 fixed Snowflake foreign-key collisions across tables sharing a constraint name, unstuck data contracts left at Running, and repaired poisoned governance trigger filters, while 1.12.14 and 1.13.2 were dominated by dependency CVE patching across MLflow, PyArrow, log4j and the ingestion images.
Holistics ships small, frequent notes - often one or two sentences - covering three strands at once: AI features in Explore and Chat, as-code control over presentation through AML, and workspace hygiene like file history and dark mode. The August entries turn to the AI layer's edges rather than its capabilities, with an AI user attribute for restricting what the assistant can reach. Several entries are barely a line long, so scope frequently has to be read from the headline.
The AI work has moved through a recognizable sequence: capability first with chart suggestions, then observability with AI Chat Insights for admins, and now access control with an AI-specific user attribute. Alongside it, Holistics keeps pulling presentation into AML - custom charts, theme palettes, currency formats - so the things analysts used to click are versioned as code. File history is the join between the two threads, giving every dashboard, model, and dataset its own restorable timeline.
With capability, visibility, and access control now in place for the AI layer, the next step is likely audit or policy depth - logging what the assistant answered against which data - rather than new AI surfaces.
OpenMetadata is running two lines at once. The 2.0.0 major is on its second release candidate, both explicitly marked dev and test only with no stated changes. The 1.13 line continues as the shipping product: 1.13.3 fixed Snowflake foreign-key collisions across tables sharing a constraint name, unstuck data contracts left at Running, and repaired poisoned governance trigger filters, while 1.12.14 and 1.13.2 were dominated by dependency CVE patching across MLflow, PyArrow, log4j and the ingestion images.
The direction was set by 1.13.0, which made MCP a first-class service category and added an RDF knowledge graph; everything since has been consolidation around those two surfaces plus a heavy security-patch cadence. With 2.0 now on its second RC and carrying no published notes, the interesting question — what actually changes in the major — remains unanswered by the entries themselves.
Expect further 2.0 release candidates before a final, and continued 1.13.x maintenance releases weighted toward governance-workflow fixes and dependency patching until the major stabilizes.
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 Holistics or OpenMetadata.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all Holistics alternatives → · See all OpenMetadata alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Holistics and OpenMetadata 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. Holistics and OpenMetadata 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 Holistics alternatives in Analytics are ranked by recent ship velocity. Browse the "Holistics alternatives" section above for the current picks, or visit /alternatives/holistics for the full list with editorial commentary on each.
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.