Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of OpenObserve and vellumplot — release velocity, themes, recent moves, and the top alternatives to consider.
After its largest release, OpenObserve is patching the seams.
v0.92.0 landed on 7 August with 836 commits and three new product surfaces - synthetic monitoring, Workflows v1, and an expanded AI observability set - after a long RC series. The two releases since are small: v0.92.1 fixed alert HAVING clause typing and put the MCP server setup page on the OSS build, and v0.92.2 adds a compactor delay setting and backports an MCP 404 fix for deployments running under a base URI. The 0.91 line is still receiving its own backports.
vellumplot tags its first release with a bet most R grammars don't make: the static figure and the widget are the same object.
A new grammar of graphics built on the vellum vector engine, developing fast — ten releases in roughly three weeks — and now at its first tagged release. The distinguishing architectural claim is that the compiled plot is the scene, so a static export and an interactive widget cannot drift apart, and that it renders without a graphics device because vellum measures text itself. Accessibility is treated as a first-class output rather than an afterthought: tagged PDF with a navigable structure tree and alt text, a plot_lint() check, and colour-vision-deficiency simulation at render time.
v0.92.0 landed on 7 August with 836 commits and three new product surfaces - synthetic monitoring, Workflows v1, and an expanded AI observability set - after a long RC series. The two releases since are small: v0.92.1 fixed alert HAVING clause typing and put the MCP server setup page on the OSS build, and v0.92.2 adds a compactor delay setting and backports an MCP 404 fix for deployments running under a base URI. The 0.91 line is still receiving its own backports.
OpenObserve is trying to become the whole monitoring stack rather than the storage layer under one. Synthetic checks, incident workflows, and SLO measurement each replace a separate tool, and incident ingestion from external alert sources hedges the migration path for teams that cannot switch all at once. The MCP work running alongside - open sourced, then given a setup page in the OSS build, then fixed for base-URI deployments - shows the same data being aimed at agent clients rather than dashboards.
The post-GA patches are still landing on the new surfaces, so expect another 0.92.x before feature work resumes - most likely hardening synthetic monitoring and Workflows, which are the two least-exercised additions.
A new grammar of graphics built on the vellum vector engine, developing fast — ten releases in roughly three weeks — and now at its first tagged release. The distinguishing architectural claim is that the compiled plot is the scene, so a static export and an interactive widget cannot drift apart, and that it renders without a graphics device because vellum measures text itself. Accessibility is treated as a first-class output rather than an afterthought: tagged PDF with a navigable structure tree and alt text, a plot_lint() check, and colour-vision-deficiency simulation at render time.
The release sequence shows a grammar filling in ggplot2-parity features and specialist marks in parallel. Parity work landed as secondary axes, rich legend titles, and Sankey styling; the specialist end added categorical datashading, image marks, flow maps and edge bundling for dense graphs. Version 0.7.0 shows a willingness to break early — vsunburst() was removed outright in favour of one vhierarchy() constructor covering sunburst, icicle, treemap and circlepack — which is the right time to do it and suggests the API is still being consolidated toward fewer, more general constructors.
Expect more consolidation of near-duplicate constructors under type arguments and continued expansion of the declarative interactivity introduced in 0.7.0, now that the first tagged release has fixed a public API surface.
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 OpenObserve or vellumplot.
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 OpenObserve alternatives → · See all vellumplot alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenObserve and vellumplot are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. OpenObserve and vellumplot are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top OpenObserve alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenObserve alternatives" section above for the current picks, or visit /alternatives/openobserve for the full list with editorial commentary on each.
Top vellumplot alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumplot alternatives" section above for the current picks, or visit /alternatives/vellumplot for the full list with editorial commentary on each.