Tinylytics
Tinylytics adds account-wide IP ignores and monitoring-only sites
A side-by-side editorial comparison of OpenHouse and OpenReplay — release velocity, themes, recent moves, and the top alternatives to consider.
OpenHouse records why table maintenance fails and adds timezone-aware retention.
OpenHouse landed Views M1 on October 30, with create, replace, list and delete over its commit-only engine behind database-scoped gating. On November 3 it shipped two operational changes: the Optimizer now stores a failure reason for each failed maintenance operation, and retention policies on string-date columns can use a timezone instead of UTC.
OpenReplay lets self-hosters block the hosts a recorded session can make its asset cacher fetch.
OpenReplay's feed is still backend maintenance across the 1.25 to 1.27 lines. On Nov 3 it added ASSETS_DENY_HOSTS so the asset cacher refuses chosen hosts before any DNS lookup, after a probe session crash-looped a pod. The same day brought a fix for EE 1.26 images that crashed on start and a product-analytics user fix backported to three lines.
OpenHouse landed Views M1 on October 30, with create, replace, list and delete over its commit-only engine behind database-scoped gating. On November 3 it shipped two operational changes: the Optimizer now stores a failure reason for each failed maintenance operation, and retention policies on string-date columns can use a timezone instead of UTC.
Feature series run in parallel: views, column defaults, and now table maintenance operations. The failure-reason work is framed as groundwork for dashboards and transient-versus-permanent classification. Retention timezone support is split across a backend PR and a Spark 3.5 SQL PR, the same stacked pattern used elsewhere.
Expect the Spark SQL half of retention timezones (#735) and further Optimizer failure-visibility work, likely failure classification.
OpenReplay's feed is still backend maintenance across the 1.25 to 1.27 lines. On Nov 3 it added ASSETS_DENY_HOSTS so the asset cacher refuses chosen hosts before any DNS lookup, after a probe session crash-looped a pod. The same day brought a fix for EE 1.26 images that crashed on start and a product-analytics user fix backported to three lines.
The work is hardening the self-hosted stack: safer asset fetching, startup crash fixes and the same patch landing on several release lines. The deny list moving into a shared package suggests asset handling is being made consistent across versions. No new user-facing features have appeared in recent entries.
Expect ASSETS_DENY_HOSTS to reach the 1.25 line next, following the usual backport pattern.
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 OpenHouse or OpenReplay.
Tinylytics adds account-wide IP ignores and monitoring-only sites
DebugBear is growing from performance testing into uptime, browser support and ad-impact data.
OpenCTI accepts Filigran licenses and closes a draft-access hole in its TAXII routes.
InfluxDB keeps patching its 3.11 and 3.12 lines, now with a catalog repair tool.
Basedash adds verified dashboards so teams know which numbers to trust.
OpenPanel tags six supporter builds in two days, from 3.21 to 3.23.2, with no notes.
See all OpenHouse alternatives → · See all OpenReplay alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenHouse and OpenReplay 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. OpenHouse and OpenReplay 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 OpenHouse alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenHouse alternatives" section above for the current picks, or visit /alternatives/openhouse for the full list with editorial commentary on each.
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.