← Back to home
Comparison · Analytics

dcurves vs NocoDB

A side-by-side editorial comparison of dcurves and NocoDB — release velocity, themes, recent moves, and the top alternatives to consider.

dcurves vs NocoDB: at a glance

FeaturedcurvesNocoDB
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themesclinical-prediction, decision-analysis, net-benefit, biostatisticsno-code-database, interfaces, permissions, realtime-collaboration
Last editorial update2d ago55m ago
WebsiteVisit →Visit →

What is dcurves?

Decision curve analysis, settled since 2022 and now moving only when its neighbours do

dcurves implements decision curve analysis — evaluating a prediction model or diagnostic test by net benefit across the range of thresholds a clinician might plausibly use, rather than by a single discrimination statistic. Its API stabilised in 2022 around dca() and test_consequences(). The two releases since exist because gtsummary and CRAN documentation rules changed, not because the method did.

Read the full dcurves trajectory →

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.

Read the full NocoDB trajectory →

dcurves vs NocoDB: editorial side-by-side

D
dcurves
ANALYTICS
0.0

Decision curve analysis, settled since 2022 and now moving only when its neighbours do

◆ Current state

dcurves implements decision curve analysis — evaluating a prediction model or diagnostic test by net benefit across the range of thresholds a clinician might plausibly use, rather than by a single discrimination statistic. Its API stabilised in 2022 around dca() and test_consequences(). The two releases since exist because gtsummary and CRAN documentation rules changed, not because the method did.

◆ Where it's heading

The package reached its intended scope quickly and then stopped. Its 2022 releases did the substantive work: adding threshold-level diagnostic accuracy, tightening argument validation, and taking one breaking change to make net-interventions-avoided plots show the treat-all and treat-none reference lines by default. Since then it has moved only as a dependent of the wider tidy-modelling documentation ecosystem it plugs into.

◆ Prediction

Nothing in these entries points to method or API work; expect the next release to be another compatibility or CRAN documentation patch.

N
NocoDB
ANALYTICS
6.3

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 dcurves 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 dcurves or NocoDB.

See all dcurves alternatives → · See all NocoDB alternatives →

Recent activity from dcurves and NocoDB

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2h agoNocoDB2026.08.1 : Introducing Realtime Presence and Folders
  2. 14d agoNocoDB2026.08.0 : Introducing Interfaces
  3. 1mo agoNocoDB2026.07.0 : Introducing Calendar Sync & Image Annotations
  4. 1mo agoNocoDB2026.06.2 : Introducing Oracle Database Support
  5. 2mo agoNocoDB2026.06.1: tsgo typechecking and rspack bump
  6. 2mo agoNocoDB2026.06.0: Bounded group-by fetch retries
  7. 9mo agodcurvesHTML5 documentation rebuild for CRAN
  8. 2y agodcurvesbroom.helpers added to Suggests for gtsummary 2.0
  9. 3y agodcurvesNet interventions plots now show treat-all and treat-none by default
  10. 4y agodcurvestest_consequences() reports accuracy across thresholds

Frequently asked questions

What is the difference between dcurves 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 dcurves 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 dcurves?

Top dcurves alternatives in Analytics are ranked by recent ship velocity. Browse the "dcurves alternatives" section above for the current picks, or visit /alternatives/dcurves 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.