dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
A side-by-side editorial comparison of NocoDB and OpenMetadata — 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 second 2.0 release candidate lands while 1.13 keeps absorbing governance and CVE fixes.
OpenMetadata is running two lines at once. The 2.0.0 major is on its second release candidate, both explicitly marked dev and test only with no stated changes. The 1.13 line continues as the shipping product: 1.13.3 fixed Snowflake foreign-key collisions across tables sharing a constraint name, unstuck data contracts left at Running, and repaired poisoned governance trigger filters, while 1.12.14 and 1.13.2 were dominated by dependency CVE patching across MLflow, PyArrow, log4j and the ingestion images.
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.
OpenMetadata is running two lines at once. The 2.0.0 major is on its second release candidate, both explicitly marked dev and test only with no stated changes. The 1.13 line continues as the shipping product: 1.13.3 fixed Snowflake foreign-key collisions across tables sharing a constraint name, unstuck data contracts left at Running, and repaired poisoned governance trigger filters, while 1.12.14 and 1.13.2 were dominated by dependency CVE patching across MLflow, PyArrow, log4j and the ingestion images.
The direction was set by 1.13.0, which made MCP a first-class service category and added an RDF knowledge graph; everything since has been consolidation around those two surfaces plus a heavy security-patch cadence. With 2.0 now on its second RC and carrying no published notes, the interesting question — what actually changes in the major — remains unanswered by the entries themselves.
Expect further 2.0 release candidates before a final, and continued 1.13.x maintenance releases weighted toward governance-workflow fixes and dependency patching until the major stabilizes.
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 OpenMetadata.
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
AgencyAI got skills three weeks ago; everything since has been making them routine.
See all NocoDB alternatives → · See all OpenMetadata 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 5.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 5.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 OpenMetadata alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenMetadata alternatives" section above for the current picks, or visit /alternatives/openmetadata for the full list with editorial commentary on each.