OpenSearch Dashboards
Three releases in a year, all of them about the Vega dependency — the feed shows nothing else.
Comparison · Analytics
Citus vs dbt Core
A side-by-side editorial comparison of Citus and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
Citus vs dbt Core: at a glance
What is Citus?
Citus keeps three Postgres branches alive while chasing each new major
Citus publishes synchronized maintenance releases across at least three live branches — 14.1, 13.3 and 12.1.13 all went out on the same day in July 2026 — with contents that are almost entirely backports of the same handful of upstream fixes. The substantive release in the window is Citus 14.0 from February, which added PostgreSQL 18.1 support. Release titles are inconsistent, several carrying release dates that contradict their publication date.
What is dbt Core?
Two engines in one repo: the Python 1.x line tightens while Fusion 2.0 goes lakehouse-catalog native
dbt-core is releasing on two tracks at once. The Python line reached 1.12.0 on 16 July after three release candidates, and it is a tightening release: the experimental `dbt login` command and the bundled dbt-state plugin were removed outright, and flags introduced in 1.9 and 1.10 now default to true. The 2.0.0 alpha track is the Fusion engine, and its work is almost entirely about catalogs — read-write Horizon and Unity access over Iceberg REST via DuckDB, a catalogs.yml v2 covering DuckLake, Iceberg REST and local filesystem, plus catalog_database overrides and Redshift catalog generation through SHOW TABLES and SVV_REDSHIFT_COLUMNS.
Citus vs dbt Core: editorial side-by-side
Citus
0.0ANALYTICS
Citus keeps three Postgres branches alive while chasing each new major
◆ Current state
Citus publishes synchronized maintenance releases across at least three live branches — 14.1, 13.3 and 12.1.13 all went out on the same day in July 2026 — with contents that are almost entirely backports of the same handful of upstream fixes. The substantive release in the window is Citus 14.0 from February, which added PostgreSQL 18.1 support. Release titles are inconsistent, several carrying release dates that contradict their publication date.
◆ Where it's heading
The pattern is a distributed-Postgres extension whose roadmap is set by Postgres itself: a major Citus version tracks a major Postgres version, then a long tail of branch releases carries fixes backward to users who cannot upgrade. Recent backport content is concentrated on correctness in edge cases — role propagation with missing grantor dependencies, deadlocks when adding named constraints with long partition names, crashes in CREATE STATISTICS — plus tightening ownership checks on citus-internal UDFs.
◆ Prediction
Expect the next Citus major to line up with the next PostgreSQL major, with 12.1 continuing to receive backports until it is retired. The entries do not indicate which branch is nearest end-of-life.
dbt Core
7.5ANALYTICS
Two engines in one repo: the Python 1.x line tightens while Fusion 2.0 goes lakehouse-catalog native
◆ Current state
dbt-core is releasing on two tracks at once. The Python line reached 1.12.0 on 16 July after three release candidates, and it is a tightening release: the experimental `dbt login` command and the bundled dbt-state plugin were removed outright, and flags introduced in 1.9 and 1.10 now default to true. The 2.0.0 alpha track is the Fusion engine, and its work is almost entirely about catalogs — read-write Horizon and Unity access over Iceberg REST via DuckDB, a catalogs.yml v2 covering DuckLake, Iceberg REST and local filesystem, plus catalog_database overrides and Redshift catalog generation through SHOW TABLES and SVV_REDSHIFT_COLUMNS.
◆ Where it's heading
The division of labour between the two tracks is clear from the entries: 1.x is consolidating and removing experiments, while 2.0 is where the new surface area lands. The 2.0 surface is specifically the lakehouse catalog layer — dbt is moving from a tool that writes to a warehouse toward one that binds to open table catalogs directly, with materialization made catalog-aware. Notably 1.12.0rc1 also teaches the Python engine to tolerate Fusion-specific warn_error_options rather than erroring, so the two engines are being made to coexist in the same projects rather than fork.
◆ Prediction
The alphas are still expanding catalog coverage adapter by adapter, so expect further catalog integrations and continued catalogs.yml v2 work before 2.0 leaves alpha. On the Python side, with the deprecated flags now defaulted and the experimental commands removed, 1.12 looks like a stabilization point rather than a base for new features.
Alternatives to Citus and dbt Core
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 dbt Core.
Apache Kylin
Kylin ships once a year with empty release notes and a native engine nobody is being told about.
Apache Iceberg
Iceberg's release cadence is now backports and CVE patches across three live minor lines.
Mage
Feature releases every two months in 2024; one bugfix release in the last twelve.
OpenMetadata
MCP servers became first-class governed assets in 1.13.0 — and 2.0 is now in release candidate.
TimescaleDB
Every release in this window is columnstore work — compression is where TimescaleDB is spending
See all Citus alternatives → · See all dbt Core alternatives →
Recent activity from Citus and dbt Core
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13d agodbt CoreFusion alpha 5: Redshift datasharing catalogs and job-specific deferral
- 17d agodbt Coredbt-core 1.12.0 drops `dbt login` and the dbt-state plugin ⚡
- 18d agodbt Core1.12.0 release candidate 3
- 23d agodbt Core1.12.0 release candidate 2
- 26d agodbt Core1.12.0 release candidate 1
- 27d agodbt CoreFusion gains read-write Iceberg REST catalogs and catalogs.yml v2 ⚡
- 1mo agoCitusCitus 14.1 backport release
- 1mo agoCitusDeadlock, crash and role-propagation fixes for 12.1
- 1mo agoCitusCitus 13.3 backport release
- 5mo agoCitusCitus 14.0 adds PostgreSQL 18.1 support ⚡
Frequently asked questions
What is the difference between Citus and dbt Core?
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 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.
Is Citus better than dbt Core?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 7.5 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.
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 dbt Core?
Top dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.