dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Comparison · Analytics
NocoDB vs rATTAINS
A side-by-side editorial comparison of NocoDB and rATTAINS — release velocity, themes, recent moves, and the top alternatives to consider.
NocoDB vs rATTAINS: at a glance
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.
What is rATTAINS?
The R client for EPA water quality data spent two releases undoing its own promises about data shape.
rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.
NocoDB vs rATTAINS: editorial side-by-side
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.
rATTAINS
0.0ANALYTICS
The R client for EPA water quality data spent two releases undoing its own promises about data shape.
◆ Current state
rATTAINS wraps the EPA's ATTAINS API, which holds state water quality assessments and impaired-waters listings. The package reached 1.0.0 by promising stable, consistently rectangled return structures, then walked that promise back in 1.1.0 when it dropped the dependency doing the rectangling. As of 1.2.0 it also requires an API key, because ATTAINS itself began requiring one in May 2026.
◆ Where it's heading
The direction is toward a thinner, lower-maintenance wrapper. Caching went in 0.1.4 when hoardr was archived, tidyjson and janitor went earlier, tibblify went in 1.1.0, and each removal handed a little more data-shaping responsibility back to the user — the current advice is to pass .unnest = FALSE and rectangle the results with whatever tidying package you prefer. Release cadence is slow and mostly reactive: upstream API terms, archived dependencies, and compatibility with test tooling account for most of the log. The package's centre of gravity is staying installable and honest about what ATTAINS returns rather than smoothing it over.
◆ Prediction
Given the pattern, the next release is likelier to be a compatibility or upstream-driven fix than new endpoint coverage; how the API key requirement affects users in scripted and CI contexts is the obvious open question the entries do not yet answer.
Alternatives to NocoDB and rATTAINS
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 rATTAINS.
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.
tulpa
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAnalytics
AgencyAI got skills three weeks ago; everything since has been making them routine.
See all NocoDB alternatives → · See all rATTAINS alternatives →
Recent activity from NocoDB and rATTAINS
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13h agoNocoDB2026.08.1 : Introducing Realtime Presence and Folders
- 14d agoNocoDB2026.08.0 : Introducing Interfaces ⚡
- 1mo agoNocoDB2026.07.0 : Introducing Calendar Sync & Image Annotations
- 1mo agorATTAINSATTAINS now requires an API key, and the package follows
- 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
- 8mo agorATTAINSThe tibblify dependency goes, and with it the stable data shapes ⚡
- 1y agorATTAINSTest suite updated for vcr v2
- 3y agorATTAINS1.0.0 commits to stable return structures via tibblify
- 3y agorATTAINSCaching removed after hoardr was archived
- 4y agorATTAINSRequests retry on timeout, with offline detection
Frequently asked questions
What is the difference between NocoDB and rATTAINS?
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 NocoDB better than rATTAINS?
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 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.
What are the best alternatives to rATTAINS?
Top rATTAINS alternatives in Analytics are ranked by recent ship velocity. Browse the "rATTAINS alternatives" section above for the current picks, or visit /alternatives/rattains for the full list with editorial commentary on each.