Dovetail
Channels stops labelling themes and starts tracking owned, priced-up ideas.
A side-by-side editorial comparison of dbt Core and Stitch — release velocity, themes, recent moves, and the top alternatives to consider.
Fusion's 2.0 train has become adapter work: Exasol from scratch, ClickHouse toward parity.
dbt-core is running two lines at once. The 2.0 Fusion train ships near-daily dev tags whose notes are dominated by adapter surface — an Exasol adapter built from nothing, ClickHouse being pulled up to what the Python adapter already does, and Databricks configuration filling in. The 1.x Python line, meanwhile, receives only backports: an Azure Blob artifact-upload fix and a sqlparse CVE pin, nothing else.
Stitch is running a fleet-wide Python 3.12 migration across its connector estate.
Stitch's changelog is a per-connector maintenance log, and August is dominated by one coordinated effort: moving integrations to Python 3.12, visible across Amplitude, Salesforce Marketing Cloud, SaaSOptics, AppsFlyer, Pipedrive and Google Analytics 360 inside a single week. Around it sit library bumps, metadata corrections, and a handful of genuine reliability fixes concentrated in Shopify (v3) and LinkedIn Ads (v2). The one connector to gain real capability is Workday RaaS, which picked up OAuth 2.0 and incremental sync on August 14.
dbt-core is running two lines at once. The 2.0 Fusion train ships near-daily dev tags whose notes are dominated by adapter surface — an Exasol adapter built from nothing, ClickHouse being pulled up to what the Python adapter already does, and Databricks configuration filling in. The 1.x Python line, meanwhile, receives only backports: an Azure Blob artifact-upload fix and a sqlparse CVE pin, nothing else.
The recurring theme across dev.30, dev.33 and beta.2 is not new capability but acceptance: Fusion learning to take the config shapes dbt Core tolerates, ClickHouse incremental strategies resolving exactly like their Python counterparts, contracts and constraints enforced end-to-end. That is a rewrite closing the gap with the thing it replaces. The 1.x releases read as a maintenance line kept alive on security patches while attention sits on 2.0.
Expect the dev tags to keep grinding through adapter parity — ClickHouse projections and codec are named in the notes as available but not working yet, which is the next obvious box to tick. The 1.x branches will likely see only dependency and CVE releases.
Stitch's changelog is a per-connector maintenance log, and August is dominated by one coordinated effort: moving integrations to Python 3.12, visible across Amplitude, Salesforce Marketing Cloud, SaaSOptics, AppsFlyer, Pipedrive and Google Analytics 360 inside a single week. Around it sit library bumps, metadata corrections, and a handful of genuine reliability fixes concentrated in Shopify (v3) and LinkedIn Ads (v2). The one connector to gain real capability is Workday RaaS, which picked up OAuth 2.0 and incremental sync on August 14.
This is an estate being maintained rather than a product being developed. The work divides into three streams: a runtime migration moving connectors off older Python, correctness fixes where a source API changed shape, such as Shopify metafields serialized to JSON strings and LinkedIn Ads discovery returning 404s on inaccessible accounts, and incremental hardening like token refresh on 401 during Shopify bulk polling. Nothing in this window changes what Stitch is or how it is used. The value being defended is that a long tail of connectors keeps working.
Expect the Python 3.12 sweep to continue through the remaining connectors, and further Shopify (v3) work, since two of its three entries this month address failures in bulk operation handling. Whether Workday's OAuth and incremental sync becomes a template for other v1 connectors is not yet visible in the feed.
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 Stitch.
Channels stops labelling themes and starts tracking owned, priced-up ideas.
Chord is turning its analytics assistant into something with memory, and now feeding it more sources
Datawrapper ships one small fix at a time, each named for the chart it touches
After a summer fencing in its AI layer, Holistics points it at the question analysts get asked most.
Reporting tool turning itself into the place agencies prove AI visibility to clients
Neo4j gives away graph analytics, then builds out the language and console around it.
See all dbt Core alternatives → · See all Stitch 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 5.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 5.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 Stitch alternatives in Analytics are ranked by recent ship velocity. Browse the "Stitch alternatives" section above for the current picks, or visit /alternatives/stitchdata for the full list with editorial commentary on each.