Lightdash vs Hex
Side-by-side trajectory, velocity, and editorial themes.
Lightdash chips away at the SQL barrier with NL-to-formula table calcs and metric-tree visualization.
The release cadence is high and the work spans three areas: lowering the technical barrier (spreadsheet-style formulas in table calculations, plain references to grand totals), enriching what a chart and dashboard can express (color palettes at every scope, row/column limits, rich-text table cells), and self-serve operability (default user spaces, expiring preview projects, dashboard-version rollbacks that include chart configs). The Canvas now hosts persistent metric trees, hinting at a heavier semantic-layer story.
Lightdash is positioning between a dbt-native semantic layer (where SQL-fluent analysts live) and a self-serve BI tool (where business users live). The intent-driven formula editor and reference-total functions chip away at the SQL prerequisite for table calculations, while Saved Trees push the metric model into something visually editable. Underneath, the platform is doing the unglamorous self-serve work — personal spaces, palette hierarchies, preview hygiene — that BI products need to survive in larger orgs.
Expect the formula editor to grow into broader AI-assisted authoring (filters, joins, custom dimensions) and Saved Trees to evolve into a more general semantic-layer view that consumes from dbt and produces governance artifacts. Color and palette work suggests embedded/customer-facing BI ambitions next.
Hex bets the product on prompt-as-authoring: data apps are now one sentence away.
Hex is in the most aggressive AI-agent build-out of any analytics tool we track. The last month has stacked: repo connections as agent context, Generative Data Apps, prompt-to-dashboard, context suggestions, user memory, projects-as-context, and a CLI for programmatic context control. Around it, the surface has been extended with Hex-in-Claude, Hex-in-Cursor, a ClickHouse partnership, and Google Sheets export.
Hex is reorganizing itself around an agent that the user steers with prompts and grounds with context. Each release adds either more context channels (repos, projects, semantic models, memory, guides) or more places the agent can act (apps, dashboards, third-party clients). The product surface is being recast: notebooks remain, but the primary entry point is becoming the prompt. Expect Hex to keep stacking context sources and to start moving from authoring assist into autonomous, scheduled, agent-driven workflows.
Next plausible moves: agent-authored scheduled jobs or alerts, deeper integrations with semantic layer tools (dbt-style metric stores) as context sources, and more co-pilot embeddings in third-party editors. A pricing tier tied to agent usage is increasingly hard to delay.
See more alternatives to Lightdash →
See more alternatives to Hex →