Dovetail
Channels stops labelling themes and starts tracking owned, priced-up ideas.
A side-by-side editorial comparison of dbt Core and Keboola — 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.
Keboola is smoothing the seams — MCP login, direct workspace writes, and BigQuery catching up to Snowflake
Keboola's August work is concentrated on removing intermediate steps. The MCP server swapped pasted Storage API tokens for a one-time browser login that reaches every project on a stack, workspaces write straight into Storage without an output-mapping job, and branched storage arrives on BigQuery to match Snowflake. Alongside that sits a run of runtime and authentication deprecations with hard dates.
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.
Keboola's August work is concentrated on removing intermediate steps. The MCP server swapped pasted Storage API tokens for a one-time browser login that reaches every project on a stack, workspaces write straight into Storage without an output-mapping job, and branched storage arrives on BigQuery to match Snowflake. Alongside that sits a run of runtime and authentication deprecations with hard dates.
Two threads run in parallel: making the assistant and workspace surfaces less ceremonious, and dragging the BigQuery backend to parity with Snowflake ahead of Branches 2.0. The deprecation notices — Python 3.10, Snowflake password auth — suggest a platform clearing old ground before the next structural release.
Branches 2.0 with approval workflows and conflict resolution is the next substantial release, and it should land once BigQuery parity work is finished.
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 Keboola.
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
Stitch is running a fleet-wide Python 3.12 migration across its connector estate.
See all dbt Core alternatives → · See all Keboola 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 Keboola alternatives in Analytics are ranked by recent ship velocity. Browse the "Keboola alternatives" section above for the current picks, or visit /alternatives/keboola for the full list with editorial commentary on each.