Microsoft Clarity
Clarity pitches one view of agents, LLM referrals and human visitors.
A side-by-side editorial comparison of Dagster and Zipkin — release velocity, themes, recent moves, and the top alternatives to consider.
Dagster is untangling itself from dbt-core so dbt Fusion can run without a fight.
Dagster's recent 1.13 releases follow two threads. dagster-dbt no longer installs dbt-core, and a dbt v2 extra installs the Fusion engine with clear errors if the two are mixed. The UI keeps gaining phone layouts, now covering code locations, sensors and schedules, while 1.13.29 also speeds up run logs, global search and the asset catalog. Dagster+ added capacity-based alert policies, and agents can retry code locations that fail to start.
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.
Dagster's recent 1.13 releases follow two threads. dagster-dbt no longer installs dbt-core, and a dbt v2 extra installs the Fusion engine with clear errors if the two are mixed. The UI keeps gaining phone layouts, now covering code locations, sensors and schedules, while 1.13.29 also speeds up run logs, global search and the asset catalog. Dagster+ added capacity-based alert policies, and agents can retry code locations that fail to start.
The dbt work is a dependency reset with real consequences, because Fusion and dbt-core claim the same import namespace and overwrite each other silently. Dagster made the safe path the default and accepted a breaking change to do it. The rest of the window is operational hardening: resuming run workers on ECS, cross-account service discovery and clearer failure reasons when a run worker dies.
Weekly-style 1.13 releases should keep extending Fusion coverage in dagster-dbt, since metadata fetching there still degrades to warnings. Declarative Automation for jobs does not appear in these entries, so its exit from preview remains unconfirmed.
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 Dagster or Zipkin.
Clarity pitches one view of agents, LLM referrals and human visitors.
Delta Lake's public stream is release mechanics; Kernel builds now carry a 4.5.0 label.
Loki 4.0 RC strips out legacy storage backends and the simple scalable mode.
OpenObserve 1.2.0-rc1 opens a metrics v2 cycle with chart alerts and forecasts.
Keboola connects GitHub organizations once, ending personal tokens for private repos.
dbt-core 1.13 drops Python 3.10 and learns to tolerate v2-only project config.
See all Dagster 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. Dagster is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. Dagster is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 Dagster alternatives in Analytics are ranked by recent ship velocity. Browse the "Dagster alternatives" section above for the current picks, or visit /alternatives/dagster 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.