OpenCTI
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
A side-by-side editorial comparison of Lightdash and Marquez — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Lightdash | Marquez |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 8.8 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | bi, data-apps, agent-native, mcp | openlineage, data-lineage, observability, metadata |
| Last editorial update | 7d ago | 19h ago |
| Website | — | Visit → |
Lightdash is turning BI into an app platform its users' coding agents can build against.
Lightdash's centre of gravity has moved from charts to Data Apps. In the last month apps gained the ability to call third-party HTTP APIs through a credential-injecting proxy, a generator that builds reusable chart types from a prompt, query-inspection tooling, and now a local workflow: scaffold an app with the CLI, iterate on it in your own IDE against live data, and upload the source for Lightdash to build on your instance. Around that, content as code expanded to cover dashboards, permissions, AI agents, automations and org roles, and verified content was unified with AI agents so the MCP serves one trusted source.
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
Marquez is the reference metadata server for OpenLineage, and this window captures a concentrated push on its web interface: a column-lineage page and redesigned lineage graph in 0.45.0, data quality and job status displays in 0.47.0, and a data observability dashboard in 0.50.0 showing event stats over 24-hour and 7-day windows with per-source, per-dataset and per-job views. The API side moved in step — job tagging, dataset schema versions, paging on jobs and dataset versions, job-to-job lineage, richer metrics labels. One contributor accounts for nearly all the web work in these entries. Note that the 0.45 through 0.49 releases were all stamped within three minutes of each other and in reverse version order, so publication timestamps here do not reflect release order.
Lightdash's centre of gravity has moved from charts to Data Apps. In the last month apps gained the ability to call third-party HTTP APIs through a credential-injecting proxy, a generator that builds reusable chart types from a prompt, query-inspection tooling, and now a local workflow: scaffold an app with the CLI, iterate on it in your own IDE against live data, and upload the source for Lightdash to build on your instance. Around that, content as code expanded to cover dashboards, permissions, AI agents, automations and org roles, and verified content was unified with AI agents so the MCP serves one trusted source.
Two threads are converging. One makes the semantic layer legible to agents - verified content and AI-verified answers share a single source of truth that the Lightdash MCP and outside assistants read from. The other makes the platform something agents can write to, with apps scaffolded locally, built by whatever coding agent the developer prefers, then shipped into a governed instance. The governance framing is carrying real weight in both, since the pitch is that data and metrics stay controlled while authoring moves outside the product.
Expect the local app workflow and content as code to fuse, so agent-driven changes to dashboards, permissions and apps arrive as pull requests against a Lightdash instance. The pieces are shipped; what these entries do not settle is how agent-authored apps get reviewed or approved before viewers see them.
Marquez is the reference metadata server for OpenLineage, and this window captures a concentrated push on its web interface: a column-lineage page and redesigned lineage graph in 0.45.0, data quality and job status displays in 0.47.0, and a data observability dashboard in 0.50.0 showing event stats over 24-hour and 7-day windows with per-source, per-dataset and per-job views. The API side moved in step — job tagging, dataset schema versions, paging on jobs and dataset versions, job-to-job lineage, richer metrics labels. One contributor accounts for nearly all the web work in these entries. Note that the 0.45 through 0.49 releases were all stamped within three minutes of each other and in reverse version order, so publication timestamps here do not reflect release order.
The arc is a backend project growing a front end: lineage data that existed in the API was progressively given pages, panels and paging, and by 0.50.0 the framing had shifted from lineage graph to observability dashboard. Tagging deepened in the same period, moving from dataset tags to field-level tags to job tags. That arc stops abruptly — 0.50.0 in October 2024 is the last entry, with nothing published in the roughly two years since.
The entries give no roadmap signal past 0.50.0, and the job-to-job lineage change was explicitly framed as a prompt for a wider parent/child hierarchy discussion that no later release picks up, so that hierarchy work is best read as unfinished rather than planned.
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 Lightdash or Marquez.
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
See all Lightdash alternatives → · See all Marquez alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Lightdash is currently shipping more aggressively (velocity 8.8 vs 0.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. Lightdash is currently shipping more aggressively (velocity 8.8 vs 0.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 Lightdash alternatives in Analytics are ranked by recent ship velocity. Browse the "Lightdash alternatives" section above for the current picks, or visit /alternatives/lightdash for the full list with editorial commentary on each.
Top Marquez alternatives in Analytics are ranked by recent ship velocity. Browse the "Marquez alternatives" section above for the current picks, or visit /alternatives/marquez for the full list with editorial commentary on each.