NocoDB review

NocoDB is a database application with a spreadsheet-style web interface, not a database engine or a client library. Teams can create an online database in NocoDB’s hosted environment or connect an existing Postgres or MySQL database. It sits above the data layer: users manage records through Grid, Kanban, Gallery, Form and Calendar views, while developers can access data through API and SQL.

That makes it useful when a team needs a shared interface for browsing and editing database records without building a custom front end. It also provides an ERD view to explore database structure and supports imports from Airtable, CSV, Excel and more. The hosted plans put limits on records, storage, seats and API calls; Community is the self-hosted option. The choice is therefore partly architectural: use NocoDB as a hosted application, or operate a self-hosted instance alongside the database and infrastructure your team already manages.

NocoDB exposes Meta APIs and Data APIs. The homepage lists v3 for both and labels the v2 Meta and Data APIs as “will deprecate soon,” so new integrations should target v3 and check the migration guidance before relying on v2. The other named developer surfaces are SQL access and connections to Postgres or MySQL.

The product also supports importing Airtable, CSV and Excel data. The vendor does not name SDK languages, a CLI, webhooks or a plugin system on its homepage; confirm SDK support and current API details in the product docs before choosing a client library. The API quota is plan-based, ranging from 1,000 calls per month on Free to 5 million on Scale. Those monthly allocations are not a substitute for a per-second rate limit: ask the vendor about burst limits, pagination, authentication and behavior at quota before wiring NocoDB into a production service.

NocoDB has two free paths. Cloud Free costs $0 and allows up to 3 users, with 3 editor seats and 10 commenter seats, 1,000 records, 1 GB storage, 100 automation runs and 1,000 API calls per month. Self-hosted Community costs $0 and offers unlimited records, storage and seats, but caps each base at 2 workflows and each workspace at 2 interfaces; it includes 6 views.

Cloud Plus starts at $12 per seat per month billed annually, or $15 monthly. It includes 50,000 records, 20 GB, 30,000 automation runs and 100,000 API calls per month, but no external database connections. Business is $24 annually or $30 monthly per seat, with 300,000 records, 100 GB, 1 million calls and 10 external database connections. Scale starts at $45 annually or $54 monthly per seat, with a 3-seat minimum. Annual billing saves 20%. Unlimited-seat add-ons cost extra on Plus and Business. The vendor does not publish overage prices here; confirm what happens when a quota is reached.

NocoDB describes itself as a fair-source product and offers Community for self-hosting. That plan includes unlimited records, storage and seats, but limits views to 6, workflows to 2 per base and interfaces to 2 per workspace. The product homepage links to GitHub, but the licence terms are not stated on the pricing or homepage text. Review the repository licence and its conditions before treating NocoDB as open source for your use case.

Self-hosting avoids a cloud seat bill, but your team takes responsibility for running the application and its database infrastructure. NocoDB supports Postgres and MySQL connections, API and SQL access, and data imports; the vendor doesn't publish export formats or a migration procedure here. Before building a dependency around it, verify how to export records, attachments and schema, then test a move back to the underlying database or another interface.

The plan quotas are operational limits to track: API calls, automation runs, records, storage and seats can all affect a live deployment. The homepage claims the product can scale to millions of rows, while cloud plan allowances range from 1,000 records on Free to 1 million on Scale; ask how limits and overages work for your intended workload. Confirm API burst limits, service availability commitments, backups, recovery and security controls before putting critical workflows on it.

Security features vary by plan. Business includes private bases and SAML single sign-on; Scale adds row-level security and audit logs; Enterprise lists SCIM, SSO and air-gapped installation. Reddit sentiment is mixed: one self-hosting thread complains that features have moved behind a paywall, and another comparison post reports slower responsiveness and search problems. Those are individual reports, not a reliability measure, but they point to the right checks: test search against your schema and evaluate the Community features you actually need.