RStudio
RStudio's first October patch is a branch merge, extending a long run of release-train upkeep.
A side-by-side editorial comparison of OpenReplay and Tautulli — release velocity, themes, recent moves, and the top alternatives to consider.
OpenReplay moves its Go backend to pgx v5 and patches vulnerable deps across 1.25–1.27.
On Oct 28 OpenReplay pushed backup tags on the 1.25, 1.26 and 1.27 lines that migrate the Go backend to pgx v5, bump vulnerable Go dependencies such as golang.org/x/net, and then fix a replay query that broke under the migration by casting issue_types to text. The previous days moved the assist and sourcemap-reader services to Node 26 LTS on the same lines and on 1.22.
Tautulli's release notes read like a security advisory with a changelog attached.
Every release in the past year has closed CVEs — path traversal, XSS, open redirect, SQL injection, remote code execution in notification text and in newsletter templates. v2.18.1 keeps the run going with an API fix for guest users being able to retrieve another user's history, and adds an X-Frame-Options header to the config file. The feature work sits in v2.18.0 two days earlier: Dolby Atmos on activity cards and in notification parameters, history pagination moved from Python into SQL, and a push relay for Remote App notifications.
On Oct 28 OpenReplay pushed backup tags on the 1.25, 1.26 and 1.27 lines that migrate the Go backend to pgx v5, bump vulnerable Go dependencies such as golang.org/x/net, and then fix a replay query that broke under the migration by casting issue_types to text. The previous days moved the assist and sourcemap-reader services to Node 26 LTS on the same lines and on 1.22.
The release feed is all maintenance: dependency and runtime upgrades backported to several self-hosted lines at once, published as timestamped backup tags without feature notes. The quick follow-up fix shows the pgx migration is touching real query paths.
Expect more backup tags as the pgx v5 change reaches 1.22 and any further query fixes land; nothing in the entries points to a feature release.
Every release in the past year has closed CVEs — path traversal, XSS, open redirect, SQL injection, remote code execution in notification text and in newsletter templates. v2.18.1 keeps the run going with an API fix for guest users being able to retrieve another user's history, and adds an X-Frame-Options header to the config file. The feature work sits in v2.18.0 two days earlier: Dolby Atmos on activity cards and in notification parameters, history pagination moved from Python into SQL, and a push relay for Remote App notifications.
Two threads run in parallel. Researchers have not stopped finding issues, and the fixes have shifted from patching individual endpoints toward changing defaults — validated paths, an authenticated image proxy, and now a framing header written into the config. The other thread is the notification stack moving off OneSignal, which the project has dated for deprecation on 1 October 2026, onto a relay it controls.
Expect another 2.18.x patch closing whatever the current round of reports surfaces, and the OneSignal migration to be pushed harder in release notes as the October deadline approaches.
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 OpenReplay or Tautulli.
RStudio's first October patch is a branch merge, extending a long run of release-train upkeep.
Basedash automations can now attach scheduled CSV exports to Slack and email.
OpenPanel tags three more note-free builds in one evening, reaching 3.16.4.
Fulcrum turns on Insights, its AI assistant for field data, for every customer.
Holistics lets admins put a key dashboard on everyone's Home page.
OpenHouse locks down its column-defaults capability flag as default values near completion.
See all OpenReplay alternatives → · See all Tautulli alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenReplay and Tautulli 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. OpenReplay and Tautulli 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 OpenReplay alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenReplay alternatives" section above for the current picks, or visit /alternatives/openreplay for the full list with editorial commentary on each.
Top Tautulli alternatives in Analytics are ranked by recent ship velocity. Browse the "Tautulli alternatives" section above for the current picks, or visit /alternatives/tautulli for the full list with editorial commentary on each.