Aim
An experiment tracker grinding on storage performance — and quiet for over a year.
A side-by-side editorial comparison of Pinpoint and Citus — release velocity, themes, recent moves, and the top alternatives to consider.
ServerMap rebuilt and application names finally long enough to describe a service.
Pinpoint ships a minor roughly once a year with patch releases in between. The 3.1.0 release rebuilt ServerMap as V3 with a redesigned storage layout, a new query path and a new set of map tables, and raised the applicationName ceiling from 24 to 254 characters — gated behind an agent property that requires collector 3.1.0 or higher. The patch line before it is mostly backports and plugin compatibility: Java 26, Kafka Streams, Kafka 4.x, S3, nested Spring Boot JARs.
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.
Pinpoint ships a minor roughly once a year with patch releases in between. The 3.1.0 release rebuilt ServerMap as V3 with a redesigned storage layout, a new query path and a new set of map tables, and raised the applicationName ceiling from 24 to 254 characters — gated behind an agent property that requires collector 3.1.0 or higher. The patch line before it is mostly backports and plugin compatibility: Java 26, Kafka Streams, Kafka 4.x, S3, nested Spring Boot JARs.
The plugin surface expands continuously — each release absorbs another client library or runtime version — while the platform work arrives in rare, larger jumps that touch storage schema and require coordinated agent and collector upgrades. The 3.1.0 changes suggest the constraints being addressed are those of large deployments: structured naming schemes that no longer fit, and a topology view whose query path needed redesigning rather than tuning.
Expect the 3.1 line to spend its patches stabilising the ServerMap V3 storage path and backporting plugin updates, with the next set of runtime and client integrations arriving the same way they always have.
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.
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.
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.
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 Pinpoint or Citus.
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.
Zipkin's last release was January 2025 — a dependency bump, and then nothing.
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
A deprecation sweep and hive-partition join rewrites, shipped on two trains at once.
See all Pinpoint alternatives → · See all Citus alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
Top Pinpoint alternatives in Analytics are ranked by recent ship velocity. Browse the "Pinpoint alternatives" section above for the current picks, or visit /alternatives/pinpoint for the full list with editorial commentary on each.
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.