Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of NocoDB and omock — 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.
A mock-data generator for OMOP studies that keeps widening what it can fake.
omock builds synthetic OMOP Common Data Model tables so packages in the darwin-eu and OHDSI ecosystem can be tested without touching patient data. The 0.7.0 release adds concept set subsetting with its own vignette, unit and value support in mockMeasurement, observation date validation and cohort attrition initialization, while deprecating mockConcepts. Releases arrive as PR digests rather than written notes.
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.
omock builds synthetic OMOP Common Data Model tables so packages in the darwin-eu and OHDSI ecosystem can be tested without touching patient data. The 0.7.0 release adds concept set subsetting with its own vignette, unit and value support in mockMeasurement, observation date validation and cohort attrition initialization, while deprecating mockConcepts. Releases arrive as PR digests rather than written notes.
The package has been moving from generating tables to shipping and managing reference datasets — mockDatasets arrived in 0.4.0, mockCdmFromDataset gained a source argument in 0.5.0, and 0.6.1 added download retry handling plus an internal GiBleed dataset after the hosted files moved. The recent work is filling in CDM fidelity: type concepts, measurement units, attrition, and guards for degenerate cases like an empty person table.
Expect coverage to keep extending table by table toward the parts of the CDM that omock still cannot mock, with mockConcepts removed outright once the concept set subsetting path settles.
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 omock.
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 NocoDB alternatives → · See all omock 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 omock alternatives in Analytics are ranked by recent ship velocity. Browse the "omock alternatives" section above for the current picks, or visit /alternatives/omock-r for the full list with editorial commentary on each.