Looker
Looker's release feed is mostly page furniture; the shipping behind it is thin.
A side-by-side editorial comparison of Lightdash and Plotly — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Lightdash | Plotly |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 8.8 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | bi, data-apps, agent-native, mcp | dash-hosting, plotly-cloud, custom-domains, compute-credits |
| Last editorial update | 15h ago | 11h 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.
The desktop app builder is pre-1.0, but Plotly Cloud quietly turned into a Dash hosting platform.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
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.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
The centre of gravity has moved from the desktop tool to the hosting product. Studio's releases are pre-1.0 hardening — navigation, credential handling, install paths — while Cloud is the side gaining capability that changes what a customer can do, and it is where the tier boundaries are being drawn. Consumption economics are becoming explicit, with idle spend and cold starts surfaced as customer-tunable settings rather than hidden platform behaviour.
The next Cloud releases most likely extend the resource and access controls a hosted app needs — finer app sizing, or authentication and access rules on custom domains — rather than adding capability to Studio.
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 Plotly.
Looker's release feed is mostly page furniture; the shipping behind it is thin.
Fulcrum is retiring Google Maps for Esri and stabilising the ArcGIS stack behind it.
Shynet went silent for two and a half years and a security audit is what woke it up.
Power BI's monthly grind: authoring defaults, DAX documentation, and cleaner axes.
BigQuery is making itself agent-callable and pulling inference inside the SQL boundary.
TimescaleDB trades new features for lock contention wins and a security patch
See all Lightdash alternatives → · See all Plotly 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 2 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 2 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 Plotly alternatives in Analytics are ranked by recent ship velocity. Browse the "Plotly alternatives" section above for the current picks, or visit /alternatives/plotly for the full list with editorial commentary on each.