Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Looker and Parseable — release velocity, themes, recent moves, and the top alternatives to consider.
Looker's release feed is mostly page furniture; the shipping behind it is thin.
Most of what reaches this feed is scraped structure from Google Cloud's release-notes index — section headings, edition filters, a navigation dump — rather than releases. The real changes in the window are narrow: mobile alerts now arrive as push notifications on the Looker app, and a Table Visualization Improvements preview landed disabled by default. One note flags behaviour changes due with Looker 26.8 in May 2026.
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.
Most of what reaches this feed is scraped structure from Google Cloud's release-notes index — section headings, edition filters, a navigation dump — rather than releases. The real changes in the window are narrow: mobile alerts now arrive as push notifications on the Looker app, and a Table Visualization Improvements preview landed disabled by default. One note flags behaviour changes due with Looker 26.8 in May 2026.
Looker's development is being folded into the Google Cloud release cadence, where each Looker change is a line item in a much larger catalogue. What is visible is upkeep of the existing surface — mobile parity, visualization polish, preview flags — not new capability. On the evidence in this feed the product is in a low-signal, maintenance phase.
The 26.8 release is the next entry with actual content behind it; the pattern here suggests it arrives as a set of preview-flagged behaviour changes rather than a headline feature.
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 Looker 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 Looker 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 0.0), 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 0.0), 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 Looker alternatives in Analytics are ranked by recent ship velocity. Browse the "Looker alternatives" section above for the current picks, or visit /alternatives/looker 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.