Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
Comparison · Analytics
hubData vs OpenObserve
A side-by-side editorial comparison of hubData and OpenObserve — release velocity, themes, recent moves, and the top alternatives to consider.
hubData vs OpenObserve: at a glance
What is hubData?
The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
What is OpenObserve?
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.
hubData vs OpenObserve: editorial side-by-side
hubData
0.0ANALYTICS
The Arrow data layer for forecast hubs, spending its releases on cloud and materialisation bugs.
◆ Current state
hubData is the access layer for hubverse forecasting hubs, connecting to local and cloud-stored model output through Arrow and handing back lazy connections or materialised tibbles. Its releases divide sharply between schema and utility additions in the 1.x line and, more recently, a run of defect fixes in the cloud and Arrow integration. Two of those fixes involved data being silently wrong rather than an error being raised.
◆ Where it's heading
The package has largely finished adding surface and is now paying down the cost of sitting on top of Arrow and S3: ALTREP-backed columns escaping into user sessions, cloud hubs whose declared format differs from what is actually written, and metadata arrays parsing inconsistently. Each fix narrows the gap between what the storage layer does and what an R user expects. The performance-motivated default flip in 2.0.0 points the same way, prioritising large cloud hubs over conservative local behaviour.
◆ Prediction
Expect continued fixes at the Arrow and cloud boundary, particularly where declared hub configuration and actual stored format disagree, which has now produced defects twice.
OpenObserve
6.3ANALYTICS
After its largest release, OpenObserve is patching the seams.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to hubData and OpenObserve
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 hubData or OpenObserve.
silx
silx settles into maintenance a release after its PySide6 migration
Plotly
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread
aniread stops asking you to know which tracker wrote the file
Rho
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all hubData alternatives → · See all OpenObserve alternatives →
Recent activity from hubData and OpenObserve
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoOpenObservev0.92.2: compactor delay setting and an MCP base-URI fix
- 5d agoOpenObservev0.92.1 brings the MCP server setup page to the OSS build
- 11d agoOpenObservev0.92.0 adds synthetic monitoring, workflows, and AI observability ⚡
- 12d agoOpenObserveRelease candidate 4 backports fixes before the v0.92.0 GA
- 14d agoOpenObserveRC3 adds agent-level filters and parallel zstd compression
- 20d agoOpenObservev0.91.5 patches an RBAC migration and a layout bug
- 1mo agohubDataCloud hubs declaring CSV no longer return an empty connection
- 3mo agohubDatacollect_hub() returns plain vectors instead of ALTREP views
- 3mo agohubDataArray-valued metadata fields now parse as list columns
- 7mo agohubDatadate_col parameter for oracle output schemas
- 9mo agohubDataconnect_hub() skips file validation by default (breaking)
- 10mo agohubDataArrow schema conversion and validation utilities
Frequently asked questions
What is the difference between hubData and OpenObserve?
They serve adjacent needs but don't currently overlap on shipped themes. OpenObserve is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 hubData better than OpenObserve?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenObserve is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 hubData?
Top hubData alternatives in Analytics are ranked by recent ship velocity. Browse the "hubData alternatives" section above for the current picks, or visit /alternatives/hubdata for the full list with editorial commentary on each.
What are the best alternatives to OpenObserve?
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.