NocoDB

NocoDB takes a different approach to the no-code database space: rather than asking you to migrate data into a proprietary store, it connects to a database you already own — MySQL, PostgreSQL, SQLite, SQL Server, or MariaDB — and surfaces a spreadsheet-style UI on top. The practical implication is significant: your data stays in the schema your applications already use, existing services keep working, and the NocoDB layer is additive rather than a replacement. That makes it the most natural fit in this category for teams with live production databases who want to hand a no-code interface to non-technical collaborators.

The feature set covers grid, gallery, kanban, form, and map views, with role-based access control down to the row and field level. Every table gets both a REST and a GraphQL endpoint generated automatically, making NocoDB genuinely useful for developers who want to expose a data layer without building an API from scratch.

Trade-offs worth knowing: the AGPL-3.0 license restricts embedding NocoDB inside proprietary SaaS products without a commercial license, which Baserow's MIT core avoids. The interface is functional but less visually refined than Airtable or Baserow. And because NocoDB wraps whatever schema you give it, disorganized legacy databases produce disorganized views — the tool reveals structure, it doesn't create it. Self-hosting remains NocoDB's clearest value proposition: one Docker image, your data, no per-seat bill.