Glances
Every Glances release this year has carried CVE fixes — the monitoring tool is being audited in public.
Comparison · Analytics
Citus vs Aim
A side-by-side editorial comparison of Citus and Aim — release velocity, themes, recent moves, and the top alternatives to consider.
Citus vs Aim: 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 Aim?
An experiment tracker grinding on storage performance — and quiet for over a year.
Aim is an open-source ML experiment tracker whose 3.2x line reads almost entirely as storage and indexing work: constant indexing of in-progress runs, reading from a single unified database, fallbacks when the index is missing, stalled-run detection. The user-facing additions in this window are narrow — a read-only UI mode, report creation, self-signed SSL support, PytorchLightning logger contexts. The most recent entry here is from May 2025, making this feed over a year stale.
Citus vs Aim: 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.
Aim
0.0ANALYTICS
An experiment tracker grinding on storage performance — and quiet for over a year.
◆ Current state
Aim is an open-source ML experiment tracker whose 3.2x line reads almost entirely as storage and indexing work: constant indexing of in-progress runs, reading from a single unified database, fallbacks when the index is missing, stalled-run detection. The user-facing additions in this window are narrow — a read-only UI mode, report creation, self-signed SSL support, PytorchLightning logger contexts. The most recent entry here is from May 2025, making this feed over a year stale.
◆ Where it's heading
The direction across these releases is toward making the local storage layer trustworthy at scale rather than expanding what the tracker does. Repeated fixes around index corruption, empty index.db handling, false-positive metric checks, and session refresh point at users hitting durability problems on long-running or high-volume tracking. Integration surface grows only where contributors push it — S3 client config, Lightning contexts, remote mass updates all arrive as outside contributions rather than a planned roadmap.
◆ Prediction
With no release visible in over a year, the honest read is that cadence has stopped rather than shifted; the entries give no signal of a 4.x line or a direction change. If work resumes, the pattern suggests more storage-correctness fixes before any new capability.
Alternatives to Citus and Aim
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 Aim.
Zipkin
Zipkin's last release was January 2025 — a dependency bump, and then nothing.
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.
Recent activity from Citus and Aim
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 agoAim🚀 v3.29.1 - Improved query performance by reading from single unified database and constant data indexing, fixes in min/max calculation in UI and jupiter/colab integration
- 1y agoAim🚀 v3.28.0 - Improved performance by removing redundant checks and bypassing runs known to yield false results, new callback for hugging face distributed runs, fixes in Tag duplicates handling, remote tracking exception handling and more, code style improvements.
- 1y agoAim🚀 v3.27.0 - Enhancements for PytorchLightning logger and S3ArtifactsStorage, fixes for RunStatusReporter, metric aggregations and tag creation from parallel runs
- 1y agoAim🚀 v3.24.0 - Support for mass updates in remote tracking, fixes in database error handling and bookmarks page scroll
- 1y agoAim🚀 v3.25.1 - Fixes in empty index.db handling and python 3.12 builds
- 1y agoAim🚀 v3.25.0 - Reports support, ability to use self-signed SSL certificates
Frequently asked questions
What is the difference between Citus and Aim?
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 Aim?
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 Aim?
Top Aim alternatives in Analytics are ranked by recent ship velocity. Browse the "Aim alternatives" section above for the current picks, or visit /alternatives/aim for the full list with editorial commentary on each.