Lightdash vs Fulcrum
Side-by-side trajectory, velocity, and editorial themes.
Lightdash is turning the analyst's prompt into the primary way to build BI
Lightdash is pushing hard on AI-native BI. Its data apps now generate reusable chart types from a plain-language prompt, verified content has gone GA and merged with the AI-agent and MCP layer, and AI-written summaries are appearing in scheduled deliveries. Alongside that, steady core work continues on SQL parameters, chart layouts, and enterprise controls like user impersonation.
The clear direction is a prompt-driven analytics surface backed by a trusted-content layer that external agents like Claude and Cursor can query through MCP. Expect the 'describe it and Lightdash builds it' pattern to spread from chart types into more of the modeling and dashboard workflow, with verification as the guardrail that keeps agent answers trustworthy.
The next moves likely push prompt-to-artifact generation deeper into dashboards and the semantic model, and expand what the MCP and verified-content layer exposes to external agents.
Fulcrum keeps hardening field GIS capture on a steady weekly cadence.
Fulcrum ships on a predictable weekly rhythm across web, iOS, and Android, and the work is concentrated on field mapping and ArcGIS interoperability. Recent releases center on map annotation, geometry rendering, and offline reliability rather than new product surface.
The arc is incremental hardening of the mobile GIS workflow — WMS and ArcGIS connectivity fixes, map scale bars, background GPS tracking — punctuated by occasional field-UX additions like sketching on a captured map. It reads as a mature product optimizing its core rather than changing direction.
Expect the weekly web and mobile cadence to continue, with more map-annotation and ArcGIS-integration refinements. Nothing in these entries points to a larger platform shift.
See more alternatives to Lightdash →
See more alternatives to Fulcrum →