Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of delaporte and NocoDB — release velocity, themes, recent moves, and the top alternatives to consider.
A Fortran-backed Delaporte distribution package where every release is compiler and CRAN weather.
Delaporte supplies the density, distribution, quantile and random-generation functions for the Delaporte distribution — a Poisson-negative-binomial convolution used for overdispersed count data — implemented in Fortran and called through C. The only user-facing addition in the visible history is explicit OpenMP thread control via getDelapThreads() and setDelapThreads() at 8.2.0.
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.
Delaporte supplies the density, distribution, quantile and random-generation functions for the Delaporte distribution — a Poisson-negative-binomial convolution used for overdispersed count data — implemented in Fortran and called through C. The only user-facing addition in the visible history is explicit OpenMP thread control via getDelapThreads() and setDelapThreads() at 8.2.0.
The maintenance burden here is portability, not statistics. Recent entries track a Fortran suffix change for Intel compiler compatibility, architecture-specific test tolerances, type-safety corrections on values crossing the C-to-Fortran boundary, and a thread-count variable relocated from R options to an environment variable to follow an upstream R commit. The distribution functions themselves are settled; what changes is how the compiled code is built and checked across CRAN's platform matrix.
Expect the next release to follow another CRAN toolchain or Writing R Extensions policy change, as the last several have. Two of the four visible entries carry no notes at all, so this feed will keep understating what actually shipped.
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.
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 delaporte or NocoDB.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
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
See all delaporte alternatives → · See all NocoDB 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 delaporte alternatives in Analytics are ranked by recent ship velocity. Browse the "delaporte alternatives" section above for the current picks, or visit /alternatives/delaporte for the full list with editorial commentary on each.
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.