Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of MVMR and OpenObserve — release velocity, themes, recent moves, and the top alternatives to consider.
MVMR spent 2026 discovering its own estimators had been returning the wrong numbers
MVMR implements multivariable Mendelian randomization — conditional instrument strength, pleiotropy tests and heterogeneity-robust effect estimation from GWAS summary data. The package has been releasing steadily through 2026, and the substantive releases are all corrections rather than features. Two core routines were found to be computing the wrong quantity outright: qhet_mvmr() built weights from the minimised objective value instead of the minimiser, and strhet_mvmr() never minimised the Q-statistic at all.
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.
MVMR implements multivariable Mendelian randomization — conditional instrument strength, pleiotropy tests and heterogeneity-robust effect estimation from GWAS summary data. The package has been releasing steadily through 2026, and the substantive releases are all corrections rather than features. Two core routines were found to be computing the wrong quantity outright: qhet_mvmr() built weights from the minimised objective value instead of the minimiser, and strhet_mvmr() never minimised the Q-statistic at all.
This is a sustained audit, not a maintenance drift. Each release since February has fixed a specific analytical defect — omitted intercepts in the exposure-on-genotype regressions, a division by zero when a gencov list held exactly two variants, covariance matrices computed wrongly for matrix inputs, a spurious covariance warning — and several explicitly warn that reported values will differ from previous versions. The strhet_mvmr() rewrite to iteratively reweighted least squares also removes a combinatorial grid that could exhaust memory past three exposures, so the function is now usable as well as correct.
The corrections have been walking through the package function by function, and the ones with published fixes so far are the heterogeneity and covariance routines; the remaining untouched estimators are the natural next stop if the audit continues at this pace.
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.
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 MVMR or OpenObserve.
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 MVMR alternatives → · See all OpenObserve alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top MVMR alternatives in Analytics are ranked by recent ship velocity. Browse the "MVMR alternatives" section above for the current picks, or visit /alternatives/mvmr for the full list with editorial commentary on each.
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.