Cluvio vs Lightdash
Side-by-side trajectory, velocity, and editorial themes.
Cluvio keeps sharpening the SQL-analyst workflow, and now lets you query files without a database.
Cluvio is a SQL-first BI tool methodically polishing the analyst loop: chart types, alerting, settings, and exports. The recent run leans heavily toward usability — redesigned preferences with country presets, a clearer datasource picker, and exports that now carry their own context. The one real capability expansion is Static Tables, which lets users query uploaded CSV and Excel files with SQL via an embedded DataFusion engine.
Most recent work tightens existing surfaces rather than opening new ones — the product is maturing its core rather than chasing scope. The exception, querying files without a connected database, points to Cluvio positioning itself for ad-hoc analysis, not only dashboards over warehouses. Expect continued UX consolidation across settings, exports, and pickers, interleaved with occasional capability adds like new chart types.
Likely next moves are further build-out of Static Tables — more file formats or richer joins across uploads — alongside continued chart and alerting polish. The cadence reads as incremental shipping rather than a large directional pivot.
Lightdash widens its surface with admin tooling, governance, and intent-driven formulas.
Lightdash is shipping in three directions at once: operator tools (user impersonation with audit + 15-min cap, auto-expiring preview projects), authoring polish (row/column limits, color palette hierarchy, saved metric trees), and a step into AI-assisted authoring with spreadsheet-style formulas where the editor infers intent. The pace is fast — multiple releases per week — and the changes are mostly visible to working analysts.
The throughline is reducing how much SQL and YAML an analyst needs to touch: formulas in plain English, filters that read user attributes from the UI, rollback that includes chart configs, color governance that doesn't require code. Lightdash is pushing the surface area an analyst manages out of files and into the product, then layering controls (audit-logged impersonation, palette precedence) for the orgs that need governance.
Expect intent-driven authoring to widen beyond table calculations — likely metric definitions and dbt model suggestions next — and for the metric-tree canvas to become a planning surface, not just a visualization. Governance features (impersonation, audit) will likely consolidate into an enterprise tier.
See more alternatives to Cluvio →
See more alternatives to Lightdash →