dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Comparison · Analytics
fossilsim vs NocoDB
A side-by-side editorial comparison of fossilsim and NocoDB — release velocity, themes, recent moves, and the top alternatives to consider.
fossilsim vs NocoDB: at a glance
What is fossilsim?
A fossil-record simulator that quietly grew a trait-evolution engine.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
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.
fossilsim vs NocoDB: editorial side-by-side
fossilsim
0.0ANALYTICS
A fossil-record simulator that quietly grew a trait-evolution engine.
◆ Current state
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
◆ Where it's heading
The arc runs from sampling mechanics toward simulating what the organisms actually were. Version 2.2.0 taught the package to handle occurrence data for occurrence birth-death models; 2.3.0 then added trait simulation under Mk, BM and OU, which is a different kind of output than fossil ages. Since then the work has been maintenance and keeping the FossilSimShiny GUI in step, suggesting the authors consider the current model set feature-complete.
◆ Prediction
The pairing of the 2.3.3 release with a FossilSimShiny version bump points to the GUI, not the library, as where the next visible work lands. The entries do not show enough activity to predict a specific new model family.
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.
Alternatives to fossilsim 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 fossilsim or NocoDB.
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 fossilsim alternatives → · See all NocoDB alternatives →
Recent activity from fossilsim and NocoDB
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12h agoNocoDB2026.08.1 : Introducing Realtime Presence and Folders
- 14d agoNocoDB2026.08.0 : Introducing Interfaces ⚡
- 1mo agoNocoDB2026.07.0 : Introducing Calendar Sync & Image Annotations
- 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
- 2y agofossilsimCompatibility bump for FossilSimShiny 1.1.2
- 4y agofossilsimBug fixes and documentation cleanup
- 4y agofossilsimTrait simulation arrives: Mk, BM and OU models ⚡
- 5y agofossilsimOccurrence handling for the occurrence birth-death model
Frequently asked questions
What is the difference between fossilsim 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 fossilsim 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 fossilsim?
Top fossilsim alternatives in Analytics are ranked by recent ship velocity. Browse the "fossilsim alternatives" section above for the current picks, or visit /alternatives/fossilsim-r 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.