NocoDB

NocoDB is an open-source, self-hostable platform that transforms existing PostgreSQL, MySQL, and SQLite databases into intuitive, Airtable-style spreadsheet interfaces. It empowers non-technical teams to view, edit, and collaborate on database records through grids, Kanban boards, galleries, forms, and calendars — without writing SQL — while developers retain full programmatic access through auto-generated REST APIs and the NocoDB SDK.

The platform is built on a TypeScript/NestJS backend and a Vue 3 frontend, organized as a monorepo with clearly separated packages for the API server, frontend GUI, and shared SDK. NocoDB connects directly to your existing databases rather than storing data in a proprietary format, which means there is no data lock-in: you own your data in your own schema at all times.

NocoDB ships with an App Store for workflow automations — including integrations with Slack, Discord, AWS S3, Minio, SMTP, and MailerSend — and supports role-based access control at the workspace, base, and table levels. An auto-upstall installer sets up Docker Compose with PostgreSQL, Redis, and Traefik (with automatic SSL) from a single shell command, making production self-hosting straightforward.

What You Get

• Spreadsheet-Style Grid Interface - Full CRUD on database tables through an Excel-like grid with inline editing, row sorting, multi-column filtering, grouping, and column hiding — no SQL required.
• Multiple View Types - Switch between Grid, Kanban, Gallery, Form, and Calendar views on the same underlying table data, each configurable independently with its own sorts, filters, and visible fields.
• Automatic REST API Generation - Every table and view is instantly accessible via versioned REST endpoints (v1 and v3) with Swagger documentation, pagination, filtering, and bulk operations built in.
• Role-Based Access Control - Granular permission tiers (Owner, Creator, Editor, Commenter, Viewer) apply at the workspace, base, and individual view level, including password-protected public share links.
• App Store for Automations - Webhook triggers tied to row events integrate with Slack, Discord, Mattermost, AWS SES, SMTP, MailerSend, AWS S3, Google Cloud Storage, and Minio out of the box.
• Rich Field Types - Supports text, numbers, dates, attachments, barcodes, QR codes, links to other records, lookups, rollups, formulas, ratings, currencies, user fields, and custom rich-text via Tiptap.
• AI-Powered Features - Built-in AI nodes using multiple provider SDKs (OpenAI, Anthropic, Google, Groq, Bedrock) for data transformation, field population, and natural-language query building.
• One-Command Production Installer - The auto-upstall script deploys NocoDB with PostgreSQL, Redis, and Traefik (with automatic SSL certificate renewal) via Docker Compose from a single curl command.

Common Use Cases

• CRM without SaaS lock-in - A sales team connects NocoDB to their existing PostgreSQL contacts database, uses Kanban views to track deal stages, shares a password-protected view with partners, and gets Slack notifications via webhook when a new lead is created.
• Internal inventory management - A warehouse operator builds a no-code inventory tracker using NocoDB’s Gallery view for product photos and Form view for stock updates, with attachments uploaded automatically to AWS S3.
• Project and task tracking - A product team uses NocoDB’s Calendar and Kanban views on a tasks table to visualize sprint work, assign owners, and track deadlines without migrating out of their existing MySQL database.
• Data collection and aggregation - A research team embeds NocoDB public Form views in survey pages to collect responses directly into a structured PostgreSQL table, then analyzes results through filtered Grid views with Rollup columns.
• API-first data backend - A developer uses NocoDB’s auto-generated REST API with JWT auth as a quick backend for internal tools or prototypes, leveraging the NocoDB SDK to programmatically create records and manage schema.
• Replacing spreadsheet chaos - An operations team migrates shared Google Sheets into NocoDB backed by SQLite, gaining proper access controls, field type validation, and relationship links between tables while retaining the familiar spreadsheet UI.

Under The Hood

Architecture NocoDB is organized as a pnpm monorepo with distinct packages for the backend API server (nocodb), the Vue frontend (nc-gui), and a shared TypeScript SDK (nocodb-sdk) that defines types and API contracts used by both sides. The backend follows NestJS module conventions with clearly separated Controllers, Services, and a data-access layer built on Knex.js, which provides a query-builder abstraction over PostgreSQL, MySQL, and SQLite without committing to a single ORM. Controllers handle HTTP routing and request validation, Services encapsulate business logic and emit application-level events through a dedicated EventEmitter module, and the database layer in BaseModelSqlv2 translates NocoDB’s view and filter abstractions into SQL. A field-handler pattern organizes per-type behavior (validation, storage, transformation) into individual handler directories, making it straightforward to add new column types without touching shared code. The frontend communicates exclusively through the versioned REST API, which means the GUI and any external consumer face the same contract.

Tech Stack The backend is a Node.js application built with NestJS, using Knex.js for multi-database SQL abstraction and Redis (optional) for caching. The frontend is a Nuxt 3 / Vue 3 application using Pinia for state management, Tiptap for rich-text editing, and a comprehensive component library for cell renderers, dialogs, and view types. AI integration uses the Vercel AI SDK with adapters for OpenAI, Anthropic, Google, Groq, Amazon Bedrock, DeepSeek, and Azure, making provider selection configurable at runtime. Storage integrations support AWS S3, Google Cloud Storage, Minio, and Backblaze via a plugin architecture. The monorepo is managed with pnpm workspaces and Lerna, bundled with Rspack on the frontend and custom build scripts on the backend, and shipped as both Docker images and self-contained binaries for Linux, macOS, and Windows.

Code Quality The codebase has extensive Playwright end-to-end test suites covering major user flows and over a hundred NestJS unit spec files for controllers and services. The field-handler pattern enforces single-responsibility at the column type level, and the shared SDK eliminates type drift between client and server. However, error handling is inconsistent — some services use typed NcBaseError exceptions while others fall back to generic messages, and test coverage of edge cases in formula evaluation and SQL generation is uneven. TypeScript is used throughout but several utility modules include broad any escapes, and some historical JavaScript files remain in the database client layer. CI runs Jest unit tests, Playwright E2E, and dependency review on every pull request via GitHub Actions.

What Makes It Unique Unlike tools that store data in a proprietary format, NocoDB connects directly to existing databases and reads the live schema, meaning teams can adopt it without migrating their data or changing existing application integrations. The per-type field-handler architecture allows the system to adapt its UI, validation, and API serialization to each column’s semantics rather than treating every cell as a string. The combination of auto-generated Swagger-documented REST APIs and a native SDK means a no-code user and a developer can work on the same table simultaneously through entirely different interfaces. Recent additions of AI nodes with multi-provider support and an MCP server integration position NocoDB as a bridge between structured relational data and LLM-driven workflows, a niche that older no-code database tools have not addressed.

Self-Hosting

NocoDB is released under the Sustainable Use License (version 1.0, updated January 2026), which replaced its previous AGPL 3.0 license as of version 0.301.0. The license permits free use, modification, and self-hosting for your own internal business purposes and for non-commercial or personal use. However, it explicitly prohibits using or distributing the software to provide a commercial service — meaning you cannot offer NocoDB as a hosted product to paying customers without a separate commercial agreement. This is a material distinction from AGPL: teams using NocoDB internally for their own operations are fully permitted, but SaaS providers or managed-service operators building on top of NocoDB are not.

Running NocoDB in production is operationally realistic for teams comfortable with Docker. The auto-upstall script handles the full deployment stack including PostgreSQL, Redis, and Traefik with automatic SSL, so initial setup can be completed in minutes. Day-to-day operations require managing Docker container updates (re-running the installer upgrades in place), monitoring disk usage for attachments and database growth, and maintaining backups of the PostgreSQL or SQLite database independently. NocoDB does not bundle backup tooling, so snapshot schedules and restore procedures are the operator’s responsibility. The application is stateless beyond the database, making horizontal scaling behind a load balancer straightforward once Redis is configured for shared caching.

The hosted NocoDB Cloud offering adds managed infrastructure, automatic upgrades, built-in backups, and enterprise features such as SAML SSO and audit logs that are not present in the self-hosted community edition. Self-hosted deployments do not receive SLAs or priority support — community support is available via Discord and the public forum. Organizations evaluating self-hosting should weigh the operational burden of database maintenance, SSL renewal, and version tracking against the cost of the cloud tier, particularly if the team lacks dedicated DevOps capacity.