Tinybird
Tinybird closes out Classic migration, makes JSON native by default, and adds MCP query plan inspection — a strong three-week sprint.
A side-by-side editorial comparison of dbt Core and Delta Lake — release velocity, themes, recent moves, and the top alternatives to consider.
dbt 2.0 ships stable with an official OSS/proprietary split and agentic skill loading
dbt shipped its 2.0 stable release on September 16, the first generational version milestone in the project's history. The release formally renames the CLI: what was 'Fusion/dbt-core' becomes 'dbt' (proprietary) and 'dbt-oss' (open source)—a structural separation that existed in practice but now has an official name. New capabilities include native Databricks metric view materializations, a ClickHouse ADBC driver, and AgentSkill installation from dbt packages gated on a new ai_provider flag.
Delta Lake runs parallel 3.x and 4.x maintenance tracks while 4.4.0 release prep lands
Delta Lake is operating in dual-track maintenance mode: the 3.3.x line is receiving backported correctness fixes covering transaction log retention, deletion vector caching in Delta Sharing, and S3 key randomization, while the 4.x line is consolidating toward a 4.4.0 release. The changelog is heavily diluted by automated DBR kernel build entries that carry no user-visible change. Real signal remains sparse but targeted — each numbered patch release addresses specific production failure modes rather than adding surface area.
dbt shipped its 2.0 stable release on September 16, the first generational version milestone in the project's history. The release formally renames the CLI: what was 'Fusion/dbt-core' becomes 'dbt' (proprietary) and 'dbt-oss' (open source)—a structural separation that existed in practice but now has an official name. New capabilities include native Databricks metric view materializations, a ClickHouse ADBC driver, and AgentSkill installation from dbt packages gated on a new ai_provider flag.
The OSS/proprietary split is the architectural move that matters most. dbt Labs is building a commercial product on top of dbt-oss, and 2.0 makes that boundary explicit to the ecosystem. The AgentSkills integration signals that dbt sees AI-assisted data transformation as a core product direction—not an add-on. The ai_provider flag is the gating mechanism through which commercial features will increasingly be differentiated.
Expect near-term differentiation between dbt (proprietary) and dbt-oss at the feature level, with AI-native capabilities—AgentSkills, model suggestions, lineage intelligence—landing exclusively in the commercial tier first.
Delta Lake is operating in dual-track maintenance mode: the 3.3.x line is receiving backported correctness fixes covering transaction log retention, deletion vector caching in Delta Sharing, and S3 key randomization, while the 4.x line is consolidating toward a 4.4.0 release. The changelog is heavily diluted by automated DBR kernel build entries that carry no user-visible change. Real signal remains sparse but targeted — each numbered patch release addresses specific production failure modes rather than adding surface area.
The project is converging on the 4.4.0 milestone, with the version-bump prep PR already merged. The 4.x line is hardening around Apache Spark 4.x compatibility, Unity Catalog integration, and the delta-connect stack, while 3.3.x continues receiving correctness backports for the substantial user base still on Spark 3. The dual-track cadence reflects an ecosystem split between legacy Spark 3 deployments and teams actively migrating to Spark 4.
A 4.4.0 full release with complete changelog is imminent — the version prep PR has merged and the tag is queued. Expect continued DBR build noise alongside it, and likely a 3.3.4 patch if additional regressions surface from the 3.3.3 correctness fixes.
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 Delta Lake.
Tinybird closes out Classic migration, makes JSON native by default, and adds MCP query plan inspection — a strong three-week sprint.
OpenHouse adds a post-commit operations framework and starts building Iceberg view support.
Lightdash cuts the dbt cord and lets users describe custom chart types in plain language — two directional moves in one week.
OpenCTI adopts a FIPS 140-3 validated base image — a quiet signal the platform is targeting federal and defense buyers.
OpenObserve v1.0 GA ships a full AI Observability platform for LLM and agent workloads — the category bet is official.
TimescaleDB 2.30.0 ships DeferredChunkAppend, cutting last-point query cost from O(n chunks) to O(1)
See all dbt Core alternatives → · See all Delta Lake 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 7.5 vs 5.0), with 1 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 7.5 vs 5.0), with 1 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 Delta Lake alternatives in Analytics are ranked by recent ship velocity. Browse the "Delta Lake alternatives" section above for the current picks, or visit /alternatives/delta-lake for the full list with editorial commentary on each.