Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
A side-by-side editorial comparison of dbt Core and dvir — release velocity, themes, recent moves, and the top alternatives to consider.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Interfaces gets the permissions layer it needed, one release after launching.
See all dbt Core alternatives → · See all dvir alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
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.
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.
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.
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.