Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of NocoDB and weird — release velocity, themes, recent moves, and the top alternatives to consider.
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.
weird rebuilt itself on distributional objects, and now the anomaly tooling composes with everything else.
An R package for anomaly detection and unusual-observation diagnostics, at four releases with a long gap between the 2024 patch and the 2026 major line. The current shape is set by 2.0.0, which refactored the package onto distributional objects and renamed its central concept from density_scores() to surprisals(). Since then the work has been filling that structure in: surprisals for more model classes, faster bandwidth and probability calculations, and new visual diagnostics.
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.
An R package for anomaly detection and unusual-observation diagnostics, at four releases with a long gap between the 2024 patch and the 2026 major line. The current shape is set by 2.0.0, which refactored the package onto distributional objects and renamed its central concept from density_scores() to surprisals(). Since then the work has been filling that structure in: surprisals for more model classes, faster bandwidth and probability calculations, and new visual diagnostics.
The refactor onto a shared distribution representation is the decision everything else follows from. It let 2.1.0 add hdr() and parameters() methods for kde objects rather than bespoke accessors, and it let 3.0.0 bring in dist_mclust() to turn a Gaussian mixture model into the same object type — so a mixture, a kernel density estimate and a fitted distribution all flow through one interface. The 3.0.0 additions lean visual and multivariate: outlier maps plotting score distance against orthogonal distance, biplot projections with variable axes overlaid, and an augment() method for robust PCA objects. Dependencies have been shed steadily along the way — lookout, interpolation — while mvscale() moved out and then back in.
Expect surprisals() coverage to keep extending to further model classes, and the multivariate and robust-PCA diagnostics introduced in 3.0.0 to gain the same distributional-object treatment as the univariate side.
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 NocoDB or weird.
Basedash keeps pushing its data out of the workspace — now to people without accounts
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 NocoDB alternatives → · See all weird 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 0.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 0.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 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.
Top weird alternatives in Analytics are ranked by recent ship velocity. Browse the "weird alternatives" section above for the current picks, or visit /alternatives/weird-r for the full list with editorial commentary on each.