Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Matomo and Parseable — release velocity, themes, recent moves, and the top alternatives to consider.
Matomo bets on AI-traffic measurement as its differentiator while modernizing the UI for upmarket buyers.
Matomo is on a near-monthly minor-release cadence threading three concurrent themes: AI-traffic instrumentation, visual modernization (dark mode and theme refresh in 5.10.0), and privacy-compliance shortcuts aimed at EU operators. Patch releases land between minors with security and archiving fixes, and the team still ships occasional Matomo 4 backports for legacy customers.
Parseable's 3.0 turns a log store into a logs, metrics, traces and APM console.
Parseable has spent the 2.9 line hardening a multi-tenant ingestion engine — API keys, OAuth sync, tenant quotas, credential masking, and a run of injection and path-traversal fixes contributed from outside the core team. Version 3.0.0 collects that groundwork into a platform release: PromQL-based alerts, dashboard templates, dataset tagging, trace and ingestion endpoints, service maps and APM in the Prism UI, and a custom-provider option in the LLM flow. The ingestion story also changed shape, with fluent-bit dropped from the scripts in favour of an OpenTelemetry collector.
Matomo is on a near-monthly minor-release cadence threading three concurrent themes: AI-traffic instrumentation, visual modernization (dark mode and theme refresh in 5.10.0), and privacy-compliance shortcuts aimed at EU operators. Patch releases land between minors with security and archiving fixes, and the team still ships occasional Matomo 4 backports for legacy customers.
After introducing AI-agent detection in 5.6.0 and dedicated AI chatbot traffic reports in 5.8.0, Matomo is positioning itself as the analytics tool that explicitly accounts for non-human traffic — a stance neither GA4 nor Plausible has taken head-on. The 5.9.0 one-click CNIL preset and 5.10.0 UI overhaul read as moves to broaden the buyer pool beyond technical self-hosters.
Expect deeper AI-traffic features — segmentation, attribution, and per-agent breakdowns — plus the one-click compliance pattern extended from CNIL to other regulators.
Parseable has spent the 2.9 line hardening a multi-tenant ingestion engine — API keys, OAuth sync, tenant quotas, credential masking, and a run of injection and path-traversal fixes contributed from outside the core team. Version 3.0.0 collects that groundwork into a platform release: PromQL-based alerts, dashboard templates, dataset tagging, trace and ingestion endpoints, service maps and APM in the Prism UI, and a custom-provider option in the LLM flow. The ingestion story also changed shape, with fluent-bit dropped from the scripts in favour of an OpenTelemetry collector.
The direction is consolidation: rather than being the cheap object-store log backend that something else queries, Parseable is absorbing the query, alerting and dashboard layers that normally sit above it. PromQL support is the clearest tell — it targets teams whose alert rules are already written for a Prometheus-shaped world. Performance work is tracking that ambition too, with zstd manifests, configurable concurrent object-store calls and faster field-stats sitting alongside the feature list.
The next releases most likely fill in the metrics side to match the logs side — deeper PromQL coverage and more dashboard and alert templates — while the 3.0 UI migrations settle through point releases. Whether the LLM provider hook grows into anything beyond configuration isn't visible from these entries.
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 Matomo or Parseable.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all Matomo alternatives → · See all Parseable alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Parseable is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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. Parseable is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 Matomo alternatives in Analytics are ranked by recent ship velocity. Browse the "Matomo alternatives" section above for the current picks, or visit /alternatives/matomo for the full list with editorial commentary on each.
Top Parseable alternatives in Analytics are ranked by recent ship velocity. Browse the "Parseable alternatives" section above for the current picks, or visit /alternatives/parseable for the full list with editorial commentary on each.