← Back to home
Comparison · Analytics

dbt Core vs dvir

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

dbt Core vs dvir: at a glance

Featuredbt Coredvir
SectorAnalyticsAnalytics
Velocity score6.30.0
Sparks · 30d00
Top themesanalytics-engineering, dbt-fusion, adapters, clickhouseforensic genetics, victim identification, pipeline, scalability
Last editorial update3h ago3d 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 dvir?

dvir keeps making disaster victim identification a single call instead of a workflow.

dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.

Read the full dvir trajectory →

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

D
dvir
ANALYTICS
0.0

dvir keeps making disaster victim identification a single call instead of a workflow.

◆ Current state

dvir handles disaster victim identification: matching unidentified remains against reference families using pedigree likelihoods. The package has consolidated around dviSolve(), a complete pipeline introduced in 3.2.1 and rewritten in 3.3.0 to use generalised likelihood ratios for families with several missing persons. Recent releases have been about making that pipeline survive large cases, adding dviGridSize() and a maxAssign cutoff to skip joint analysis when the combination count explodes, plus per-step timings.

◆ Where it's heading

The arc is from a toolbox of functions toward one supervised pipeline, with the older jointDVI() now emitting a legacy message. The current constraint is combinatorial: joint analysis over many victims and missing persons blows up, so the work has gone to measuring the blowup and bailing out of it. Parallelism is mid-migration, with the parallel and pbapply implementation removed and a mirai replacement stated as planned but not yet shipped, leaving numCores accepted and ignored with a warning.

◆ Prediction

The mirai-based parallelisation is announced as coming, so expect it next, most likely applied to the joint analysis step that maxAssign currently exists to avoid.

Alternatives to dbt Core and dvir

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

See all dbt Core alternatives → · See all dvir alternatives →

Recent activity from dbt Core and dvir

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

  1. 1d agodbt CoreFusion beta.2 fills in ClickHouse materializations and catalogs
  2. 5d agodbt Coredbt 1.2.7 backports the deprecated-version warning and old fixes
  3. 5d agodbt Coredbt 1.1.6 backports the deprecated-version warning and old fixes
  4. 5d agodbt Coredbt 1.3.8 backports the deprecated-version warning
  5. 5d agodbt Coredbt 1.4.10 drops Python 3.8 and warns on deprecated versions
  6. 5d agodbt Coredbt 1.5.12 drops Python 3.8 and warns on deprecated versions
  7. 1mo agodvirCombination sizing and a cutoff for joint analysis
  8. 3mo agodvirJoint tables added to solver output
  9. 3mo agodvirVictim and database accessors, plus solver refinements
  10. 1y agodvirSolver rewritten around generalised likelihood ratios
  11. 2y agodvirdviSolve() pipeline and manual pairing controls
  12. 2y agodvirMaintainer handover and small reporting additions

Frequently asked questions

What is the difference between dbt Core and dvir?

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 dvir?

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 dvir?

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