Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
Comparison · Analytics
gratia vs NocoDB
A side-by-side editorial comparison of gratia and NocoDB — release velocity, themes, recent moves, and the top alternatives to consider.
gratia vs NocoDB: at a glance
What is gratia?
The tidy front-end for GAMs, now stable enough that upstream ggplot2 sets its release calendar.
gratia wraps mgcv-fitted generalized additive models in tidy data frames and ggplot2 graphics — smooth_estimates(), fitted_values(), derivatives(), draw() and appraise() cover evaluation, prediction and diagnostics. The API reached its intended shape at 0.9.0, when every generated column was renamed to a dot-prefixed form, and 0.10.0 added conditional_values() for covariate-conditional prediction plots.
What is NocoDB?
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.
gratia vs NocoDB: editorial side-by-side
gratia
0.0ANALYTICS
The tidy front-end for GAMs, now stable enough that upstream ggplot2 sets its release calendar.
◆ Current state
gratia wraps mgcv-fitted generalized additive models in tidy data frames and ggplot2 graphics — smooth_estimates(), fitted_values(), derivatives(), draw() and appraise() cover evaluation, prediction and diagnostics. The API reached its intended shape at 0.9.0, when every generated column was renamed to a dot-prefixed form, and 0.10.0 added conditional_values() for covariate-conditional prediction plots.
◆ Where it's heading
The package has moved through a long rewrite cycle and out the other side. Successive releases replaced evaluate_smooth() with smooth_estimates(), rebuilt draw() on top of it, then renamed the entire output vocabulary to avoid colliding with user variables. That work is finished; 0.11.1 is driven almost entirely by ggplot2 4.0.0 compatibility, with new mgcv family support for quantile residuals riding along. Development now tracks upstream breakage rather than internal redesign.
◆ Prediction
Expect the next releases to continue absorbing ggplot2 4.x and mgcv changes, with incremental family coverage in quantile_residuals() as the visible new work. The entries give no signal on which mgcv families come next.
NocoDB
6.3ANALYTICS
Interfaces gets the permissions layer it needed, one release after launching.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to gratia and NocoDB
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 gratia or NocoDB.
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all gratia alternatives → · See all NocoDB alternatives →
Recent activity from gratia and NocoDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 14h agoNocoDB2026.08.1 : Introducing Realtime Presence and Folders
- 14d agoNocoDB2026.08.0 : Introducing Interfaces ⚡
- 1mo agoNocoDB2026.07.0 : Introducing Calendar Sync & Image Annotations
- 1mo agoNocoDB2026.06.2 : Introducing Oracle Database Support
- 2mo agoNocoDB2026.06.1: tsgo typechecking and rspack bump
- 2mo agoNocoDB2026.06.0: Bounded group-by fetch retries
- 11mo agogratiaggplot2 4.0.0 compatibility, plus four more quantile-residual families
- 1y agogratiaconditional_values() replaces vis.gam for conditional prediction plots
- 2y agogratiaparametric_effects() joins the dot-prefix rename; LSS families begin
- 2y agogratiaEvery generated column gains a dot prefix ⚡
- 3y agogratiaReal variable names in smooth_samples(), plus dplyr 1.1.0 fixes
- 4y agogratiaM1 example output fixes and confint tibble returns
Frequently asked questions
What is the difference between gratia and NocoDB?
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.
Is gratia better than NocoDB?
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.
What are the best alternatives to gratia?
Top gratia alternatives in Analytics are ranked by recent ship velocity. Browse the "gratia alternatives" section above for the current picks, or visit /alternatives/gratia for the full list with editorial commentary on each.
What are the best alternatives to NocoDB?
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.