SvGrid vs NocoDB

Verdict

NocoDB is the pick when you want a finished app your team signs into. SvGrid Base is the pick when the table database has to live inside your own Svelte app, under your login, your branding and your licence terms, on the database you already run.

Migration guide: moving from NocoDB to SvGrid

At a glance

Overview

NocoDB turns database tables into a collaborative app: grid, form, gallery, Kanban, calendar and map views, linked records with lookups and rollups, record comments, webhooks and workflows. It runs on NocoDB Cloud, priced per seat, or self-hosted with Docker, where the Community edition has no record or storage limits. It can store data in its own database or connect to an existing PostgreSQL or MySQL database. Since January 2026 the source is under the Sustainable Use License rather than AGPL.

SvGrid Base is the same kind of tool shipped as a Svelte 5 component in @svgrid/enterprise. You install it, give it your tables (or point it at your database), and your users get typed fields, saved views, filters, groups, linked records, automations and an expanded record with comments, all inside your app. There is no separate server to run and no second login: the base talks to your database through the endpoint you already have.

Looking for a NocoDB alternative for Svelte?

People searching for a NocoDB alternative usually hit one of three walls: the app has to appear inside their own product rather than in a NocoDB tab or iframe, the January 2026 licence change rules out offering it to customers without a commercial agreement, or the views they need (timeline, Gantt) sit on the Business plan. SvGrid Base answers all three by being a component: <SvBase> renders the grid, Kanban, calendar, gallery, Gantt, chart and form views inside your Svelte app and reads and writes your Postgres, MySQL, SQLite, Supabase or REST API through your own server.

What they have in common

• A grid of typed fields with saved views: grid, form, gallery, Kanban and calendar.
• Linked records between tables, with lookup and rollup fields and formulas.
• Can work on top of an existing PostgreSQL or MySQL database instead of a private store.
• Automations that react to record changes, send email and call webhooks.
• Record comments in an expanded record view.
• Filters, sorts, groups and hidden fields saved per view.

Where SvGrid is stronger

• It is a component, not an app: <SvBase> renders inside your own Svelte pages, under your login and your design tokens, with no iframe and no second product for users to sign into.
• Built to ship to customers: an Enterprise Suite licence covers unlimited apps and end users, so putting the base inside a product your customers use needs no separate agreement.
• Gantt, chart and autonumber are part of the base itself, with no plan above them.
• Automations run in the browser or on your server with no monthly run quota, and their secrets stay on your server.
• Reads and writes Postgres, MySQL, SQLite, Supabase or any REST API through the data source your app already uses, with one parameterized endpoint and an authorize hook you write.
• Priced per developer, not per editor: the people who use the app do not need seats.

Where NocoDB is stronger

• A finished product: sign up or run one Docker command and a team is working, with no developer involved.
• Roles out of the box (owner, creator, editor, commenter, viewer) with a sharing screen, and table and field permissions on paid plans.
• Realtime presence shows who else is in a table, and record revision history is kept for days to a year on cloud and without limit self-hosted.
• A REST API, an SDK, an MCP server and a workflow builder with integration nodes (Slack, Gmail, GitHub and more).
• A map view and file import (CSV, Excel, JSON, and Airtable bases) in the free edition.
• No record limit per table when self-hosted; SvGrid Base keeps each table's records in the page, up to a configurable limit.

Feature by feature

Yes: shipped in the package. Partial: needs extra work or a companion package. Paid tier: only in a paid edition. No: not available. n/a: does not apply.

When to choose SvGrid

• The table database has to appear inside your own Svelte or SvelteKit app, under your login and your look.
• You want to offer it to your customers without a separate commercial agreement for the table tool.
• You need Gantt, charts and autonumber without moving everyone to a higher plan.
• Your data already lives in Postgres, MySQL, SQLite, Supabase or behind your API and should stay there, reached through your own server.
• You would rather pay per developer than per editor seat.

When to choose NocoDB

• You want a finished app a team can use today, with no developer.
• You need roles, sharing links and per-table or per-field permissions managed from a screen.
• You want long record revision history and presence without building anything.
• You want workflows with ready-made Slack, Gmail or GitHub nodes.

Migration effort

Estimated effort: 1-2 hours per base on PostgreSQL or MySQL; more to rebuild workflows.

What you give up:

• The roles screen and sharing links; who may do what moves into your server's authorize hook or your database's row level security.
• Long record revision history; the base shows a session's changes and your audit hook keeps the rest.
• Workflow integration nodes; SvGrid Base automations call webhooks, send email and run actions you register in code.
• A no-code setup path: someone has to add <SvBase> to a Svelte app.

Migration guide: moving from NocoDB to SvGrid

Live example

Project tracker: open it in the gallery for the source and the full-size version.

The bottom line

NocoDB is a strong self-hosted table database for a team that wants a finished app and will sign into it. When the table database is part of your own product, SvGrid Base fits better: it renders inside your Svelte app with your login and branding, works on the database you already run, ships Gantt, charts and server-side automations without plan gates, and its licence already covers putting it in front of your customers.

Frequently asked questions

Can I embed NocoDB inside my own app?

Only as an iframe: NocoDB lets you embed a shared base or a read-only shared view with an HTML iframe, and its licence page says embedding NocoDB in a platform where customers interact with it needs a commercial licence. SvGrid Base is a Svelte component, so it renders in your own pages, edits records in place and uses your app's login.

Is NocoDB still open source?

Its source is public, but since January 2026 it is under the Sustainable Use License, which NocoDB's own docs say is not OSI-approved; before that it was AGPL-3.0. SvGrid Base is commercial (Enterprise Suite of @svgrid/enterprise); the grid it is built on, @svgrid/grid, is MIT.

Can SvGrid Base use the same database NocoDB is connected to?

Yes, if NocoDB was connected to your own PostgreSQL or MySQL database. createBaseEndpoint reads the tables, columns and foreign keys from that database and <SvBase> opens them as tabs with typed fields and links. Tables NocoDB created in its own metadata database are better exported to CSV and loaded into your database first; the migration guide walks through both.

Does SvGrid Base have a Gantt view like NocoDB's paid plans?

Yes. A view of type gantt takes a start and end date field, an optional progress field and a link field for dependencies. NocoDB lists its Gantt and timeline views on the Business plan and above.

How is SvGrid Base priced compared with NocoDB?

NocoDB charges per seat on cloud and on its paid self-hosted plans; the prices it listed on the day we read them are in the pricing line at the top of this page. SvGrid Base ships in Enterprise Suite at $999 per developer per year, for unlimited apps and unlimited end users, so the number of people using the app does not change the price.

What does SvGrid Base not do that NocoDB does?

There is no roles and sharing screen (access rules live in your server or database), no presence indicator, no long revision history kept for you, no map view and no file import dialog in the base itself, and every table's records are held in the page up to a limit you set. It also needs a developer to add it to an app.

Is SvGrid a good NocoDB alternative for Svelte?

People searching for a NocoDB alternative usually hit one of three walls: the app has to appear inside their own product rather than in a NocoDB tab or iframe, the January 2026 licence change rules out offering it to customers without a commercial agreement, or the views they need (timeline, Gantt) sit on the Business plan. SvGrid Base answers all three by being a component: <SvBase> renders the grid, Kanban, calendar, gallery, Gantt, chart and form views inside your Svelte app and reads and writes your Postgres, MySQL, SQLite, Supabase or REST API through your own server.

Related comparisons and docs

• SvGrid vs Airtable
• SvGrid vs Baserow
• Build a project tracker
• From a database to an app
• Keep a base in a database
• Automations
• Field types

Sources and last verified

Every claim on this page was last checked on 14 Oct 2026. Feature and pricing statements come from the pages listed below.

• noco-pricing: Plan cards: Free $0 for up to 3 users with 1,000 records; Plus $12 per seat per month billed annually or $15 monthly; Business $24 annually or $30 monthly; Scale $45 annually or $54 monthly with 3 minimum seats; Enterprise schedule a call; self-hosted Community $0 with unlimited records and storage; dashboards on Business; record revision history from 3 days on Free to 365 days on Enterprise, unlimited self-hosted (checked 14 Oct 2026)
• noco-license: From January 09, 2026 NocoDB changes from AGPL-3.0 to a Sustainable Use License, not OSI-approved; a commercial licence is needed to embed NocoDB in a platform where customers interact with NocoDB itself (checked 14 Oct 2026)
• noco-share: A shared project can be embedded in another application with an HTML iframe; shared views are read-only (checked 14 Oct 2026)
• noco-datasource: Connect an external PostgreSQL or MySQL database as a data source; Microsoft SQL Server is an add-on for Enterprise customers (checked 14 Oct 2026)
• noco-views: View types: grid, form, gallery, Kanban, calendar, map, with list, timeline and Gantt marked for paid plans (checked 14 Oct 2026)
• noco-timeline: Timeline view is available on NocoDB Cloud Business plan and above and licensed self-hosted deployments Business plan and above; the Gantt view page says the same (checked 14 Oct 2026)
• noco-editions: Community edition includes link, lookup, rollup, formula, attachment, rating, user, barcode, QR code and button fields, Airtable import and CSV and Excel export (checked 14 Oct 2026)
• noco-autonumber: Auto Number is available on NocoDB Cloud plans and licensed self-hosted deployments Business plan and above, PostgreSQL only (checked 14 Oct 2026)
• noco-workflows: The Community Edition includes 2 workflows per project with record and manual triggers; workflow actions include send email, HTTP request and integration nodes; cloud automation runs are metered per plan (checked 14 Oct 2026)
• noco-comments: Record comments on every plan; mentions and the comment-resolve workflow need cloud Plus or self-hosted Business and above (checked 14 Oct 2026)
• noco-roles: Owner, creator, editor, commenter and viewer roles on every plan; table and field permissions on cloud Plus or self-hosted Business and above; record level security on Scale (checked 14 Oct 2026)
• noco-presence: Realtime presence shows who else works in a table; it does not lock anything (checked 14 Oct 2026)
• noco-import: Create a table by importing a CSV, Excel or JSON file, maximum file size 5 MB (checked 14 Oct 2026)
• noco-whitelabel: White-label is available on self-hosted instances as an add-on to the Enterprise plan and not on NocoDB Cloud (checked 14 Oct 2026)
• noco-install: One command makes a Docker Compose stack with NocoDB, a worker, Postgres and Redis (checked 14 Oct 2026)