Tautulli
Plex's analytics companion has spent a year shipping CVE fixes faster than features.
A side-by-side editorial comparison of Fulcrum and Grafana Mimir — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | Grafana Mimir |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | field-data-collection, gis, esri-integration, mobile-apps | prometheus, query-engine, multi-tenancy, cost-attribution |
| Last editorial update | 4d ago | 3h ago |
| Website | — | Visit → |
Fulcrum is retiring Google Maps and betting its field app entirely on Esri.
Fulcrum's field data collection platform is mid-consolidation onto a single mapping engine. The legacy Google Maps engine retires on September 1, 2026, and any organization still defaulting to it on web or mobile will be switched to Esri Maps automatically; Google's satellite, hybrid, and street basemaps survive as options in the Esri layer picker. Everything else this cycle is routine — weekly web release notes covering map layer and billing fixes, and phased mobile releases addressing stability, offline symbology, and KML display.
Mimir's feed is mostly bot-authored Helm bumps; the real release is 3.2, and it is query-engine work.
Four of the six visible entries are automated weekly Helm chart releases opened by a bot, which inflates the apparent cadence without carrying product change. The substance sits in the 3.2 release candidate: 693 pull requests from 61 authors, dominated by Mimir Query Engine optimizations — scalar common subexpression elimination, subquery splitting and caching from instant queries, native histogram support in extended range selectors, histogram_quantiles, and a rename of the experimental duration helpers to min_of and max_of. Operational additions include named per-tenant cost attribution trackers, a tenant-fair compute worker pool in the ingester, memberlist compression selection and Kafka producer compression control.
Fulcrum's field data collection platform is mid-consolidation onto a single mapping engine. The legacy Google Maps engine retires on September 1, 2026, and any organization still defaulting to it on web or mobile will be switched to Esri Maps automatically; Google's satellite, hybrid, and street basemaps survive as options in the Esri layer picker. Everything else this cycle is routine — weekly web release notes covering map layer and billing fixes, and phased mobile releases addressing stability, offline symbology, and KML display.
The Esri consolidation buys capabilities the Google engine could not offer: line and polygon snapping, GPS tracks with background tracking, offline basemaps, a redesigned mobile Location Editor, and direct connectivity to ArcGIS Online and Enterprise feature service layers. That positions Fulcrum as an ArcGIS-adjacent field client rather than a general mobile forms tool. The release cadence is high but the substance is thin between the engine migration and a steady drip of fixes.
Expect migration prompts and default-switch warnings to escalate through August as the deadline approaches, and MMPK layer support to leave early access once Esri is the only engine to support it on.
Four of the six visible entries are automated weekly Helm chart releases opened by a bot, which inflates the apparent cadence without carrying product change. The substance sits in the 3.2 release candidate: 693 pull requests from 61 authors, dominated by Mimir Query Engine optimizations — scalar common subexpression elimination, subquery splitting and caching from instant queries, native histogram support in extended range selectors, histogram_quantiles, and a rename of the experimental duration helpers to min_of and max_of. Operational additions include named per-tenant cost attribution trackers, a tenant-fair compute worker pool in the ingester, memberlist compression selection and Kafka producer compression control.
Two threads dominate. MQE is being ground into the default query path piece by piece — each release moves another optimization or PromQL surface behind a flag, and the flags accumulate rather than flip. The second is multi-tenant fairness and chargeback: cost attribution trackers, a shared tenant-fair worker pool and compression controls are all about making one tenant's queries not everyone else's problem, which is what a hosted operator needs before raising density.
Expect the experimental MQE flags introduced here to move toward default-on in a subsequent release, and cost attribution to grow reporting surfaces now that multiple named trackers per tenant exist.
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 Fulcrum or Grafana Mimir.
Plex's analytics companion has spent a year shipping CVE fixes faster than features.
Delta Lake is handing table authority to Unity Catalog — under a feed buried in Databricks build tags.
OpenCTI ships weekly and is rebuilding its connector catalog into a marketplace.
Fluent Bit runs a 4.2 and a 5.0 train side by side, both fed by the same backport pipeline.
Omni ships weekly, and this quarter every week added something to the AI layer.
Countly's core is in maintenance while every real feature lands in the enterprise journey engine.
See all Fulcrum alternatives → · See all Grafana Mimir alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 5.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. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 5.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 Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.
Top Grafana Mimir alternatives in Analytics are ranked by recent ship velocity. Browse the "Grafana Mimir alternatives" section above for the current picks, or visit /alternatives/grafana-mimir for the full list with editorial commentary on each.