RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of fasster and OpenObserve — release velocity, themes, recent moves, and the top alternatives to consider.
fasster arrives as a fable-compatible state space model for switching seasonality.
fasster implements FASSTER, a state space model with a switching component in the measurement equation, aimed at series carrying several seasonal patterns and abrupt structural change. Version 0.2.0 is the first substantive release: a formula interface with trend(), season(), fourier(), ARMA() and xreg() plus the %S% switching and %?% conditional operators, and the full fable method set. Parameters come from a filtering-and-smoothing heuristic rather than full optimisation.
After the 836-commit 0.92 release, OpenObserve is quietly moving its MCP server into the free tier
OpenObserve is in the settle-down phase after v0.92.0, the largest release the project has shipped, which added synthetic monitoring, Workflows v1, an expanded AI observability set, per-group and per-series alerting with SLOs, and moved Vortex and the MCP server into open source. The v0.92.1 patch that followed is small but pointed: the MCP Server setup page now renders on the OSS build, and an alerts bug where the HAVING clause was typed from the column rather than the aggregate is fixed. The 0.91 line continues to receive backported fixes in parallel.
fasster implements FASSTER, a state space model with a switching component in the measurement equation, aimed at series carrying several seasonal patterns and abrupt structural change. Version 0.2.0 is the first substantive release: a formula interface with trend(), season(), fourier(), ARMA() and xreg() plus the %S% switching and %?% conditional operators, and the full fable method set. Parameters come from a filtering-and-smoothing heuristic rather than full optimisation.
The package sat at a 2018 development version for over seven years, so the news is that it exists as a usable model at all. Implementing the whole fable contract — forecast(), refit(), stream(), interpolate(), components() — means it slots into an existing forecasting workflow instead of asking for its own. The heuristic estimator is the open question these entries leave unanswered.
The obvious next step is supplementing the heuristic parameter estimates with proper optimisation, though the two entries here give no direct signal on timing.
OpenObserve is in the settle-down phase after v0.92.0, the largest release the project has shipped, which added synthetic monitoring, Workflows v1, an expanded AI observability set, per-group and per-series alerting with SLOs, and moved Vortex and the MCP server into open source. The v0.92.1 patch that followed is small but pointed: the MCP Server setup page now renders on the OSS build, and an alerts bug where the HAVING clause was typed from the column rather than the aggregate is fixed. The 0.91 line continues to receive backported fixes in parallel.
The MCP thread is the one to watch. Open-sourcing the server in 0.92.0 was the architectural move; serving its setup page on the OSS build a week later is what makes it reachable without an enterprise license. That points at agent clients as a first-class consumption path rather than an enterprise upsell, which is a different distribution bet than the synthetic-monitoring and Workflows surfaces that headlined the same release. Everything else in this window is stabilization — RC backports, memtable rotation, RBAC migrations — consistent with a project digesting a release that spanned two repositories and a large-scale crate reorganization.
Expect a run of 0.92.x patches concentrated on the three new surfaces, since synthetic monitoring, Workflows and eval scheduling all shipped at once with limited production exposure. The alerts fix suggests the aggregation path is a likely source of further corrections.
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 fasster or OpenObserve.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all fasster 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 fasster alternatives in Analytics are ranked by recent ship velocity. Browse the "fasster alternatives" section above for the current picks, or visit /alternatives/fasster 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.