Fulcrum vs NocoDB
Side-by-side trajectory, velocity, and editorial themes.
Field-data captures grow a BI layer while mobile coasts on fixes.
Fulcrum continues steady weekly shipping across web, iOS, and Android, but the substance is concentrated on the web. Recent releases add a freehand lasso selection on maps, a Power BI connector, and time-aware Insights (Beta) queries. Mobile cadence is dominated by single-issue stability fixes rather than new capabilities.
The product is widening from pure field-data capture into the analyze-and-share layer above it. Web work is going into bulk-action ergonomics, BI tooling integration, and growing the Insights surface. Mobile platforms are tracking a maintenance pattern, with versioned releases shipping one or two narrow fixes at a time and no new user-facing capabilities.
Expect Insights to gain depth toward general availability, with more BI-side integrations and richer bulk operations on web selections. Mobile is unlikely to see significant new capabilities in the next cycle.
NocoDB shifts from spreadsheet-database into a multi-surface workspace with a clearer paid tier.
NocoDB is on a tight release cadence with substantial feature drops layered on top of the database. April introduced Map View, three new field types (UUID, GeoData and others), and NocoDocs — a real document editor that sits next to the data. May has continued with multi-column form layouts, Postgres ENUM mirroring, Bookmarks for cross-workspace context, Smart Text fields, and Mermaid diagrams inside NocoDocs. The release notes now consistently split features across CE/Free vs Paid/Enterprise.
NocoDB is repositioning from 'Airtable alternative with a database' to a multi-surface workspace — table + form + map + timeline + docs — with an explicit open-core monetization split. The Self-Serve Self-Hosted Licensing flow shipping in 2026.05.1 closes the buying loop for enterprise self-hosters. AI-flavored features (Smart Text) are starting to appear but are not yet the headline pitch.
Expect the open-core split to deepen and more AI-aware field types to spread across surfaces. Given how integration-shaped the Postgres ENUM and webhook work has been, a richer agent-addressable API or an explicit MCP integration is a plausible next move.
See more alternatives to Fulcrum →
See more alternatives to NocoDB →