Chord vs Lightdash
Side-by-side trajectory, velocity, and editorial themes.
Chord is rebuilding Copilot on Anthropic models, Enriched Context, and a breaking SQL infra change.
Chord is a CDP that has spent the last quarter rebuilding its Copilot AI from the inside. The reasoning layer switched to Anthropic models, the context capture got expanded as Enriched Context, and the SQL generation pipeline took a breaking infrastructure change. Around that, the regular CDP work — Iterable data modeling, searchable tables, Activations sync redesign — continues at a steady release cadence.
Copilot is becoming the product. Each release this year has tied AI further into the CDP's core data plane — modeling, querying, activations — rather than treating it as a sidebar. Live documentation grounding and feedback memory in the latest release signal a push to keep Copilot accurate as the schema evolves underneath it.
Expect a deeper agentic move where Copilot proposes activations or builds segments end-to-end. The Iterable-style data modeling work hints at where AI assistance lands next.
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.
See more alternatives to Chord →
See more alternatives to Lightdash →