Tinylytics
Tinylytics adds account-wide IP ignores and monitoring-only sites
A side-by-side editorial comparison of OpenCTI and OpenReplay — release velocity, themes, recent moves, and the top alternatives to consider.
OpenCTI accepts Filigran licenses and closes a draft-access hole in its TAXII routes.
OpenCTI keeps a release every few days. 7.261103.0 lets a Filigran license be installed as the platform license, validates draft context on TAXII and HTTP routes so users can't reach drafts they shouldn't, and harmonizes redirects across authentication endpoints. It also fixes a regression that left the Prometheus exporter listening only on localhost. The prior release added Hub import to custom views and configuration-bundle export.
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.
OpenCTI keeps a release every few days. 7.261103.0 lets a Filigran license be installed as the platform license, validates draft context on TAXII and HTTP routes so users can't reach drafts they shouldn't, and harmonizes redirects across authentication endpoints. It also fixes a regression that left the Prometheus exporter listening only on localhost. The prior release added Hub import to custom views and configuration-bundle export.
After two weeks spent on dashboards and the knowledge graph, attention is turning to platform administration: configuration presets, Hub-distributed views, connector forms and ingestion health, which is being built behind a feature flag. Custom fields now sit on the Enterprise side of the line, so new data-model flexibility is being used as a paid differentiator. Access-control fixes keep appearing, which suggests organization segregation is still being hardened.
Expect ingestion health to leave its feature flag in a coming weekly, with email notifications already in place. The entries do not indicate when a new LTS line will be cut.
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 OpenCTI 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.
OpenHouse records why table maintenance fails and adds timezone-aware retention.
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 OpenCTI 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. OpenCTI 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. OpenCTI 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 OpenCTI alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenCTI alternatives" section above for the current picks, or visit /alternatives/opencti 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.