dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of NocoDB and robma — 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.
RoBMA 4.0 tears out its own constructor surface and rebuilds on one class hierarchy
RoBMA fits robust Bayesian model-averaged meta-analyses that adjust for publication bias. The 3.x line grew by accretion: separate constructors for each model family (RoBMA.reg, NoBMA, BiBMA and their .reg variants), a spike-and-slab algorithm in 3.3.0 that made estimation fast enough to matter, then a steady stream of post-estimation tooling gated on that algorithm — heterogeneity summaries, residuals, funnel plots, z-curve conversion, predict, extract, pooled and adjusted effects. Version 4.0.0 in May 2026 collapses all of it into a unified brma class hierarchy.
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.
RoBMA fits robust Bayesian model-averaged meta-analyses that adjust for publication bias. The 3.x line grew by accretion: separate constructors for each model family (RoBMA.reg, NoBMA, BiBMA and their .reg variants), a spike-and-slab algorithm in 3.3.0 that made estimation fast enough to matter, then a steady stream of post-estimation tooling gated on that algorithm — heterogeneity summaries, residuals, funnel plots, z-curve conversion, predict, extract, pooled and adjusted effects. Version 4.0.0 in May 2026 collapses all of it into a unified brma class hierarchy.
The 3.x series solved the modeling problem and left an interface problem behind: a caller had to know which of six constructors matched their data type, and argument names differed across them. 4.0.0 resolves that by making the model family a set of arguments rather than a function name, and by standardizing input naming on metafor-style conventions. It shipped one day after BayesTools 0.3.0, the author's own upstream infrastructure package, whose new standardization and prior-transformation machinery this rewrite depends on.
A rewrite this wide usually needs a follow-up, so expect 4.0.x patches addressing migration gaps as users hit the removed constructors and renamed arguments.
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 robma.
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 NocoDB alternatives → · See all robma 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 robma alternatives in Analytics are ranked by recent ship velocity. Browse the "robma alternatives" section above for the current picks, or visit /alternatives/robma for the full list with editorial commentary on each.