Aim
An experiment tracker grinding on storage performance — and quiet for over a year.
A side-by-side editorial comparison of Lightdash and Zipkin — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Lightdash | Zipkin |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 8.8 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | bi, data-apps, agent-native, mcp | distributed tracing, maintenance only, stale feed, opensearch |
| Last editorial update | 2d ago | 2h 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.
Zipkin's last release was January 2025 — a dependency bump, and then nothing.
The recent history is three consecutive maintenance releases whose entire content is dependency and base-image updates: 3.4.3 aligned Maven versions with the Docker images, 3.4.2 and 3.4.1 moved Spring Boot, Netty, Micrometer, Armeria, Alpine and the JRE forward to clear CVEs. The last release carrying a feature was 3.4 in May 2024, which added OpenSearch v2 as a storage backend using the existing ES_-prefixed environment variables.
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.
The recent history is three consecutive maintenance releases whose entire content is dependency and base-image updates: 3.4.3 aligned Maven versions with the Docker images, 3.4.2 and 3.4.1 moved Spring Boot, Netty, Micrometer, Armeria, Alpine and the JRE forward to clear CVEs. The last release carrying a feature was 3.4 in May 2024, which added OpenSearch v2 as a storage backend using the existing ES_-prefixed environment variables.
This is a project in preservation rather than development. The pattern across the window — feature in May 2024, then three releases of purely defensive dependency work, then silence since January 2025 — describes a mature tracing server being kept safe to run rather than extended. The distributed-tracing work that would once have landed here now largely happens in OpenTelemetry, which Zipkin interoperates with rather than competes against.
The feed has produced nothing for nineteen months, so the honest read is that no next release is scheduled. If one comes, the shape of the last three says it will be another dependency and base-image refresh rather than new capability.
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 Zipkin.
An experiment tracker grinding on storage performance — and quiet for over a year.
Every Glances release this year has carried CVE fixes — the monitoring tool is being audited in public.
One release turns a telemetry store into synthetics, workflows, and AI observability.
Chord rebuilt Copilot, renamed it, and let it start building the audiences it used to describe
Citus is in maintenance mode across four branches, with the feature work invisible from the feed.
A deprecation sweep and hive-partition join rewrites, shipped on two trains at once.
See all Lightdash alternatives → · See all Zipkin 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 Zipkin alternatives in Analytics are ranked by recent ship velocity. Browse the "Zipkin alternatives" section above for the current picks, or visit /alternatives/zipkin for the full list with editorial commentary on each.