dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of Delta Lake and NocoDB — release velocity, themes, recent moves, and the top alternatives to consider.
Delta Lake's public releases are patch work while Databricks kernel builds fill the feed.
Two kinds of entry dominate: numbered patch releases on the 3.3 and 4.3 lines, and near-daily Databricks kernel build tags that carry a single commit message each. The patch releases are targeted correctness work — a metadata cleanup that could delete transaction log files still needed to reconstruct versions inside the retention window, a Delta Sharing cache refresh that dropped deletion-vector URL mappings, an OAuth key-casing bug in the REST Catalog, and S3A fast-listing through FilterFileSystem wrappers. The 3.3.3 release also declines to publish delta-iceberg, leaving UniForm users on the prior patch.
Interfaces gets the permissions layer it needed, one release after launching.
NocoDB ships monthly, and the last two releases are a launch and its follow-through. 2026.08.0 introduced Interfaces, custom app surfaces built over a base; 2026.08.1 gives that layer what it was missing — per-dashboard visibility and editing permissions, field edit permissions enforced on interface pages, team-granted access, and page reordering. Alongside it the grid gains realtime presence with per-collaborator colours and jump-to-cursor, folders for grouping tables and views, up to three frozen fields, and nested records in List View.
Two kinds of entry dominate: numbered patch releases on the 3.3 and 4.3 lines, and near-daily Databricks kernel build tags that carry a single commit message each. The patch releases are targeted correctness work — a metadata cleanup that could delete transaction log files still needed to reconstruct versions inside the retention window, a Delta Sharing cache refresh that dropped deletion-vector URL mappings, an OAuth key-casing bug in the REST Catalog, and S3A fast-listing through FilterFileSystem wrappers. The 3.3.3 release also declines to publish delta-iceberg, leaving UniForm users on the prior patch.
The project is stabilising two supported lines in parallel rather than moving the format forward in these entries, and the recurring theme is metadata and log durability — the parts of Delta that silently break time travel and CDF when they are wrong. Kernel work continues in the build tags, most visibly treating _last_checkpoint as opaque JSON. The unpublished UniForm artifact is the one open thread with a stated follow-up plan.
A follow-up patch that restores the delta-iceberg artifact for the 3.3 line is the clearest next step; otherwise expect the kernel build cadence to continue between numbered releases.
NocoDB ships monthly, and the last two releases are a launch and its follow-through. 2026.08.0 introduced Interfaces, custom app surfaces built over a base; 2026.08.1 gives that layer what it was missing — per-dashboard visibility and editing permissions, field edit permissions enforced on interface pages, team-granted access, and page reordering. Alongside it the grid gains realtime presence with per-collaborator colours and jump-to-cursor, folders for grouping tables and views, up to three frozen fields, and nested records in List View.
The pattern is consistent: NocoDB launches a surface, then spends the next release making it governable and usable at team scale. Presence and folders are collaboration parity rather than new direction — the directional bet was Interfaces, and this release is that bet being made safe for the eighty people who only need to approve something. The permission system is now the same one across tables, fields, dashboards, and interface pages, which is the consolidation that makes the app layer sellable.
Write-back actions and embedding are the remaining pieces app builders expect from Interfaces, and the availability tables in each release suggest they land on the paid tier.
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 Delta Lake or NocoDB.
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
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.
See all Delta Lake alternatives → · See all NocoDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NocoDB is currently shipping more aggressively (velocity 6.3 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. NocoDB is currently shipping more aggressively (velocity 6.3 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 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.
Top NocoDB alternatives in Analytics are ranked by recent ship velocity. Browse the "NocoDB alternatives" section above for the current picks, or visit /alternatives/nocodb for the full list with editorial commentary on each.