Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of NocoDB and VWO — 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.
VWO consolidates experimentation, analytics, and AI as the AB Tasty merger surfaces
VWO is broadening from A/B testing into a wider optimization suite: VWO AI to compress insight-to-execution, behavior analytics linked directly to feature experimentation, the VWO Pulse Voice-of-Customer product, and a Go SDK for backend feature flags. Operationally, the AB Tasty merger is now visible — the app is moving from app.vwo.com to app.wingify.com.
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.
VWO is broadening from A/B testing into a wider optimization suite: VWO AI to compress insight-to-execution, behavior analytics linked directly to feature experimentation, the VWO Pulse Voice-of-Customer product, and a Go SDK for backend feature flags. Operationally, the AB Tasty merger is now visible — the app is moving from app.vwo.com to app.wingify.com.
Direction is a unified experimentation-and-insight platform that connects the 'what' (experiments, feature releases) to the 'why' (behavior analytics, VoC feedback), with AI shortening the analysis loop. The merger layers consolidation and infrastructure alignment on top of the feature expansion.
Expect tighter integration between VWO AI, behavior analytics, and feature experimentation, plus continued post-merger platform and domain consolidation.
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 VWO.
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
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. NocoDB and VWO are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 and VWO are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 VWO alternatives in Analytics are ranked by recent ship velocity. Browse the "VWO alternatives" section above for the current picks, or visit /alternatives/vwo for the full list with editorial commentary on each.