distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
A side-by-side editorial comparison of Basedash and Delta Lake — release velocity, themes, recent moves, and the top alternatives to consider.
Basedash keeps pushing its data out of the workspace — now to people without accounts
Basedash is a BI tool built around an AI data analyst, and the last month has been about getting its output to more places: an API that exposes chat, insights, automations and dashboards; scheduled snapshots to email and Slack; and now a link that opens a live, filterable dashboard for someone with no Basedash account. Alongside that distribution work sits a research-preview agent, Tasks, that reads company data and produces a ranked to-do list. Audit logs, including a record of every query the AI runs, arrived in the same window.
A 4.4.0 tag appears, but the feed carries only its release plumbing
The newest entry is the commit that tagged 4.4.0 — a version.sbt bump plus a local Maven overwrite setting needed for cross-Spark publishing, and it states outright that there are no runtime behaviour changes. The 4.4.0 release notes themselves have not reached this feed, so what the minor version actually contains is not readable here. Behind it sit two patch releases doing targeted correctness work: 3.3.3 on transaction log retention and Delta Sharing cache, 4.3.1 on Delta REST Catalog OAuth and S3A listing, interleaved with near-daily Databricks kernel build tags.
Basedash is a BI tool built around an AI data analyst, and the last month has been about getting its output to more places: an API that exposes chat, insights, automations and dashboards; scheduled snapshots to email and Slack; and now a link that opens a live, filterable dashboard for someone with no Basedash account. Alongside that distribution work sits a research-preview agent, Tasks, that reads company data and produces a ranked to-do list. Audit logs, including a record of every query the AI runs, arrived in the same window.
Two arcs are running in parallel. One narrows the gap between viewing data and acting on it — suggestions before you type a prompt, then Tasks writing the work item and tracking whether the metric moved. The other decouples consumption from seats: API, subscriptions, and public links each reach an audience that never logs in. The interface work (module-anchored sidebar, per-user table sorting that doesn't rewrite the author's SQL) reads as load-bearing for both.
Tasks leaving research preview is the release that decides how much of this is real; its value depends entirely on the outcome-tracking loop having run long enough to show whether its recommendations worked. Expect the sharing surface to grow permissions and expiry controls next, since a link that works without an account is the first place governance pressure lands.
The newest entry is the commit that tagged 4.4.0 — a version.sbt bump plus a local Maven overwrite setting needed for cross-Spark publishing, and it states outright that there are no runtime behaviour changes. The 4.4.0 release notes themselves have not reached this feed, so what the minor version actually contains is not readable here. Behind it sit two patch releases doing targeted correctness work: 3.3.3 on transaction log retention and Delta Sharing cache, 4.3.1 on Delta REST Catalog OAuth and S3A listing, interleaved with near-daily Databricks kernel build tags.
The project keeps two supported lines stable in parallel while the format work happens elsewhere, and the durable theme across these patches is metadata and log correctness — the failures that silently break time travel and CDF rather than throwing. The 4.4.0 prep notes one thing worth watching: artifacts are now published across Spark 4.0, 4.1 and 4.2 stages, so the cross-Spark support matrix is widening even as the release content stays out of view.
The 4.4.0 release notes should follow this tag and reveal what the minor version carries; until they do the entries support no read on its direction. The unresolved delta-iceberg artifact gap on the 3.3 line still has no follow-up here.
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 Basedash or Delta Lake.
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
RStudio ships through release branches, and the notes are commit messages
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.
See all Basedash 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. Basedash 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. Basedash 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 Basedash alternatives in Analytics are ranked by recent ship velocity. Browse the "Basedash alternatives" section above for the current picks, or visit /alternatives/basedash 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.