OpenHouse
OpenHouse is hardening the seams where table policies and jobs quietly fail.
A side-by-side editorial comparison of Fathom Analytics and shiny — release velocity, themes, recent moves, and the top alternatives to consider.
Fathom rebuilds its query engine and bolts on Search Console, reaching for GA4's lunch.
Fathom shipped a complete analytics-engine rebuild in March 2026, paired with secondary dimensions, faster queries, and more accurate time-on-page measurement. The product is closing the feature gap with mainstream analytics tools while keeping its cookie-free, privacy-first stance. Recent additions — Google Search Console integration, entry/exit pages, dashboard ZIP exports, and a fresh layer of bot detection — directly target reasons users still keep GA4 open in another tab.
Shiny made reactive apps observable, then gave them a way to tear themselves down
Version 1.12.0 added OpenTelemetry support through the {otel} package, emitting spans for session start and end, reactive updates and individual reactive expressions, with collection depth set by an option or environment variable. The releases since have refined it - scoped collection controls in 1.12.1, cleaner stack traces in 1.13.0 - while 1.14.0 turned to lifecycle, adding session$destroy() on module proxies and a non-blocking startApp() for driving apps programmatically.
Fathom shipped a complete analytics-engine rebuild in March 2026, paired with secondary dimensions, faster queries, and more accurate time-on-page measurement. The product is closing the feature gap with mainstream analytics tools while keeping its cookie-free, privacy-first stance. Recent additions — Google Search Console integration, entry/exit pages, dashboard ZIP exports, and a fresh layer of bot detection — directly target reasons users still keep GA4 open in another tab.
The roadmap is clearly aimed at making Fathom a viable single-pane replacement for Google Analytics rather than a privacy-first complement to it. Expect continued investment in detection accuracy, reporting depth (custom exports, secondary dimensions), and Google-side integrations. The new analytics engine is foundational — it is what makes the next layer of features possible.
Next likely moves are deeper UTM and campaign analytics, an experimentation or goals-funnel surface, and tighter agency tooling that builds on self-serve site transfer and shared-dashboard exports.
Version 1.12.0 added OpenTelemetry support through the {otel} package, emitting spans for session start and end, reactive updates and individual reactive expressions, with collection depth set by an option or environment variable. The releases since have refined it - scoped collection controls in 1.12.1, cleaner stack traces in 1.13.0 - while 1.14.0 turned to lifecycle, adding session$destroy() on module proxies and a non-blocking startApp() for driving apps programmatically.
The framework is addressing the two things that make Shiny apps hard to run in production: you could not see inside the reactive graph, and you could not reliably dispose of parts of it. Tracing answers the first; scoped destruction of module session proxies answers the second. Both are aimed at long-lived, dynamically composed apps rather than at the single-file demo.
Expect the OpenTelemetry attribute names to settle once the deprecated spellings are dropped, and more of the reactive lifecycle to gain explicit teardown hooks now that session$destroy() has established the pattern. Editor integration is a likely area for follow-up after the Ark breakpoint support.
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 Fathom Analytics or shiny.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
statsmodels ships only what the ecosystem breaks — six releases, no new statistics.
StatsBase.jl is in caretaker mode — correctness fixes in, dependency bumps out.
Iris ships steadily on a two-a-year cadence, but its feed publishes only pointers.
ggplot2 swapped its object system out from under a decade of downstream code
See all Fathom Analytics alternatives → · See all shiny alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fathom Analytics is currently shipping more aggressively (velocity 1.3 vs 0.0), with 0 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. Fathom Analytics is currently shipping more aggressively (velocity 1.3 vs 0.0), with 0 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 Fathom Analytics alternatives in Analytics are ranked by recent ship velocity. Browse the "Fathom Analytics alternatives" section above for the current picks, or visit /alternatives/fathom-analytics for the full list with editorial commentary on each.
Top shiny alternatives in Analytics are ranked by recent ship velocity. Browse the "shiny alternatives" section above for the current picks, or visit /alternatives/r-shiny for the full list with editorial commentary on each.