← Back to home
Comparison · Analytics

dbt Core vs writexl

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

dbt Core vs writexl: at a glance

Featuredbt Corewritexl
SectorAnalyticsAnalytics
Velocity score6.36.3
Sparks · 30d01
Top themesanalytics-engineering, dbt-fusion, adapters, clickhousexlsx, libxlsxwriter, cell-formatting, major-version
Last editorial update15h ago6d 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 writexl?

writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.

For most of its history writexl was a deliberately minimal wrapper: bump the vendored libxlsxwriter, handle NA and Date coercion correctly, support a list of data frames for multiple sheets, and nothing else. 2.0.0, released August 2026, changes that — near-full libxlsxwriter coverage, cell/worksheet/workbook formatting, cell comments, an `xl_cell_general` class carrying value, formula and hyperlink, a cell-by-cell refactor, libxlsxwriter 1.2.4, and memory-safety work. It landed the same day as 1.5.4, a typo fix on the old line.

Read the full writexl trajectory →

dbt Core vs writexl: 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.

W
writexl
ANALYTICS
6.3

writexl spent nine years refusing to do formatting, then shipped all of it in 2.0.0.

◆ Current state

For most of its history writexl was a deliberately minimal wrapper: bump the vendored libxlsxwriter, handle NA and Date coercion correctly, support a list of data frames for multiple sheets, and nothing else. 2.0.0, released August 2026, changes that — near-full libxlsxwriter coverage, cell/worksheet/workbook formatting, cell comments, an `xl_cell_general` class carrying value, formula and hyperlink, a cell-by-cell refactor, libxlsxwriter 1.2.4, and memory-safety work. It landed the same day as 1.5.4, a typo fix on the old line.

◆ Where it's heading

The package has changed category. Its selling point was being the dependency-free, opinion-free way to get a data frame into xlsx; 2.0.0 makes it a formatting-capable writer that now compares itself against openxlsx2 in its own test suite. The cell-by-cell refactor is what made that possible and is also the largest structural change in the package's history. Note that a single contributor drove essentially all of it.

◆ Prediction

Expect follow-up releases fixing edge cases in the new formatting and comment APIs — the cell-by-cell rewrite is too large to land clean, and the 2.0.0 notes already mention an off-by-one in date columns.

Alternatives to dbt Core and writexl

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 writexl.

See all dbt Core alternatives → · See all writexl alternatives →

Recent activity from dbt Core and writexl

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. 14d agowritexlwritexl 2.0.0 adds formatting, comments and full libxlsxwriter coverage
  8. 14d agowritexlwritexl 1.5.4 fixes a documentation typo
  9. 5y agowritexlwritexl 1.4.0 updates libxlsxwriter to 1.0.3
  10. 6y agowritexlwritexl 1.2 fixes NA in formulas and hyperlinks
  11. 7y agowritexlwritexl 1.1 fixes NA strings and bit64 coercion
  12. 8y agowritexlwritexl 1.0 writes Date values as datetimes

Frequently asked questions

What is the difference between dbt Core and writexl?

They serve adjacent needs but don't currently overlap on shipped themes. dbt Core and writexl are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 writexl?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core and writexl are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 writexl?

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