← Back to home
Comparison · Analytics

dbt Core vs gtsummary

A side-by-side editorial comparison of dbt Core and gtsummary — release velocity, themes, recent moves, and the top alternatives to consider.

dbt Core vs gtsummary: at a glance

Featuredbt Coregtsummary
SectorAnalyticsAnalytics
Velocity score6.30.0
Sparks · 30d00
Top themesanalytics-engineering, dbt-fusion, adapters, clickhouseclinical-tables, analysis-results-data, regression-summaries, reproducible-reporting
Last editorial update16h ago4d ago
WebsiteVisit →Visit →

What is dbt Core?

dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs

Fusion 2.0 is in its second beta, and the content has shifted from engine capability to adapter coverage. beta.2 is almost entirely ClickHouse — Dictionary materialization, index definitions, additional settings, a relation-scoped catalog macro that fixes --write-catalog, and a seed nullability fix — plus Entra bearer-token authentication for the Fabric adapter. Behind it sits the August 14 backport wave, which cut releases for 1.1 through 1.8 in a single day to deliver one deprecated-version warning.

Read the full dbt Core trajectory →

What is gtsummary?

gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.

gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.

Read the full gtsummary trajectory →

dbt Core vs gtsummary: editorial side-by-side

D
dbt Core
ANALYTICS
6.3

dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs

◆ Current state

Fusion 2.0 is in its second beta, and the content has shifted from engine capability to adapter coverage. beta.2 is almost entirely ClickHouse — Dictionary materialization, index definitions, additional settings, a relation-scoped catalog macro that fixes --write-catalog, and a seed nullability fix — plus Entra bearer-token authentication for the Fabric adapter. Behind it sits the August 14 backport wave, which cut releases for 1.1 through 1.8 in a single day to deliver one deprecated-version warning.

◆ Where it's heading

The two ends of this project are pulling apart cleanly. Old branches are being prepared for retirement — a deprecation warning fanned across eight of them, Python 3.8 testing dropped from 1.4 through 1.6 — while Fusion accumulates the adapter breadth it needs to be a credible replacement. beta.1 proved the engine could bind without a catalog; beta.2 is the unglamorous follow-through of making a specific warehouse work properly.

◆ Prediction

Expect further beta releases filling in per-adapter gaps rather than new engine capability, and formal end-of-life notices for the branches that just took the deprecation warning.

G
gtsummary
ANALYTICS
0.0

gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.

◆ Current state

gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.

◆ Where it's heading

The ARD work is the through-line. Table IDs exist so gather_ard() can return a named list; hierarchical tables gained per-level sorting and targeted filtering; ARD inputs are pre-processed so sorting applies to non-standard shapes. The package is becoming a structured-results engine that happens to render tables, rather than a renderer alone. Alongside that, 2.2.0 restored data pre-processing that 2.0 had removed after the reduced functionality hurt users — a maintainer willing to reverse a major-version decision.

◆ Prediction

Expect the hierarchical and ARD functions, introduced as a preview without a full deprecation cycle, to keep stabilizing toward a settled API rather than new table types appearing.

Alternatives to dbt Core and gtsummary

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 dbt Core or gtsummary.

See all dbt Core alternatives → · See all gtsummary alternatives →

Recent activity from dbt Core and gtsummary

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agodbt CoreFusion beta.2 fills in ClickHouse materializations and catalogs
  2. 6d agodbt Coredbt 1.2.7 backports the deprecated-version warning and old fixes
  3. 6d agodbt Coredbt 1.1.6 backports the deprecated-version warning and old fixes
  4. 6d agodbt Coredbt 1.3.8 backports the deprecated-version warning
  5. 6d agodbt Coredbt 1.4.10 drops Python 3.8 and warns on deprecated versions
  6. 6d agodbt Coredbt 1.5.12 drops Python 3.8 and warns on deprecated versions
  7. 2mo agogtsummaryTheme elements no longer evaluated by default
  8. 8mo agogtsummaryARD strata functions and finer theme control
  9. 11mo agogtsummaryPer-level hierarchical sorting and labeled stacking
  10. 1y agogtsummaryTable splitting, ID labeling, and add_difference_row
  11. 1y agogtsummaryData pre-processing restored after the 2.0 removal
  12. 1y agogtsummarytbl_merge gains explicit merge columns

Frequently asked questions

What is the difference between dbt Core and gtsummary?

They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 6.3 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 dbt Core better than gtsummary?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 6.3 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 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.

What are the best alternatives to gtsummary?

Top gtsummary alternatives in Analytics are ranked by recent ship velocity. Browse the "gtsummary alternatives" section above for the current picks, or visit /alternatives/gtsummary-r for the full list with editorial commentary on each.