← Back to home
Comparison · Analytics

NocoDB vs seriation

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

NocoDB vs seriation: at a glance

FeatureNocoDBseriation
SectorAnalyticsAnalytics
Velocity score6.30.0
Sparks · 30d10
Top themesno-code-database, interfaces, permissions, realtime-collaborationseriation, matrix-reordering, optimization, clustering
Last editorial update1h ago3d ago
WebsiteVisit →Visit →

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 →

What is seriation?

seriation stopped shipping algorithms and started shipping a way to pick between them.

seriation finds meaningful orderings for matrices, distance objects and dendrograms, and carries a large registry of methods from classic combinatorial criteria to t-SNE and UMAP embeddings. The 1.5.0 release added a layer above that registry — seriate_best(), seriate_rep() and seriate_improve() — which run randomized methods repeatedly, in parallel, and keep the best result. Recent work is definitional and numeric rather than additive: 1.5.8 corrects the linear seriation criterion to match Hubert and Schultz's original 1976 definition.

Read the full seriation trajectory →

NocoDB vs seriation: editorial side-by-side

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.

S
seriation
ANALYTICS
0.0

seriation stopped shipping algorithms and started shipping a way to pick between them.

◆ Current state

seriation finds meaningful orderings for matrices, distance objects and dendrograms, and carries a large registry of methods from classic combinatorial criteria to t-SNE and UMAP embeddings. The 1.5.0 release added a layer above that registry — seriate_best(), seriate_rep() and seriate_improve() — which run randomized methods repeatedly, in parallel, and keep the best result. Recent work is definitional and numeric rather than additive: 1.5.8 corrects the linear seriation criterion to match Hubert and Schultz's original 1976 definition.

◆ Where it's heading

The package has shifted from breadth to judgment. Through 1.3.x the additions were new methods; from 1.5.0 the registry started carrying metadata about the methods — whether they are randomized, what criterion they optimize — so the package could choose and evaluate on the user's behalf. The 1.5.6 replacement of FORTRAN with C for BEA and ME points the same way, reducing the legacy surface underneath that machinery.

◆ Prediction

Further criterion audits are the likeliest next move, since 1.5.8 shows a published definition being reconciled against the implementation and the registry now records what each method optimizes. Expect corrections rather than new seriation algorithms.

Alternatives to NocoDB and seriation

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 seriation.

See all NocoDB alternatives → · See all seriation alternatives →

Recent activity from NocoDB and seriation

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

  1. 3h 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. 0y agoseriationseriation 1.5.8 realigns linear criterion with Hubert and Schultz
  8. 1y agoseriationseriation 1.5.7 adds BK_unconstrained, handles tiny inputs
  9. 1y agoseriationseriation 1.5.6 replaces FORTRAN BEA with C, modernizes allocation
  10. 2y agoseriationseriation 1.5.5 digest: AOE method, rep parameter, MDS_angle fix
  11. 3y agoseriationseriation 1.5.1 refines pimage, permute and hmap
  12. 3y agoseriationseriation 1.5.0 adds seriate_best and parallel repeated search

Frequently asked questions

What is the difference between NocoDB and seriation?

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 seriation?

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 seriation?

Top seriation alternatives in Analytics are ranked by recent ship velocity. Browse the "seriation alternatives" section above for the current picks, or visit /alternatives/seriation-r for the full list with editorial commentary on each.