dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of admiral and TimescaleDB — release velocity, themes, recent moves, and the top alternatives to consider.
admiral spent its last cycle making complex derivations documentable rather than adding more of them.
admiral is the pharmaverse's ADaM dataset derivation toolkit — a large library of derive_* functions for building analysis datasets from SDTM. The 1.2.0 and 1.3.0 releases added new derivation functions and then a substantial documentation overhaul: argument defaults now appear in the help text and complex functions carry titled, described examples. 1.3.1 was a hotfix for links and the search index.
TimescaleDB is paying down correctness debt in its columnstore query paths.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
admiral is the pharmaverse's ADaM dataset derivation toolkit — a large library of derive_* functions for building analysis datasets from SDTM. The 1.2.0 and 1.3.0 releases added new derivation functions and then a substantial documentation overhaul: argument defaults now appear in the help text and complex functions carry titled, described examples. 1.3.1 was a hotfix for links and the search index.
The direction is toward usability of an already-large API rather than growth of it. 1.1.0 rewrote error messaging to be user-facing, 1.2.0 added flexibility to duplicate handling across several functions via check_type, and 1.3.0 invested in the structured-example documentation that the rdx_roclet work in {admiraldev} made possible. The two packages move together.
With the documentation infrastructure in place, expect the remaining complex derivation functions to be brought up to the structured-example standard, and new therapeutic-area work to keep landing in the extension packages rather than the core.
The 2.29 line is in patch mode after 2.29.0 landed chunk exclusion for DML in late July. 2.29.1 carried three security advisories alongside compression fixes, and 2.29.2 is bug fixes only - most of them wrong-results bugs in the columnar execution paths rather than crashes. Every release note in this window recommends upgrading at the next opportunity.
The feature work of 2.27 and 2.28 - vectorized filter evaluation, first/last derived straight from columnstore batch metadata, sparse indexes, SkipScan on compressed data - has been followed by a steady stream of fixes to those same code paths. 2.29.2 alone repairs SkipScan dropping uncompressed rows, sparse-index pushdown returning wrong results for IS NULL, and gapfill over window aggregates. That is the normal cost of pushing query optimizations into a compressed columnar store, and the project is working through it release by release rather than pausing.
With three consecutive patch releases on the 2.29 line and no new highlighted features since 2.29.0, the next minor is likely to resume the columnstore performance work - though the density of wrong-results fixes suggests more patches first.
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 admiral or TimescaleDB.
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAI got skills three weeks ago; everything since has been making them routine.
See all admiral alternatives → · See all TimescaleDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TimescaleDB 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. TimescaleDB 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 admiral alternatives in Analytics are ranked by recent ship velocity. Browse the "admiral alternatives" section above for the current picks, or visit /alternatives/admiral for the full list with editorial commentary on each.
Top TimescaleDB alternatives in Analytics are ranked by recent ship velocity. Browse the "TimescaleDB alternatives" section above for the current picks, or visit /alternatives/timescaledb for the full list with editorial commentary on each.