Aim
An experiment tracker grinding on storage performance — and quiet for over a year.
Comparison · Analytics
Citus vs Zipkin
A side-by-side editorial comparison of Citus and Zipkin — release velocity, themes, recent moves, and the top alternatives to consider.
Citus vs Zipkin: at a glance
What is Citus?
Citus is in maintenance mode across four branches, with the feature work invisible from the feed.
Citus is the Postgres extension that shards tables across a cluster, and its release feed right now is almost entirely branch upkeep. Four lines are live at once — 12.1, 13.3, 14.0 and 14.1 — and the recent tags are backports and CI fixes moving between them, authored by a small handful of maintainers. The last release with user-facing feature text is Citus 14.0 in February, which added PostgreSQL 18.1 support and pointed at a blog post rather than listing what changed.
What is Zipkin?
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.
Citus vs Zipkin: editorial side-by-side
Citus
2.5ANALYTICS
Citus is in maintenance mode across four branches, with the feature work invisible from the feed.
◆ Current state
Citus is the Postgres extension that shards tables across a cluster, and its release feed right now is almost entirely branch upkeep. Four lines are live at once — 12.1, 13.3, 14.0 and 14.1 — and the recent tags are backports and CI fixes moving between them, authored by a small handful of maintainers. The last release with user-facing feature text is Citus 14.0 in February, which added PostgreSQL 18.1 support and pointed at a blog post rather than listing what changed.
◆ Where it's heading
The shape here is a mature extension keeping several supported branches alive rather than pushing new capability. Correctness is the live concern: the 12.1 patches fix wrong query results, an EXPLAIN segfault, a standby coordinator crash and a deadlock, all backported from work done on newer branches. Note that the release notes are thin by design — 13.3 and 14.1 list only PR titles for backports and test plumbing, so the feed understates whatever is landing on the main line.
◆ Prediction
More 12.1 patch tags are the safe expectation while that branch stays supported. Whether the 14.x line picks up new distributed-query features is not visible from these entries — the notes only cover backports, so the main-branch work would have to be read elsewhere.
Zipkin
0.0ANALYTICS
Zipkin's last release was January 2025 — a dependency bump, and then nothing.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Citus and Zipkin
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 Citus or Zipkin.
Glances
Every Glances release this year has carried CVE fixes — the monitoring tool is being audited in public.
OpenObserve
One release turns a telemetry store into synthetics, workflows, and AI observability.
Chord
Chord rebuilt Copilot, renamed it, and let it start building the audiences it used to describe
Polars
A deprecation sweep and hive-partition join rewrites, shipped on two trains at once.
Pinpoint
ServerMap rebuilt and application names finally long enough to describe a service.
See all Citus alternatives → · See all Zipkin alternatives →
Recent activity from Citus and Zipkin
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoCitus12.1.14 fixes wrong results, an EXPLAIN segfault and a standby crash
- 1mo agoCitusCitus 14.1 ships as a backport and CI maintenance release
- 1mo agoCitus12.1.13 fixes a deadlock, crashes and internal UDF ownership
- 1mo agoCitusCitus 13.3 lands as a backport-only release on the 13.x line
- 5mo agoCitusCitus 14.0 adds PostgreSQL 18.1 support
- 1y agoZipkinMaven versions realigned with the Docker images
- 1y agoZipkinSpring Boot, Netty and Micrometer updated to clear CVEs
- 2y agoZipkinDependency and base-image updates for CVEs
- 2y agoZipkinZipkin 3.4
- 2y agoZipkinSpring Boot 3.3 and Alpine 3.20, with an OpenSearch test image
Frequently asked questions
What is the difference between Citus and Zipkin?
They serve adjacent needs but don't currently overlap on shipped themes. Citus is currently shipping more aggressively (velocity 2.5 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.
Is Citus better than Zipkin?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Citus is currently shipping more aggressively (velocity 2.5 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.
What are the best alternatives to Citus?
Top Citus alternatives in Analytics are ranked by recent ship velocity. Browse the "Citus alternatives" section above for the current picks, or visit /alternatives/citus for the full list with editorial commentary on each.
What are the best alternatives to Zipkin?
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.