AgencyAnalytics
AgencyAI got skills three weeks ago; everything since has been making them routine.
A side-by-side editorial comparison of NocoDB and rredlist — 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.
rredlist threw out its species-centric API in 1.0.0 and rebuilt around assessments.
rredlist 1.0.0 is a hard break: the IUCN Red List API moved to v4, and the package followed by dropping v3 support entirely, reorganising around assessments rather than species, renaming or removing most functions, changing returned data structures, and requiring users to generate a new API key. The two releases since are consolidation on that new shape — `rl_assessment_list()` and `rl_assessment_extract()` for retrieving and unpacking many assessments at once, a `scope` argument on the `*_latest()` functions, and NULL-safe extraction.
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.
rredlist 1.0.0 is a hard break: the IUCN Red List API moved to v4, and the package followed by dropping v3 support entirely, reorganising around assessments rather than species, renaming or removing most functions, changing returned data structures, and requiring users to generate a new API key. The two releases since are consolidation on that new shape — `rl_assessment_list()` and `rl_assessment_extract()` for retrieving and unpacking many assessments at once, a `scope` argument on the `*_latest()` functions, and NULL-safe extraction.
Post-1.0.0 work is clearly aimed at bulk use: fetch many assessments, pull a chosen field out of each. That is a different usage pattern from the one-species-at-a-time queries the v3-era functions encouraged, and it suits the conservation-analysis workloads the package is actually used for. Deprecated v3 functions are still present and flagged for eventual removal.
The deprecated v3-era functions are the obvious next thing to disappear, and further bulk-retrieval helpers are likely given both post-1.0 releases went that way.
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 rredlist.
AgencyAI got skills three weeks ago; everything since has been making them routine.
RecoveryManager Plus keeps widening its backup coverage across the Microsoft identity estate.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
See all NocoDB alternatives → · See all rredlist 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 rredlist alternatives in Analytics are ranked by recent ship velocity. Browse the "rredlist alternatives" section above for the current picks, or visit /alternatives/rredlist for the full list with editorial commentary on each.