Tinylytics
Tinylytics adds account-wide IP ignores and monitoring-only sites
A side-by-side editorial comparison of ntopng and OpenReplay — release velocity, themes, recent moves, and the top alternatives to consider.
ntopng 7.0 adds an AI traffic analyst, Wazuh integration and BGP in one release.
ntopng 7.0 arrived in September, ten months after 6.6. nAnalyst brings AI chat, policies, dashboards and an agentic loop across multiple LLM providers, with an MCP server included. The release also adds Wazuh XDR/SIEM integration, a Sites hierarchy, BGP/BMP with RPKI validation, a ClickHouse timeseries engine, OpenID Connect SSO, MFA and passkeys, and a new Vue.js frontend replacing legacy pages.
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.
ntopng 7.0 arrived in September, ten months after 6.6. nAnalyst brings AI chat, policies, dashboards and an agentic loop across multiple LLM providers, with an MCP server included. The release also adds Wazuh XDR/SIEM integration, a Sites hierarchy, BGP/BMP with RPKI validation, a ClickHouse timeseries engine, OpenID Connect SSO, MFA and passkeys, and a new Vue.js frontend replacing legacy pages.
Each major has annexed an adjacent category, and 7.0 reaches for three at once: AI-assisted analysis, SIEM-adjacent security and routing visibility. ClickHouse is now the assumed foundation, and nAnalyst requires it. The licensing line is also explicit, with nAnalyst limited to enterprise M and above and the MCP functions split between community and pro.
Point releases should focus on nAnalyst and the new frontend, the two largest and least mature surfaces. The next major, on past spacing, is about a year off and likely extends the same analysis and security surfaces.
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 ntopng 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.
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.
See all ntopng 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. OpenReplay is currently shipping more aggressively (velocity 5.0 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. OpenReplay is currently shipping more aggressively (velocity 5.0 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 ntopng alternatives in Analytics are ranked by recent ship velocity. Browse the "ntopng alternatives" section above for the current picks, or visit /alternatives/ntopng 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.