@svgrid/mcp 3.0.15 → 3.0.17

package/dist/data.js

@@ -5001,14 +5001,14 @@ export const docs = [
         "path": "docs/help/migrating-from-airtable.md",
         "title": "Migrating from Airtable",
         "section": "Help",
-        "markdown": "# Migrating from Airtable\n\nAirtable is a cloud service: the base, its views and its records live on\nAirtable, and the most you can put in your own app is a read-only iframe.\n[SvGrid Base](./base/start.md) is the same kind of table database shipped\nas a Svelte 5 component. The records move into your own database, `<SvBase>`\nrenders the views inside your app, and every edit goes back to your tables.\n\n> Estimated effort: **half a day** for a typical base, plus the time to\n> rebuild its automations.\n\n<!-- facts:start airtable -->\n> **Facts, checked 14 Oct 2026.** `@svgrid/grid` 3.0.3, MIT, last published 11 Sep 2026, 16,900 npm downloads in the 30 days to 10 Sep 2026. Airtable pricing, as its site states it: Airtable Free has no cost. airtable.com/pricing lists Team at $20 per seat per month billed annually ($24 monthly) and Business at $45 per seat per month billed annually ($54 monthly); Enterprise Scale pricing is custom. Read-only collaborators are not charged on Team or Business (https://airtable.com/pricing, read 14 Oct 2026). SvGrid: SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT. Side by side, with sources: [SvGrid vs Airtable](https://svgrid.com/compare/airtable/).\n<!-- facts:end -->\n\n## What maps to what\n\n| Airtable | SvGrid Base |\n| --- | --- |\n| A base | A `<SvBase tables>` with one tab per table |\n| A table | A table in your database, opened as a `BaseTable` |\n| A linked record field | A foreign key (link to one) or a junction table (link to many) |\n| A view | A `FieldView`: `grid`, `kanban`, `calendar`, `gallery`, `gantt`, `chart` or `form` |\n| An automation | An automation in the view bar, or `createAutomationServer` on your server |\n| Collaborators and permissions | Your app's login, and `authorize` on the endpoint |\n| Comments | `setRecordComments`, stored where your app stores them |\n| An interface | Your own Svelte page around the base |\n\nField types carry over almost one to one:\n\n| Airtable field | `fieldType` |\n| --- | --- |\n| Single line text | `text` |\n| Long text | `longText` (with `richText` for bold, italic, links and lists) |\n| Attachment | `attachment` |\n| Checkbox | `checkbox` |\n| Single select, multiple select | `singleSelect`, `multiSelect` |\n| User | `user` |\n| Date | `date` |\n| Phone number, email, URL | `phone`, `email`, `url` |\n| Number, currency, percent | `number` with `format: 'integer'`, `'currency'` or `'percent'` |\n| Duration | `duration` |\n| Rating | `rating` |\n| Formula | `formula` |\n| Lookup, rollup, count | `lookup`, `rollup`, `count` |\n| Created time, last modified time | `createdTime`, `lastModifiedTime` |\n| Created by, last modified by | `createdBy`, `lastModifiedBy` |\n| Autonumber | `autoNumber` |\n| Barcode, button | `barcode`, `button` |\n| Linked record | `link` |\n\nFormulas use the same shape: fields by name in braces, `&` to join text,\nand functions such as `IF`, `SWITCH`, `ROUND`, `DATEADD` and\n`DATETIME_DIFF`. Paste each formula into the field editor; one that uses a\nfunction the base does not have shows `#ERROR` and names it, and you\nrewrite that part.\n\n## 1. Export each table\n\nIn Airtable, open a grid view that shows every field and every record (no\nfilter, no hidden fields) and choose **Download CSV**. Do this for each\ntable. A linked record column comes out as text naming the linked records\nrather than as record ids; open one file to see the exact form before the\nnext step turns those names back into links.\n\nAttachment columns come out as URLs that Airtable expires after a few\nhours. Download the files straight away and put them in your own storage,\nor skip the column and move the files later.\n\n## 2. Load the tables into your database\n\nCreate a table per Airtable table, with a key the database makes, and load\nthe CSV with a text column for each link. Postgres:\n\n```sql\ncreate table projects (\n  id uuid primary key default gen_random_uuid(),\n  name text not null,\n  status text,\n  due date\n);\n\ncreate table tasks (\n  id uuid primary key default gen_random_uuid(),\n  task text not null,\n  status text,\n  budget numeric,\n  project_name text,                    -- the CSV's \"Project\" column\n  project_id uuid references projects(id)\n);\n\n\\copy projects (name, status, due) from 'Projects-Grid view.csv' csv header\n\\copy tasks (task, status, budget, project_name) from 'Tasks-Grid view.csv' csv header\n```\n\nThen match the names to keys and drop the text column:\n\n```sql\nupdate tasks t set project_id = p.id\nfrom projects p where p.name = t.project_name;\n\nalter table tasks drop column project_name;\n```\n\nA link to many records becomes a table that pairs the two. Load the CSV's\nlist of names into a text column first (`tag_names` below; adjust the\nseparator to what the file holds), then:\n\n```sql\ncreate table task_tags (\n  task_id uuid references tasks(id) on delete cascade,\n  tag_id uuid references tags(id) on delete cascade,\n  primary key (task_id, tag_id)\n);\n\ninsert into task_tags (task_id, tag_id)\nselect t.id, g.id\nfrom tasks t\ncross join lateral unnest(string_to_array(t.tag_names, ', ')) as n(name)\njoin tags g on g.name = n.name;\n```\n\nNames must be unique for the match to be right. If two Airtable records\nshared a primary value, give them distinct names before you export, or\nmatch on another column.\n\n## 3. Open the database as a base\n\nOne endpoint on your server reads the tables and serves them; the page\nopens them. A foreign key becomes a link with a field in the other table\nthat links back, a pairing table a link to many records, and a text column\nthat repeats a few values a single select with a color per value\n([what it reads](./base/quick-start.md#what-it-reads-from-your-database)).\n\n```ts\n// src/routes/api/base/+server.ts\nimport { createBaseEndpoint } from '@svgrid/enterprise/base'\n\n// Your database driver: run parameterized SQL, return the rows.\ndeclare function query(sql: string, params: unknown[]): Promise<Record<string, unknown>[]>\n\nexport const { GET, POST } = createBaseEndpoint({ execute: query })\n```\n\n```svelte\n<!-- src/routes/base/+page.svelte (with `export const ssr = false` in +page.ts) -->\n<script lang=\"ts\">\n  import { SvToaster } from '@svgrid/grid'\n  import { SvBase, baseFromEndpoint, enableBase } from '@svgrid/enterprise/base'\n\n  enableBase()\n  const tables = baseFromEndpoint('/api/base')\n</script>\n\n{#await tables then tables}\n  <SvBase {tables} editable sortable columnAdder fieldMenu />\n{/await}\n<SvToaster />\n```\n\n[Build a base on Postgres](./base/postgres.md) is the same thing end to\nend, and [From a database to an app](./base/quick-start.md) covers MySQL,\nSQLite and Supabase.\n\n## 4. Set the field types and views\n\nThe base guesses the types from the columns. Fix the ones it cannot know\n(a percent, a rating, a user, a formula) and recreate the views you used:\n\n```ts\nimport type { FieldView } from '@svgrid/enterprise/base'\n\nconst views: FieldView[] = [\n  { id: 'all', name: 'All tasks', type: 'grid', color: { mode: 'field', field: 'status' } },\n  { id: 'board', name: 'Board', type: 'kanban', stackBy: 'status' },\n  { id: 'due', name: 'Due dates', type: 'calendar', dateField: 'due' },\n  { id: 'request', name: 'Request a task', type: 'form' },\n]\n```\n\nWhat you change in the app (field types, views, colors) comes back through\n`onTablesChange`; store it and start from it next time. The records stay in\nyour database either way.\n\n## 5. Rebuild the automations\n\nOpen **Automations** in the view bar. The triggers you know are there: a\nrecord is created, a record changes, a record matches a condition, a form\nis sent, a button is pressed, a scheduled time. The actions update the\nrecord, create a record in any table, show a notice, color the record,\ncall a webhook or send an email. An Airtable script that calls an API\nbecomes a webhook action, or an action you register in code with\n`registerAutomationAction`.\n\nAutomations that must run whoever made the change, or that hold secrets,\nrun on your server with `createAutomationServer`; see\n[Automations on the server](./base/automations.md#on-the-server).\n\n## 6. Users, permissions and comments\n\nYour app's login replaces Airtable collaborators. List the people for user\nfields with `setFieldUsers`, say who is signed in with `setCurrentUser`\n(created by and last modified by read it), and decide who may read or write\nwhat in the endpoint's `authorize`, or with row level security on Supabase.\nComments go through `setRecordComments` to wherever you keep them.\n\n## What you give up\n\n- The hosted service: someone adds `<SvBase>` to a Svelte app and runs the\n  database it reads.\n- Interfaces, Omni and the AI credits. The pages around the base are your\n  own Svelte pages.\n- Native mobile apps, and the list and inbox views.\n- The permissions screen, sharing links and the long revision history.\n  Access rules live in your server or database; the record shows the\n  changes made in the session, and the endpoint's `audit` hook can log\n  every write.\n\nSvGrid Base is part of the Suite edition of `@svgrid/enterprise` ($999 per\ndeveloper). It runs without a key during an evaluation, with a watermark.\n\n## See also\n\n- [SvGrid vs Airtable](https://svgrid.com/compare/airtable/): the side-by-side comparison with sources.\n- [Build a project tracker](./base/start.md): SvGrid Base step by step.\n- [Ready-to-use bases](./base/templates.md): a CRM, a content calendar, a roadmap and more.\n- [Field types](./fields.md): every type and its properties.\n"
+        "markdown": "# Migrating from Airtable\n\nAirtable is a cloud service: the base, its views and its records live on\nAirtable, and the most you can put in your own app is a read-only iframe.\n[SvGrid Base](./base/start.md) is the same kind of table database shipped\nas a Svelte 5 component. The records move into your own database, `<SvBase>`\nrenders the views inside your app, and every edit goes back to your tables.\n\n> Estimated effort: **half a day** for a typical base, plus the time to\n> rebuild its automations.\n\n<!-- facts:start airtable -->\n> **Facts, checked 14 Oct 2026.** `@svgrid/grid` 3.0.3, MIT, last published 11 Sep 2026, 16,900 npm downloads in the 30 days to 10 Sep 2026. Airtable pricing, as its site states it: Airtable Free has no cost. airtable.com/pricing lists Team at $20 per seat per month billed annually ($24 monthly) and Business at $45 per seat per month billed annually ($54 monthly); Enterprise Scale pricing is custom. Read-only collaborators are not charged on Team or Business (https://airtable.com/pricing, read 14 Oct 2026). SvGrid: SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT. Side by side, with sources: [SvGrid vs Airtable](https://svgrid.com/compare/airtable/).\n<!-- facts:end -->\n\n## What maps to what\n\n| Airtable | SvGrid Base |\n| --- | --- |\n| A base | A `<SvBase tables>` with one tab per table |\n| A table | A table in your database, opened as a `BaseTable` |\n| A linked record field | A foreign key (link to one) or a junction table (link to many) |\n| A view | A `FieldView`: `grid`, `kanban`, `calendar`, `gallery`, `chart` or `form` |\n| An automation | An automation in the view bar, or `createAutomationServer` on your server |\n| Collaborators and permissions | Your app's login, and `authorize` on the endpoint |\n| Comments | `setRecordComments`, stored where your app stores them |\n| An interface | Your own Svelte page around the base |\n\nField types carry over almost one to one:\n\n| Airtable field | `fieldType` |\n| --- | --- |\n| Single line text | `text` |\n| Long text | `longText` (with `richText` for bold, italic, links and lists) |\n| Attachment | `attachment` |\n| Checkbox | `checkbox` |\n| Single select, multiple select | `singleSelect`, `multiSelect` |\n| User | `user` |\n| Date | `date` |\n| Phone number, email, URL | `phone`, `email`, `url` |\n| Number, currency, percent | `number` with `format: 'integer'`, `'currency'` or `'percent'` |\n| Duration | `duration` |\n| Rating | `rating` |\n| Formula | `formula` |\n| Lookup, rollup, count | `lookup`, `rollup`, `count` |\n| Created time, last modified time | `createdTime`, `lastModifiedTime` |\n| Created by, last modified by | `createdBy`, `lastModifiedBy` |\n| Autonumber | `autoNumber` |\n| Barcode, button | `barcode`, `button` |\n| Linked record | `link` |\n\nFormulas use the same shape: fields by name in braces, `&` to join text,\nand functions such as `IF`, `SWITCH`, `ROUND`, `DATEADD` and\n`DATETIME_DIFF`. Paste each formula into the field editor; one that uses a\nfunction the base does not have shows `#ERROR` and names it, and you\nrewrite that part.\n\n## 1. Export each table\n\nIn Airtable, open a grid view that shows every field and every record (no\nfilter, no hidden fields) and choose **Download CSV**. Do this for each\ntable. A linked record column comes out as text naming the linked records\nrather than as record ids; open one file to see the exact form before the\nnext step turns those names back into links.\n\nAttachment columns come out as URLs that Airtable expires after a few\nhours. Download the files straight away and put them in your own storage,\nor skip the column and move the files later.\n\n## 2. Load the tables into your database\n\nCreate a table per Airtable table, with a key the database makes, and load\nthe CSV with a text column for each link. Postgres:\n\n```sql\ncreate table projects (\n  id uuid primary key default gen_random_uuid(),\n  name text not null,\n  status text,\n  due date\n);\n\ncreate table tasks (\n  id uuid primary key default gen_random_uuid(),\n  task text not null,\n  status text,\n  budget numeric,\n  project_name text,                    -- the CSV's \"Project\" column\n  project_id uuid references projects(id)\n);\n\n\\copy projects (name, status, due) from 'Projects-Grid view.csv' csv header\n\\copy tasks (task, status, budget, project_name) from 'Tasks-Grid view.csv' csv header\n```\n\nThen match the names to keys and drop the text column:\n\n```sql\nupdate tasks t set project_id = p.id\nfrom projects p where p.name = t.project_name;\n\nalter table tasks drop column project_name;\n```\n\nA link to many records becomes a table that pairs the two. Load the CSV's\nlist of names into a text column first (`tag_names` below; adjust the\nseparator to what the file holds), then:\n\n```sql\ncreate table task_tags (\n  task_id uuid references tasks(id) on delete cascade,\n  tag_id uuid references tags(id) on delete cascade,\n  primary key (task_id, tag_id)\n);\n\ninsert into task_tags (task_id, tag_id)\nselect t.id, g.id\nfrom tasks t\ncross join lateral unnest(string_to_array(t.tag_names, ', ')) as n(name)\njoin tags g on g.name = n.name;\n```\n\nNames must be unique for the match to be right. If two Airtable records\nshared a primary value, give them distinct names before you export, or\nmatch on another column.\n\n## 3. Open the database as a base\n\nOne endpoint on your server reads the tables and serves them; the page\nopens them. A foreign key becomes a link with a field in the other table\nthat links back, a pairing table a link to many records, and a text column\nthat repeats a few values a single select with a color per value\n([what it reads](./base/quick-start.md#what-it-reads-from-your-database)).\n\n```ts\n// src/routes/api/base/+server.ts\nimport { createBaseEndpoint } from '@svgrid/enterprise/base'\n\n// Your database driver: run parameterized SQL, return the rows.\ndeclare function query(sql: string, params: unknown[]): Promise<Record<string, unknown>[]>\n\nexport const { GET, POST } = createBaseEndpoint({ execute: query })\n```\n\n```svelte\n<!-- src/routes/base/+page.svelte (with `export const ssr = false` in +page.ts) -->\n<script lang=\"ts\">\n  import { SvToaster } from '@svgrid/grid'\n  import { SvBase, baseFromEndpoint, enableBase } from '@svgrid/enterprise/base'\n\n  enableBase()\n  const tables = baseFromEndpoint('/api/base')\n</script>\n\n{#await tables then tables}\n  <SvBase {tables} editable sortable columnAdder fieldMenu />\n{/await}\n<SvToaster />\n```\n\n[Build a base on Postgres](./base/postgres.md) is the same thing end to\nend, and [From a database to an app](./base/quick-start.md) covers MySQL,\nSQLite and Supabase.\n\n## 4. Set the field types and views\n\nThe base guesses the types from the columns. Fix the ones it cannot know\n(a percent, a rating, a user, a formula) and recreate the views you used:\n\n```ts\nimport type { FieldView } from '@svgrid/enterprise/base'\n\nconst views: FieldView[] = [\n  { id: 'all', name: 'All tasks', type: 'grid', color: { mode: 'field', field: 'status' } },\n  { id: 'board', name: 'Board', type: 'kanban', stackBy: 'status' },\n  { id: 'due', name: 'Due dates', type: 'calendar', dateField: 'due' },\n  { id: 'request', name: 'Request a task', type: 'form' },\n]\n```\n\nWhat you change in the app (field types, views, colors) comes back through\n`onTablesChange`; store it and start from it next time. The records stay in\nyour database either way.\n\n## 5. Rebuild the automations\n\nOpen **Automations** in the view bar. The triggers you know are there: a\nrecord is created, a record changes, a record matches a condition, a form\nis sent, a button is pressed, a scheduled time. The actions update the\nrecord, create a record in any table, show a notice, color the record,\ncall a webhook or send an email. An Airtable script that calls an API\nbecomes a webhook action, or an action you register in code with\n`registerAutomationAction`.\n\nAutomations that must run whoever made the change, or that hold secrets,\nrun on your server with `createAutomationServer`; see\n[Automations on the server](./base/automations.md#on-the-server).\n\n## 6. Users, permissions and comments\n\nYour app's login replaces Airtable collaborators. List the people for user\nfields with `setFieldUsers`, say who is signed in with `setCurrentUser`\n(created by and last modified by read it), and decide who may read or write\nwhat in the endpoint's `authorize`, or with row level security on Supabase.\nComments go through `setRecordComments` to wherever you keep them.\n\n## What you give up\n\n- The hosted service: someone adds `<SvBase>` to a Svelte app and runs the\n  database it reads.\n- Interfaces, Omni and the AI credits. The pages around the base are your\n  own Svelte pages.\n- Native mobile apps, and the list and inbox views.\n- The permissions screen, sharing links and the long revision history.\n  Access rules live in your server or database; the record shows the\n  changes made in the session, and the endpoint's `audit` hook can log\n  every write.\n\nSvGrid Base is part of the Suite edition of `@svgrid/enterprise` ($999 per\ndeveloper). It runs without a key during an evaluation, with a watermark.\n\n## See also\n\n- [SvGrid vs Airtable](https://svgrid.com/compare/airtable/): the side-by-side comparison with sources.\n- [Build a project tracker](./base/start.md): SvGrid Base step by step.\n- [Ready-to-use bases](./base/templates.md): a CRM, a content calendar, a roadmap and more.\n- [Field types](./fields.md): every type and its properties.\n"
     },
     {
         "slug": "help/migrating-from-baserow",
         "path": "docs/help/migrating-from-baserow.md",
         "title": "Migrating from Baserow",
         "section": "Help",
-        "markdown": "# Migrating from Baserow\n\nBaserow is an app your team signs into; outside it, a view shows up only as\na read-only iframe. [SvGrid Base](./base/start.md) is the same kind of table\ndatabase shipped as a Svelte 5 component. The records go into tables in your\nown database, `<SvBase>` renders editable views inside your app, and every\nchange is written back to those tables.\n\n> Estimated effort: **1-3 hours** per database, plus the time to rebuild\n> its automations.\n\n<!-- facts:start baserow -->\n> **Facts, checked 14 Oct 2026.** `@svgrid/grid` 3.0.3, MIT, last published 11 Sep 2026, 16,900 npm downloads in the 30 days to 10 Sep 2026. Baserow pricing, as its site states it: Baserow's self-hosted open-source edition is free with unlimited rows. baserow.io/pricing lists Premium at $10 per user per month billed yearly ($12 monthly), Advanced at $18 per user per month billed yearly ($22 monthly) and Enterprise on request, at the same prices on cloud and self-hosted; cloud Free is $0 with 3,000 rows per workspace (https://baserow.io/pricing, read 14 Oct 2026). SvGrid: SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT. Side by side, with sources: [SvGrid vs Baserow](https://svgrid.com/compare/baserow/).\n<!-- facts:end -->\n\n## Two starting points\n\n- **Your data was synced in from your own PostgreSQL.** Baserow's\n  PostgreSQL data sync copies a table you own into Baserow. Skip the export:\n  point the base at the source tables (step 3) and they open with their\n  foreign keys as links.\n- **Your data lives in Baserow.** Baserow's own tables belong to Baserow.\n  Export each one and load it into tables of yours, as below.\n\n## What maps to what\n\n| Baserow | SvGrid Base |\n| --- | --- |\n| A database | A `<SvBase tables>` with one tab per table |\n| A table | A table in your database, opened as a `BaseTable` |\n| A view | A `FieldView`: `grid`, `kanban`, `calendar`, `gallery`, `gantt`, `chart` or `form` |\n| A timeline view | A `gantt` view with `dateField` and `endField` |\n| An automation | An automation in the view bar, or `createAutomationServer` on your server |\n| Workspace roles | Your app's login, and `authorize` on the endpoint |\n| Row comments | `setRecordComments`, stored where your app stores them |\n| An application builder page | Your own Svelte page around the base |\n\n| Baserow field | `fieldType` |\n| --- | --- |\n| Single line text, long text | `text`, `longText` |\n| Link to table | `link` |\n| Lookup, rollup, count | `lookup`, `rollup`, `count` |\n| Formula | `formula` |\n| Number, rating, duration | `number`, `rating`, `duration` |\n| Boolean | `checkbox` |\n| Date | `date` |\n| Created on, last modified | `createdTime`, `lastModifiedTime` |\n| Created by, last modified by | `createdBy`, `lastModifiedBy` |\n| Collaborator | `user` |\n| File | `attachment` |\n| Single select, multiple select | `singleSelect`, `multiSelect` |\n| Autonumber | `autoNumber` |\n| URL, email, phone number | `url`, `email`, `phone` |\n| Button | `button` |\n| UUID | `text`, or the table's key |\n| Password | none: passwords belong to your app's login |\n| AI prompt | none: an automation action you register with `registerAutomationAction` |\n\nBaserow formulas name fields in square brackets (`[Quantity] * [Unit Price]`);\nSvGrid Base names them in braces (`{Quantity} * {Unit Price}`). Change the\nbrackets and paste the formula into the field editor. A function the base\ndoes not have shows `#ERROR` and is named in the editor, so you rewrite\nthat part.\n\n## 1. Export each table\n\nIn each table, export the grid view as CSV with every field shown and no\nfilter. Open one file and look at how the link columns came out: the next\nstep matches the linked rows they name back to keys.\n\n## 2. Load the tables into your database\n\nCreate a table per Baserow table, with a key the database makes, load the\nCSV, and turn the link text into foreign keys and pairing tables. The SQL is\nthe same as for any other CSV export:\n[Load the tables into your database](./migrating-from-airtable.md#2-load-the-tables-into-your-database)\nwalks through it, a link to one record and a link to many.\n\n## 3. Open the database as a base\n\n```ts\n// src/routes/api/base/+server.ts\nimport { createBaseEndpoint } from '@svgrid/enterprise/base'\n\n// Your database driver: run parameterized SQL, return the rows.\ndeclare function query(sql: string, params: unknown[]): Promise<Record<string, unknown>[]>\n\nexport const { GET, POST } = createBaseEndpoint({ execute: query })\n```\n\n```svelte\n<!-- src/routes/base/+page.svelte (with `export const ssr = false` in +page.ts) -->\n<script lang=\"ts\">\n  import { SvToaster } from '@svgrid/grid'\n  import { SvBase, baseFromEndpoint, enableBase } from '@svgrid/enterprise/base'\n\n  enableBase()\n  const tables = baseFromEndpoint('/api/base')\n</script>\n\n{#await tables then tables}\n  <SvBase {tables} editable sortable columnAdder fieldMenu />\n{/await}\n<SvToaster />\n```\n\nForeign keys become links with a field on the other side that links back,\npairing tables become links to many records, and a text column that repeats\na few values becomes a single select with a color per value. See\n[what it reads from your database](./base/quick-start.md#what-it-reads-from-your-database).\n\n## 4. Views, automations and access\n\nRecreate the views you used, including the Kanban, calendar and timeline\nviews that were paid on Baserow:\n\n```ts\nimport type { FieldView } from '@svgrid/enterprise/base'\n\nconst views: FieldView[] = [\n  { id: 'all', name: 'All rows', type: 'grid', color: { mode: 'field', field: 'status' } },\n  { id: 'board', name: 'Board', type: 'kanban', stackBy: 'status' },\n  { id: 'due', name: 'Due dates', type: 'calendar', dateField: 'due' },\n]\n```\n\nAutomations take the triggers you know (a record created or changed, a\ncondition, a form, a button, a schedule) and update records, create\nrecords, call webhooks or send email; see [Automations](./base/automations.md).\nRoles move into the endpoint's `authorize`, or into row level security on\nSupabase.\n\n## What you give up\n\n- Workspaces, roles and the sharing screen. Access rules live in your\n  server or database.\n- The application builder. The screens around the base are your own\n  Svelte pages.\n- Long row change history and audit logs kept for you. The record shows the\n  changes made in the session, and the endpoint's `audit` hook can log every\n  write.\n- File import, AI fields and the AI assistant inside the tool.\n\nSvGrid Base is part of the Suite edition of `@svgrid/enterprise` ($999 per\ndeveloper). It runs without a key during an evaluation, with a watermark.\n\n## See also\n\n- [SvGrid vs Baserow](https://svgrid.com/compare/baserow/): the side-by-side comparison with sources.\n- [Keep a base in a database](./base/data.md): how the writes, links and realtime work.\n- [Ready-to-use bases](./base/templates.md): templates to start from.\n- [Field types](./fields.md): every type and its properties.\n"
+        "markdown": "# Migrating from Baserow\n\nBaserow is an app your team signs into; outside it, a view shows up only as\na read-only iframe. [SvGrid Base](./base/start.md) is the same kind of table\ndatabase shipped as a Svelte 5 component. The records go into tables in your\nown database, `<SvBase>` renders editable views inside your app, and every\nchange is written back to those tables.\n\n> Estimated effort: **1-3 hours** per database, plus the time to rebuild\n> its automations.\n\n<!-- facts:start baserow -->\n> **Facts, checked 14 Oct 2026.** `@svgrid/grid` 3.0.3, MIT, last published 11 Sep 2026, 16,900 npm downloads in the 30 days to 10 Sep 2026. Baserow pricing, as its site states it: Baserow's self-hosted open-source edition is free with unlimited rows. baserow.io/pricing lists Premium at $10 per user per month billed yearly ($12 monthly), Advanced at $18 per user per month billed yearly ($22 monthly) and Enterprise on request, at the same prices on cloud and self-hosted; cloud Free is $0 with 3,000 rows per workspace (https://baserow.io/pricing, read 14 Oct 2026). SvGrid: SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT. Side by side, with sources: [SvGrid vs Baserow](https://svgrid.com/compare/baserow/).\n<!-- facts:end -->\n\n## Two starting points\n\n- **Your data was synced in from your own PostgreSQL.** Baserow's\n  PostgreSQL data sync copies a table you own into Baserow. Skip the export:\n  point the base at the source tables (step 3) and they open with their\n  foreign keys as links.\n- **Your data lives in Baserow.** Baserow's own tables belong to Baserow.\n  Export each one and load it into tables of yours, as below.\n\n## What maps to what\n\n| Baserow | SvGrid Base |\n| --- | --- |\n| A database | A `<SvBase tables>` with one tab per table |\n| A table | A table in your database, opened as a `BaseTable` |\n| A view | A `FieldView`: `grid`, `kanban`, `calendar`, `gallery`, `chart` or `form` |\n| An automation | An automation in the view bar, or `createAutomationServer` on your server |\n| Workspace roles | Your app's login, and `authorize` on the endpoint |\n| Row comments | `setRecordComments`, stored where your app stores them |\n| An application builder page | Your own Svelte page around the base |\n\n| Baserow field | `fieldType` |\n| --- | --- |\n| Single line text, long text | `text`, `longText` |\n| Link to table | `link` |\n| Lookup, rollup, count | `lookup`, `rollup`, `count` |\n| Formula | `formula` |\n| Number, rating, duration | `number`, `rating`, `duration` |\n| Boolean | `checkbox` |\n| Date | `date` |\n| Created on, last modified | `createdTime`, `lastModifiedTime` |\n| Created by, last modified by | `createdBy`, `lastModifiedBy` |\n| Collaborator | `user` |\n| File | `attachment` |\n| Single select, multiple select | `singleSelect`, `multiSelect` |\n| Autonumber | `autoNumber` |\n| URL, email, phone number | `url`, `email`, `phone` |\n| Button | `button` |\n| UUID | `text`, or the table's key |\n| Password | none: passwords belong to your app's login |\n| AI prompt | none: an automation action you register with `registerAutomationAction` |\n\nBaserow formulas name fields in square brackets (`[Quantity] * [Unit Price]`);\nSvGrid Base names them in braces (`{Quantity} * {Unit Price}`). Change the\nbrackets and paste the formula into the field editor. A function the base\ndoes not have shows `#ERROR` and is named in the editor, so you rewrite\nthat part.\n\n## 1. Export each table\n\nIn each table, export the grid view as CSV with every field shown and no\nfilter. Open one file and look at how the link columns came out: the next\nstep matches the linked rows they name back to keys.\n\n## 2. Load the tables into your database\n\nCreate a table per Baserow table, with a key the database makes, load the\nCSV, and turn the link text into foreign keys and pairing tables. The SQL is\nthe same as for any other CSV export:\n[Load the tables into your database](./migrating-from-airtable.md#2-load-the-tables-into-your-database)\nwalks through it, a link to one record and a link to many.\n\n## 3. Open the database as a base\n\n```ts\n// src/routes/api/base/+server.ts\nimport { createBaseEndpoint } from '@svgrid/enterprise/base'\n\n// Your database driver: run parameterized SQL, return the rows.\ndeclare function query(sql: string, params: unknown[]): Promise<Record<string, unknown>[]>\n\nexport const { GET, POST } = createBaseEndpoint({ execute: query })\n```\n\n```svelte\n<!-- src/routes/base/+page.svelte (with `export const ssr = false` in +page.ts) -->\n<script lang=\"ts\">\n  import { SvToaster } from '@svgrid/grid'\n  import { SvBase, baseFromEndpoint, enableBase } from '@svgrid/enterprise/base'\n\n  enableBase()\n  const tables = baseFromEndpoint('/api/base')\n</script>\n\n{#await tables then tables}\n  <SvBase {tables} editable sortable columnAdder fieldMenu />\n{/await}\n<SvToaster />\n```\n\nForeign keys become links with a field on the other side that links back,\npairing tables become links to many records, and a text column that repeats\na few values becomes a single select with a color per value. See\n[what it reads from your database](./base/quick-start.md#what-it-reads-from-your-database).\n\n## 4. Views, automations and access\n\nRecreate the views you used, including the Kanban and calendar views that\nwere paid on Baserow:\n\n```ts\nimport type { FieldView } from '@svgrid/enterprise/base'\n\nconst views: FieldView[] = [\n  { id: 'all', name: 'All rows', type: 'grid', color: { mode: 'field', field: 'status' } },\n  { id: 'board', name: 'Board', type: 'kanban', stackBy: 'status' },\n  { id: 'due', name: 'Due dates', type: 'calendar', dateField: 'due' },\n]\n```\n\nAutomations take the triggers you know (a record created or changed, a\ncondition, a form, a button, a schedule) and update records, create\nrecords, call webhooks or send email; see [Automations](./base/automations.md).\nRoles move into the endpoint's `authorize`, or into row level security on\nSupabase.\n\n## What you give up\n\n- Workspaces, roles and the sharing screen. Access rules live in your\n  server or database.\n- The application builder. The screens around the base are your own\n  Svelte pages.\n- Long row change history and audit logs kept for you. The record shows the\n  changes made in the session, and the endpoint's `audit` hook can log every\n  write.\n- File import, AI fields and the AI assistant inside the tool.\n\nSvGrid Base is part of the Suite edition of `@svgrid/enterprise` ($999 per\ndeveloper). It runs without a key during an evaluation, with a watermark.\n\n## See also\n\n- [SvGrid vs Baserow](https://svgrid.com/compare/baserow/): the side-by-side comparison with sources.\n- [Keep a base in a database](./base/data.md): how the writes, links and realtime work.\n- [Ready-to-use bases](./base/templates.md): templates to start from.\n- [Field types](./fields.md): every type and its properties.\n"
     },
     {
         "slug": "help/migrating-from-devextreme",
@@ -5064,7 +5064,7 @@ export const docs = [
         "path": "docs/help/migrating-from-nocodb.md",
         "title": "Migrating from NocoDB",
         "section": "Help",
-        "markdown": "# Migrating from NocoDB\n\nNocoDB is an app your team signs into, and outside it a shared view shows up\nonly as an iframe. [SvGrid Base](./base/start.md) is the same kind of table\ndatabase shipped as a Svelte 5 component: `<SvBase>` renders the views\ninside your own app, on your own database, and writes every change back.\n\n> Estimated effort: **1-2 hours** per base on PostgreSQL or MySQL; more to\n> rebuild workflows.\n\n<!-- facts:start nocodb -->\n> **Facts, checked 14 Oct 2026.** `@svgrid/grid` 3.0.3, MIT, last published 11 Sep 2026, 16,900 npm downloads in the 30 days to 10 Sep 2026. NocoDB pricing, as its site states it: NocoDB self-hosted Community is $0 under the Sustainable Use License. nocodb.com/pricing lists cloud Plus at $12 per seat per month billed annually ($15 monthly), Business at $24 per seat per month billed annually ($30 monthly), Scale at $45 per seat per month billed annually with 3 minimum seats, and Enterprise on request; self-hosted Business and Scale are priced the same per seat (https://nocodb.com/pricing, read 14 Oct 2026). SvGrid: SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT. Side by side, with sources: [SvGrid vs NocoDB](https://svgrid.com/compare/nocodb/).\n<!-- facts:end -->\n\n## Two starting points\n\n- **NocoDB was connected to your own PostgreSQL or MySQL.** The tables are\n  already yours. Point the base at the same database (step 2) and you are\n  most of the way there.\n- **The tables live in NocoDB's own database.** Download each table as CSV\n  (NocoDB also offers JSON and Excel), load it into tables of yours, and\n  continue from step 2.\n  [Load the tables into your database](./migrating-from-airtable.md#2-load-the-tables-into-your-database)\n  has the SQL for the keys, a link to one record and a link to many.\n\n## What maps to what\n\n| NocoDB | SvGrid Base |\n| --- | --- |\n| A base | A `<SvBase tables>` with one tab per table |\n| A table | A table in your database, opened as a `BaseTable` |\n| A view | A `FieldView`: `grid`, `kanban`, `calendar`, `gallery`, `gantt`, `chart` or `form` |\n| A timeline or Gantt view | A `gantt` view with `dateField`, `endField` and `dependencyField` |\n| A workflow or webhook | An automation in the view bar, or `createAutomationServer` on your server |\n| Roles | Your app's login, and `authorize` on the endpoint |\n| Record comments | `setRecordComments`, stored where your app stores them |\n\n| NocoDB field | `fieldType` |\n| --- | --- |\n| Single line text, long text | `text`, `longText` |\n| Link to another record | `link` |\n| Lookup, rollup | `lookup`, `rollup`; a rollup with the count function can be `count` |\n| Formula | `formula` |\n| Number, currency, percent | `number` with the matching `format` |\n| Rating, duration | `rating`, `duration` |\n| Checkbox | `checkbox` |\n| Date | `date` (with `time: true` for a date and time) |\n| Created time, last modified time | `createdTime`, `lastModifiedTime` |\n| Created by, last modified by | `createdBy`, `lastModifiedBy` |\n| User | `user` |\n| Attachment | `attachment` |\n| Single select, multi select | `singleSelect`, `multiSelect` |\n| Barcode, button | `barcode`, `button` |\n| Auto number | `autoNumber` |\n| Email, URL, phone number | `email`, `url`, `phone` |\n\nPaste each formula into the field editor. Fields go by name in braces\n(`{Qty} * {Unit price}`); a function the base does not have shows `#ERROR`\nand is named in the editor, so you rewrite that part.\n\n## 1. Check the links\n\nThe base turns a foreign key into a link with a field on the other side\nthat links back, and a table that only pairs two others into a link to many\nrecords. Look at the links you made in NocoDB: if one has no foreign key or\npairing table behind it in your database, add one before you open the base,\nor that link will not appear.\n\n## 2. Open the database as a base\n\n```ts\n// src/routes/api/base/+server.ts\nimport { createBaseEndpoint } from '@svgrid/enterprise/base'\n\n// Your database driver: run parameterized SQL, return the rows.\ndeclare function query(sql: string, params: unknown[]): Promise<Record<string, unknown>[]>\n\nexport const { GET, POST } = createBaseEndpoint({ execute: query })\n```\n\nFor MySQL, pass `dialect: 'mysql'`; `tables` limits the base to the tables\nyou name.\n\n```svelte\n<!-- src/routes/base/+page.svelte (with `export const ssr = false` in +page.ts) -->\n<script lang=\"ts\">\n  import { SvToaster } from '@svgrid/grid'\n  import { SvBase, baseFromEndpoint, enableBase } from '@svgrid/enterprise/base'\n\n  enableBase()\n  const tables = baseFromEndpoint('/api/base')\n</script>\n\n{#await tables then tables}\n  <SvBase {tables} editable sortable columnAdder fieldMenu />\n{/await}\n<SvToaster />\n```\n\n## 3. Views, automations and access\n\nRecreate the views, including a Gantt for the timeline and Gantt views that\nwere on NocoDB's Business plan:\n\n```ts\nimport type { FieldView } from '@svgrid/enterprise/base'\n\nconst views: FieldView[] = [\n  { id: 'all', name: 'All tasks', type: 'grid', color: { mode: 'field', field: 'status' } },\n  { id: 'board', name: 'Board', type: 'kanban', stackBy: 'status' },\n  { id: 'plan', name: 'Plan', type: 'gantt', dateField: 'start', endField: 'due' },\n]\n```\n\nWorkflows become automations: a record created or changed, a condition, a\nform, a button or a schedule sets them off, and they update or create\nrecords, call webhooks and send email. Integration nodes (Slack, Gmail and\nso on) become webhook calls or actions you register with\n`registerAutomationAction`. See [Automations](./base/automations.md).\n\nNocoDB's roles move into the endpoint's `authorize`, or into row level\nsecurity on Supabase.\n\n## What you give up\n\n- The roles screen and sharing links. Access rules live in your server or\n  database.\n- The long record revision history. The record shows the changes made in\n  the session, and the endpoint's `audit` hook can log every write.\n- Workflow integration nodes; they become webhooks and actions you write.\n- A no-code setup path: someone adds `<SvBase>` to a Svelte app.\n\nSvGrid Base is part of the Suite edition of `@svgrid/enterprise` ($999 per\ndeveloper). It runs without a key during an evaluation, with a watermark.\n\n## See also\n\n- [SvGrid vs NocoDB](https://svgrid.com/compare/nocodb/): the side-by-side comparison with sources.\n- [From a database to an app](./base/quick-start.md): what the base reads from your database.\n- [Keep a base in a database](./base/data.md): how the writes, links and realtime work.\n- [Field types](./fields.md): every type and its properties.\n"
+        "markdown": "# Migrating from NocoDB\n\nNocoDB is an app your team signs into, and outside it a shared view shows up\nonly as an iframe. [SvGrid Base](./base/start.md) is the same kind of table\ndatabase shipped as a Svelte 5 component: `<SvBase>` renders the views\ninside your own app, on your own database, and writes every change back.\n\n> Estimated effort: **1-2 hours** per base on PostgreSQL or MySQL; more to\n> rebuild workflows.\n\n<!-- facts:start nocodb -->\n> **Facts, checked 14 Oct 2026.** `@svgrid/grid` 3.0.3, MIT, last published 11 Sep 2026, 16,900 npm downloads in the 30 days to 10 Sep 2026. NocoDB pricing, as its site states it: NocoDB self-hosted Community is $0 under the Sustainable Use License. nocodb.com/pricing lists cloud Plus at $12 per seat per month billed annually ($15 monthly), Business at $24 per seat per month billed annually ($30 monthly), Scale at $45 per seat per month billed annually with 3 minimum seats, and Enterprise on request; self-hosted Business and Scale are priced the same per seat (https://nocodb.com/pricing, read 14 Oct 2026). SvGrid: SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT. Side by side, with sources: [SvGrid vs NocoDB](https://svgrid.com/compare/nocodb/).\n<!-- facts:end -->\n\n## Two starting points\n\n- **NocoDB was connected to your own PostgreSQL or MySQL.** The tables are\n  already yours. Point the base at the same database (step 2) and you are\n  most of the way there.\n- **The tables live in NocoDB's own database.** Download each table as CSV\n  (NocoDB also offers JSON and Excel), load it into tables of yours, and\n  continue from step 2.\n  [Load the tables into your database](./migrating-from-airtable.md#2-load-the-tables-into-your-database)\n  has the SQL for the keys, a link to one record and a link to many.\n\n## What maps to what\n\n| NocoDB | SvGrid Base |\n| --- | --- |\n| A base | A `<SvBase tables>` with one tab per table |\n| A table | A table in your database, opened as a `BaseTable` |\n| A view | A `FieldView`: `grid`, `kanban`, `calendar`, `gallery`, `chart` or `form` |\n| A workflow or webhook | An automation in the view bar, or `createAutomationServer` on your server |\n| Roles | Your app's login, and `authorize` on the endpoint |\n| Record comments | `setRecordComments`, stored where your app stores them |\n\n| NocoDB field | `fieldType` |\n| --- | --- |\n| Single line text, long text | `text`, `longText` |\n| Link to another record | `link` |\n| Lookup, rollup | `lookup`, `rollup`; a rollup with the count function can be `count` |\n| Formula | `formula` |\n| Number, currency, percent | `number` with the matching `format` |\n| Rating, duration | `rating`, `duration` |\n| Checkbox | `checkbox` |\n| Date | `date` (with `time: true` for a date and time) |\n| Created time, last modified time | `createdTime`, `lastModifiedTime` |\n| Created by, last modified by | `createdBy`, `lastModifiedBy` |\n| User | `user` |\n| Attachment | `attachment` |\n| Single select, multi select | `singleSelect`, `multiSelect` |\n| Barcode, button | `barcode`, `button` |\n| Auto number | `autoNumber` |\n| Email, URL, phone number | `email`, `url`, `phone` |\n\nPaste each formula into the field editor. Fields go by name in braces\n(`{Qty} * {Unit price}`); a function the base does not have shows `#ERROR`\nand is named in the editor, so you rewrite that part.\n\n## 1. Check the links\n\nThe base turns a foreign key into a link with a field on the other side\nthat links back, and a table that only pairs two others into a link to many\nrecords. Look at the links you made in NocoDB: if one has no foreign key or\npairing table behind it in your database, add one before you open the base,\nor that link will not appear.\n\n## 2. Open the database as a base\n\n```ts\n// src/routes/api/base/+server.ts\nimport { createBaseEndpoint } from '@svgrid/enterprise/base'\n\n// Your database driver: run parameterized SQL, return the rows.\ndeclare function query(sql: string, params: unknown[]): Promise<Record<string, unknown>[]>\n\nexport const { GET, POST } = createBaseEndpoint({ execute: query })\n```\n\nFor MySQL, pass `dialect: 'mysql'`; `tables` limits the base to the tables\nyou name.\n\n```svelte\n<!-- src/routes/base/+page.svelte (with `export const ssr = false` in +page.ts) -->\n<script lang=\"ts\">\n  import { SvToaster } from '@svgrid/grid'\n  import { SvBase, baseFromEndpoint, enableBase } from '@svgrid/enterprise/base'\n\n  enableBase()\n  const tables = baseFromEndpoint('/api/base')\n</script>\n\n{#await tables then tables}\n  <SvBase {tables} editable sortable columnAdder fieldMenu />\n{/await}\n<SvToaster />\n```\n\n## 3. Views, automations and access\n\nRecreate the views you used:\n\n```ts\nimport type { FieldView } from '@svgrid/enterprise/base'\n\nconst views: FieldView[] = [\n  { id: 'all', name: 'All tasks', type: 'grid', color: { mode: 'field', field: 'status' } },\n  { id: 'board', name: 'Board', type: 'kanban', stackBy: 'status' },\n  { id: 'due', name: 'Due dates', type: 'calendar', dateField: 'due' },\n]\n```\n\nWorkflows become automations: a record created or changed, a condition, a\nform, a button or a schedule sets them off, and they update or create\nrecords, call webhooks and send email. Integration nodes (Slack, Gmail and\nso on) become webhook calls or actions you register with\n`registerAutomationAction`. See [Automations](./base/automations.md).\n\nNocoDB's roles move into the endpoint's `authorize`, or into row level\nsecurity on Supabase.\n\n## What you give up\n\n- The roles screen and sharing links. Access rules live in your server or\n  database.\n- The long record revision history. The record shows the changes made in\n  the session, and the endpoint's `audit` hook can log every write.\n- Workflow integration nodes; they become webhooks and actions you write.\n- A no-code setup path: someone adds `<SvBase>` to a Svelte app.\n\nSvGrid Base is part of the Suite edition of `@svgrid/enterprise` ($999 per\ndeveloper). It runs without a key during an evaluation, with a watermark.\n\n## See also\n\n- [SvGrid vs NocoDB](https://svgrid.com/compare/nocodb/): the side-by-side comparison with sources.\n- [From a database to an app](./base/quick-start.md): what the base reads from your database.\n- [Keep a base in a database](./base/data.md): how the writes, links and realtime work.\n- [Field types](./fields.md): every type and its properties.\n"
     },
     {
         "slug": "help/migrating-from-primevue-datatable",
@@ -7220,14 +7220,14 @@ export const docs = [
         "path": "docs/_data/comparisons/airtable.json",
         "title": "SvGrid vs Airtable",
         "section": "Comparisons",
-        "markdown": "# SvGrid vs Airtable\n\nCanonical URL: https://svgrid.com/compare/airtable/\nFacts verified: 2026-10-14\nCompetitor site: https://www.airtable.com/\n\nAirtable is a hosted table-database app: bases of linked tables with views, interfaces, automations and AI, sold per seat as a cloud service.\n\n## Verdict\n\nAirtable is the pick when a team wants the finished service and is happy to work in it. SvGrid Base is the pick when the same experience has to live inside your own Svelte app, on your servers and your database, with no per-seat bill and no Airtable branding.\n\nMigration guide: moving from Airtable to SvGrid: https://svgrid.com/docs/help/migrating-from-airtable/\n\n## At a glance\n\n| Fact | SvGrid | Airtable | Checked |\n| --- | --- | --- | --- |\n| What it is | A Svelte 5 component (<SvBase>) inside your own app, on your database | Hosted web app (cloud) | 14 Oct 2026 |\n| Pricing | SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT | Airtable Free has no cost. airtable.com/pricing lists Team at $20 per seat per month billed annually ($24 monthly) and Business at $45 per seat per month billed annually ($54 monthly); Enterprise Scale pricing is custom. Read-only collaborators are not charged on Team or Business | 14 Oct 2026 |\n\n## Overview\n\nAirtable organizes data into bases of linked tables with typed fields, and shows them through grid, form, calendar, gallery, Kanban, list, timeline and Gantt views. On top of a base it offers Interface Designer for app-like pages, automations with record, schedule, form and webhook triggers, Omni and other AI features, comments, revision history and native mobile apps. It is a cloud service only: Airtable says it does not plan to offer a self-hosted version.\n\nSvGrid Base is that kind of table database shipped as a Svelte 5 component in @svgrid/enterprise. You add <SvBase> to a page, give it tables or let it read your database, and your users work with typed fields, saved views, filters, groups, row colors, linked records, automations and records with comments, inside your app and under your login. The records stay in the database you already run.\n\n## Looking for an Airtable alternative for Svelte?\n\nMost searches for an Airtable alternative come from developers who like what Airtable does but cannot use it where they need it: inside their own product, for their own customers, on data that has to stay in their database. Airtable is cloud-only and its embed is a read-only iframe. SvGrid Base gives you the parts people know from it (typed fields, linked records, grid, Kanban, calendar, gallery, Gantt and form views, automations, an expanded record with comments) as one Svelte component, <SvBase>, that you host in your app and point at Postgres, MySQL, SQLite, Supabase or your REST API.\n\n## What they have in common\n\n- Bases of several tables, linked to each other, with lookup, rollup and count fields.\n- Typed fields: single and multiple select, user, date, attachment, rating, barcode, button, formula, autonumber, created and last-modified.\n- Grid, form, calendar, gallery, Kanban and Gantt views, each with its own filters, sorts, groups and hidden fields.\n- Automations triggered by a new record, a change, a matching condition, a form, a button or a schedule.\n- An expanded record with every field and its comments.\n- Row colors driven by a field or by conditions.\n\n## Where SvGrid is stronger\n\n- Runs where you need it: inside your own Svelte app, on your servers, with your login; Airtable is cloud-only and its embed is a read-only iframe.\n- Your data stays in your database: Postgres, MySQL, SQLite, Supabase or your API, read and written through your own endpoint, with no data residency question.\n- No Airtable branding to remove: the base takes your app's look from --sg-* tokens.\n- Automations run in the browser or on your server with no monthly run quota, and their secrets never leave your server.\n- No record cap set by a plan: the database decides, and the page loads up to a limit you choose.\n- Priced per developer, not per seat: the people who use the app do not each need a licence.\n\n## Where Airtable is stronger\n\n- A finished service: sign up and work, with nothing to host and no developer needed.\n- Interface Designer, Omni AI and AI credits on every plan, and a large set of automation integrations (Slack, Google Workspace, Microsoft Teams, Salesforce, Jira and more).\n- Native iOS and Android apps, and a list and inbox view.\n- Field and table editing permissions, sharing, and record revision history kept for up to three years on Enterprise Scale.\n- Import from CSV, Excel, Google Sheets and Smartsheet, and a public REST API with webhooks.\n- A large template gallery and community.\n\n## Feature by feature\n\nYes: 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.\n\n| Feature | SvGrid | Airtable |\n| --- | --- | --- |\n| Runs inside your own app's pages | Yes - a Svelte 5 component, <SvBase> | No - a live, read-only iframe of a view or base |\n| Edit records from the embedded view | Yes | No - embeds are read-only |\n| Runs on your own servers | Yes - it is part of your app | No - cloud SaaS only, no self-hosted option planned |\n| Data stays in your own database | Yes - Postgres, MySQL, SQLite, Supabase or a REST API | No - stored in Airtable's cloud; region choice on Enterprise Scale |\n| Grid, form, gallery, Kanban and calendar views | Yes | Yes - every plan |\n| Gantt and timeline views | Yes - Gantt view with dependencies and progress | Paid tier - Team plan and up |\n| Linked records, lookup, rollup, count and formula fields | Yes | Yes |\n| Barcode, button and autonumber fields | Yes | Yes |\n| Automations | Yes - in the browser or on your server, no run quota | Partial - runs metered per month by plan |\n| Call your own webhook from an automation | Yes - POST the record to any URL, secrets read on the server | Partial - through a run-a-script action, not on Free |\n| Record comments | Yes - stored wherever your app stores them | Yes - every plan |\n| Record revision history | Partial - this session's changes in the record; a server audit hook logs every write | Yes - kept from two weeks to three years by plan |\n| Field and table editing permissions | Partial - your server's authorize hook or the database's row level security; no permissions screen | Paid tier - Team plan and up |\n| Changes from other users appear live | Partial - through a realtime source (Supabase Realtime, a WebSocket, a poll) | Yes |\n| Import CSV or Excel files | Partial - paste a range, or load the file into your database and open it | Yes - CSV, Excel, Google Sheets and Smartsheet |\n| Your branding only | Yes - your app's look through --sg-* tokens | No - not possible to remove all Airtable branding |\n| Records per table | Partial - the page holds a table's records, up to a limit you set (10,000 by default) | Partial - a per-base cap set by the plan |\n| Works offline | Yes - with Postgres in the browser (PGlite) | No - offline access is not supported |\n| Native mobile apps | No - a web component in your app | Yes - iOS and Android |\n| Usable with no developer | No - a developer adds it to an app | Yes - sign up and start |\n\n## When to choose SvGrid\n\n- The table database has to live inside your own Svelte or SvelteKit app, for your users or your customers, under your login and your look.\n- The data must stay in your database or on your servers.\n- You do not want a per-seat bill that grows with every person who uses the app.\n- You need automations whose secrets and side effects stay on your server.\n\n## When to choose Airtable\n\n- You want a finished service a team can use today, with no developer and nothing to host.\n- You want built-in AI, interfaces and a wide set of ready-made automation integrations.\n- You need native mobile apps.\n- You want permissions, sharing and long revision history handled for you.\n\n## Migration effort\n\nEstimated effort: half a day for a typical base, plus rebuilding automations.\n\nWhat you give up:\n\n- The hosted service: someone has to add <SvBase> to a Svelte app and run the database it reads.\n- Interfaces, Omni and the AI credits; the screens around the base are your own Svelte pages.\n- Native mobile apps and the list and inbox views.\n- The permissions screen, sharing links and long revision history; access rules move into your server or database, and your audit hook keeps the history.\n\nMigration guide: moving from Airtable to SvGrid: https://svgrid.com/docs/help/migrating-from-airtable/\n\n## Live example\n\nProject Tracker: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/504-project-tracker/\n\n## The bottom line\n\nAirtable is the reference table database for a team that wants a finished cloud service. When that experience has to be part of your own product, SvGrid Base fits better: it is a Svelte component you host, it works on the database you already run, it carries your branding and no one else's, and it is priced per developer rather than per seat.\n\n## Frequently asked questions\n\n### Can I put Airtable inside my own app?\n\nAirtable lets you embed a live, read-only copy of a view or base as an iframe, and Business and Enterprise Scale plans can embed a single interface page. It is a cloud service only, so the data and the app stay on Airtable. SvGrid Base is a Svelte component: its views render and edit records in your own pages, behind your login, on your database.\n\n### Is there a self-hosted Airtable?\n\nNot from Airtable: its technical requirements page says it is a cloud SaaS product with no plan to offer an on-premise or self-hosted version. SvGrid Base runs wherever your Svelte app runs, and keeps records in Postgres, MySQL, SQLite, Supabase or behind your REST API.\n\n### Which Airtable features does SvGrid Base have?\n\nSeveral linked tables per base; single and multiple select, user, date, attachment, rating, barcode, button, formula, autonumber, lookup, rollup and count fields; grid, Kanban, calendar, gallery, Gantt, chart and form views with their own filters, sorts and groups; row colors; automations with record, form, button and schedule triggers and update, create, email and webhook actions; and an expanded record with comments.\n\n### How do I move a base from Airtable to SvGrid Base?\n\nDownload each view as CSV, load the files into your own database tables, add foreign keys for the links, and point createBaseEndpoint at the database: the base opens with a tab per table, typed fields and links. Views and automations are rebuilt in a few lines of configuration. The migration guide has the steps.\n\n### How is SvGrid Base priced compared with Airtable?\n\nAirtable is priced per seat per month; 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.\n\n### What does SvGrid Base not do that Airtable does?\n\nIt is not a hosted service and needs a developer to add it to an app. There are no interfaces, no built-in AI credits, no native mobile apps, no permissions screen or sharing links (access rules live in your server or database), no long revision history kept for you, and every table's records are held in the page up to a limit you set.\n\n### Is SvGrid a good Airtable alternative for Svelte?\n\nMost searches for an Airtable alternative come from developers who like what Airtable does but cannot use it where they need it: inside their own product, for their own customers, on data that has to stay in their database. Airtable is cloud-only and its embed is a read-only iframe. SvGrid Base gives you the parts people know from it (typed fields, linked records, grid, Kanban, calendar, gallery, Gantt and form views, automations, an expanded record with comments) as one Svelte component, <SvBase>, that you host in your app and point at Postgres, MySQL, SQLite, Supabase or your REST API.\n\n## Related comparisons and docs\n\n- [SvGrid vs Baserow](https://svgrid.com/compare/baserow/)\n- [SvGrid vs NocoDB](https://svgrid.com/compare/nocodb/)\n- [Build a project tracker](https://svgrid.com/docs/help/base/start/)\n- [Ready-to-use bases](https://svgrid.com/docs/help/base/templates/)\n- [From a database to an app](https://svgrid.com/docs/help/base/quick-start/)\n- [Automations](https://svgrid.com/docs/help/base/automations/)\n- [Field types](https://svgrid.com/docs/help/fields/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 14 Oct 2026. Feature and pricing statements come from the pages listed below.\n\n- at-pricing: Free plan at no cost with up to 5 creators or editors; Team $20 per user per month billed annually; Business $45 per user per month billed annually; Enterprise Scale pricing is custom; read-only collaborators are not charged on Team or Business (checked 14 Oct 2026) https://airtable.com/pricing\n- at-plans: Team $24 per collaborator per month billed monthly or $20 billed annually; Business $54 monthly; records per base 1,000 on Free, 50,000 on Team and 125,000 on Business; Team and above include timeline and Gantt views (checked 14 Oct 2026) https://support.airtable.com/articles/2277136852-airtable-plans-overview\n- at-embed: Embedding places a live, read-only copy of a view or base inside another web page as an HTML iframe (checked 14 Oct 2026) https://support.airtable.com/articles/6973404921-embedding-airtable-views-and-bases\n- at-tech: Airtable is a cloud-based SaaS product and does not plan on offering an on-premise or self-hosted solution; offline access is not supported (checked 14 Oct 2026) https://support.airtable.com/articles/5016991853-airtable-technical-requirements\n- at-residency: Data residency in the United States by default, Europe or Australia for Enterprise Scale customers; some data stays in US data centers whatever the region (checked 14 Oct 2026) https://support.airtable.com/articles/3345708696-data-residency-at-airtable\n- at-views: Grid is the default view; other types include form, calendar, gallery, Kanban, timeline, list and Gantt (checked 14 Oct 2026) https://support.airtable.com/articles/5189551686-getting-started-with-airtable-views\n- at-fields: Field types include linked record, lookup, rollup, count, formula, attachment, rating, barcode, button, autonumber, created and last modified time and by, user, duration, currency and percent (checked 14 Oct 2026) https://support.airtable.com/articles/4808831313-supported-field-types-in-airtable-overview\n- at-automations: Triggers include record created, updated, entering a view or matching a condition, form submitted, scheduled time, webhook received and button clicked; actions include record actions, send email and run a script, unavailable on Free; runs per workspace per month from 100 on Free to 500,000 on Enterprise Scale (checked 14 Oct 2026) https://support.airtable.com/articles/3669392397-getting-started-with-airtable-automations\n- at-comments: Commenting is available on all plan types for collaborators with commenter permissions or higher (checked 14 Oct 2026) https://support.airtable.com/articles/1999477400-commenting-in-airtable\n- at-history: Record revision history covers the past 2 weeks on Free, 1 year on Team, 2 years on Business and 3 years on Enterprise Scale (checked 14 Oct 2026) https://support.airtable.com/articles/3516802427-record-level-revision-history-in-airtable\n- at-permissions: Field and table editing permissions are available on Team, Business and Enterprise Scale and do not affect who can see information (checked 14 Oct 2026) https://support.airtable.com/articles/2296468758-airtable-field-and-table-editing-permissions\n- at-guide: Teams work from the same data sources, updated in real time (checked 14 Oct 2026) https://www.airtable.com/guides/start/what-is-airtable\n- at-import: Native import of CSV and Excel files, and imports from Google Sheets and Smartsheet, on all plan types (checked 14 Oct 2026) https://support.airtable.com/articles/9412806945-importing-third-party-data-into-airtable\n- at-forms: The Airtable label can be removed from forms on paid plans, but it is not currently possible to remove all Airtable branding or add custom branding within the Airtable UI (checked 14 Oct 2026) https://support.airtable.com/articles/8588280258-getting-started-with-airtable-form-views\n- at-mobile: iOS and Android apps exist; automations, Gantt, timeline and CSV import and export are not available in them (checked 14 Oct 2026) https://support.airtable.com/articles/9609457174-airtable-desktop-and-mobile-feature-differences\n"
+        "markdown": "# SvGrid vs Airtable\n\nCanonical URL: https://svgrid.com/compare/airtable/\nFacts verified: 2026-10-14\nCompetitor site: https://www.airtable.com/\n\nAirtable is a hosted table-database app: bases of linked tables with views, interfaces, automations and AI, sold per seat as a cloud service.\n\n## Verdict\n\nAirtable is the pick when a team wants the finished service and is happy to work in it. SvGrid Base is the pick when the same experience has to live inside your own Svelte app, on your servers and your database, with no per-seat bill and no Airtable branding.\n\nMigration guide: moving from Airtable to SvGrid: https://svgrid.com/docs/help/migrating-from-airtable/\n\n## At a glance\n\n| Fact | SvGrid | Airtable | Checked |\n| --- | --- | --- | --- |\n| What it is | A Svelte 5 component (<SvBase>) inside your own app, on your database | Hosted web app (cloud) | 14 Oct 2026 |\n| Pricing | SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT | Airtable Free has no cost. airtable.com/pricing lists Team at $20 per seat per month billed annually ($24 monthly) and Business at $45 per seat per month billed annually ($54 monthly); Enterprise Scale pricing is custom. Read-only collaborators are not charged on Team or Business | 14 Oct 2026 |\n\n## Overview\n\nAirtable organizes data into bases of linked tables with typed fields, and shows them through grid, form, calendar, gallery, Kanban, list, timeline and Gantt views. On top of a base it offers Interface Designer for app-like pages, automations with record, schedule, form and webhook triggers, Omni and other AI features, comments, revision history and native mobile apps. It is a cloud service only: Airtable says it does not plan to offer a self-hosted version.\n\nSvGrid Base is that kind of table database shipped as a Svelte 5 component in @svgrid/enterprise. You add <SvBase> to a page, give it tables or let it read your database, and your users work with typed fields, saved views, filters, groups, row colors, linked records, automations and records with comments, inside your app and under your login. The records stay in the database you already run.\n\n## Looking for an Airtable alternative for Svelte?\n\nMost searches for an Airtable alternative come from developers who like what Airtable does but cannot use it where they need it: inside their own product, for their own customers, on data that has to stay in their database. Airtable is cloud-only and its embed is a read-only iframe. SvGrid Base gives you the parts people know from it (typed fields, linked records, grid, Kanban, calendar, gallery and form views, automations, an expanded record with comments) as one Svelte component, <SvBase>, that you host in your app and point at Postgres, MySQL, SQLite, Supabase or your REST API.\n\n## What they have in common\n\n- Bases of several tables, linked to each other, with lookup, rollup and count fields.\n- Typed fields: single and multiple select, user, date, attachment, rating, barcode, button, formula, autonumber, created and last-modified.\n- Grid, form, calendar, gallery and Kanban views, each with its own filters, sorts, groups and hidden fields.\n- Automations triggered by a new record, a change, a matching condition, a form, a button or a schedule.\n- An expanded record with every field and its comments.\n- Row colors driven by a field or by conditions.\n\n## Where SvGrid is stronger\n\n- Runs where you need it: inside your own Svelte app, on your servers, with your login; Airtable is cloud-only and its embed is a read-only iframe.\n- Your data stays in your database: Postgres, MySQL, SQLite, Supabase or your API, read and written through your own endpoint, with no data residency question.\n- No Airtable branding to remove: the base takes your app's look from --sg-* tokens.\n- Automations run in the browser or on your server with no monthly run quota, and their secrets never leave your server.\n- No record cap set by a plan: the database decides, and the page loads up to a limit you choose.\n- Priced per developer, not per seat: the people who use the app do not each need a licence.\n\n## Where Airtable is stronger\n\n- A finished service: sign up and work, with nothing to host and no developer needed.\n- Interface Designer, Omni AI and AI credits on every plan, and a large set of automation integrations (Slack, Google Workspace, Microsoft Teams, Salesforce, Jira and more).\n- Native iOS and Android apps, and a list and inbox view.\n- Field and table editing permissions, sharing, and record revision history kept for up to three years on Enterprise Scale.\n- Import from CSV, Excel, Google Sheets and Smartsheet, and a public REST API with webhooks.\n- A large template gallery and community.\n\n## Feature by feature\n\nYes: 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.\n\n| Feature | SvGrid | Airtable |\n| --- | --- | --- |\n| Runs inside your own app's pages | Yes - a Svelte 5 component, <SvBase> | No - a live, read-only iframe of a view or base |\n| Edit records from the embedded view | Yes | No - embeds are read-only |\n| Runs on your own servers | Yes - it is part of your app | No - cloud SaaS only, no self-hosted option planned |\n| Data stays in your own database | Yes - Postgres, MySQL, SQLite, Supabase or a REST API | No - stored in Airtable's cloud; region choice on Enterprise Scale |\n| Grid, form, gallery, Kanban and calendar views | Yes | Yes - every plan |\n| Linked records, lookup, rollup, count and formula fields | Yes | Yes |\n| Barcode, button and autonumber fields | Yes | Yes |\n| Automations | Yes - in the browser or on your server, no run quota | Partial - runs metered per month by plan |\n| Call your own webhook from an automation | Yes - POST the record to any URL, secrets read on the server | Partial - through a run-a-script action, not on Free |\n| Record comments | Yes - stored wherever your app stores them | Yes - every plan |\n| Record revision history | Partial - this session's changes in the record; a server audit hook logs every write | Yes - kept from two weeks to three years by plan |\n| Field and table editing permissions | Partial - your server's authorize hook or the database's row level security; no permissions screen | Paid tier - Team plan and up |\n| Changes from other users appear live | Partial - through a realtime source (Supabase Realtime, a WebSocket, a poll) | Yes |\n| Import CSV or Excel files | Partial - paste a range, or load the file into your database and open it | Yes - CSV, Excel, Google Sheets and Smartsheet |\n| Your branding only | Yes - your app's look through --sg-* tokens | No - not possible to remove all Airtable branding |\n| Records per table | Partial - the page holds a table's records, up to a limit you set (10,000 by default) | Partial - a per-base cap set by the plan |\n| Works offline | Yes - with Postgres in the browser (PGlite) | No - offline access is not supported |\n| Native mobile apps | No - a web component in your app | Yes - iOS and Android |\n| Usable with no developer | No - a developer adds it to an app | Yes - sign up and start |\n\n## When to choose SvGrid\n\n- The table database has to live inside your own Svelte or SvelteKit app, for your users or your customers, under your login and your look.\n- The data must stay in your database or on your servers.\n- You do not want a per-seat bill that grows with every person who uses the app.\n- You need automations whose secrets and side effects stay on your server.\n\n## When to choose Airtable\n\n- You want a finished service a team can use today, with no developer and nothing to host.\n- You want built-in AI, interfaces and a wide set of ready-made automation integrations.\n- You need native mobile apps.\n- You want permissions, sharing and long revision history handled for you.\n\n## Migration effort\n\nEstimated effort: half a day for a typical base, plus rebuilding automations.\n\nWhat you give up:\n\n- The hosted service: someone has to add <SvBase> to a Svelte app and run the database it reads.\n- Interfaces, Omni and the AI credits; the screens around the base are your own Svelte pages.\n- Native mobile apps and the list and inbox views.\n- The permissions screen, sharing links and long revision history; access rules move into your server or database, and your audit hook keeps the history.\n\nMigration guide: moving from Airtable to SvGrid: https://svgrid.com/docs/help/migrating-from-airtable/\n\n## Live example\n\nProject Tracker: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/504-project-tracker/\n\n## The bottom line\n\nAirtable is the reference table database for a team that wants a finished cloud service. When that experience has to be part of your own product, SvGrid Base fits better: it is a Svelte component you host, it works on the database you already run, it carries your branding and no one else's, and it is priced per developer rather than per seat.\n\n## Frequently asked questions\n\n### Can I put Airtable inside my own app?\n\nAirtable lets you embed a live, read-only copy of a view or base as an iframe, and Business and Enterprise Scale plans can embed a single interface page. It is a cloud service only, so the data and the app stay on Airtable. SvGrid Base is a Svelte component: its views render and edit records in your own pages, behind your login, on your database.\n\n### Is there a self-hosted Airtable?\n\nNot from Airtable: its technical requirements page says it is a cloud SaaS product with no plan to offer an on-premise or self-hosted version. SvGrid Base runs wherever your Svelte app runs, and keeps records in Postgres, MySQL, SQLite, Supabase or behind your REST API.\n\n### Which Airtable features does SvGrid Base have?\n\nSeveral linked tables per base; single and multiple select, user, date, attachment, rating, barcode, button, formula, autonumber, lookup, rollup and count fields; grid, Kanban, calendar, gallery, chart and form views with their own filters, sorts and groups; row colors; automations with record, form, button and schedule triggers and update, create, email and webhook actions; and an expanded record with comments.\n\n### How do I move a base from Airtable to SvGrid Base?\n\nDownload each view as CSV, load the files into your own database tables, add foreign keys for the links, and point createBaseEndpoint at the database: the base opens with a tab per table, typed fields and links. Views and automations are rebuilt in a few lines of configuration. The migration guide has the steps.\n\n### How is SvGrid Base priced compared with Airtable?\n\nAirtable is priced per seat per month; 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.\n\n### What does SvGrid Base not do that Airtable does?\n\nIt is not a hosted service and needs a developer to add it to an app. There are no interfaces, no built-in AI credits, no native mobile apps, no permissions screen or sharing links (access rules live in your server or database), no long revision history kept for you, and every table's records are held in the page up to a limit you set.\n\n### Is SvGrid a good Airtable alternative for Svelte?\n\nMost searches for an Airtable alternative come from developers who like what Airtable does but cannot use it where they need it: inside their own product, for their own customers, on data that has to stay in their database. Airtable is cloud-only and its embed is a read-only iframe. SvGrid Base gives you the parts people know from it (typed fields, linked records, grid, Kanban, calendar, gallery and form views, automations, an expanded record with comments) as one Svelte component, <SvBase>, that you host in your app and point at Postgres, MySQL, SQLite, Supabase or your REST API.\n\n## Related comparisons and docs\n\n- [SvGrid vs Baserow](https://svgrid.com/compare/baserow/)\n- [SvGrid vs NocoDB](https://svgrid.com/compare/nocodb/)\n- [Build a project tracker](https://svgrid.com/docs/help/base/start/)\n- [Ready-to-use bases](https://svgrid.com/docs/help/base/templates/)\n- [From a database to an app](https://svgrid.com/docs/help/base/quick-start/)\n- [Automations](https://svgrid.com/docs/help/base/automations/)\n- [Field types](https://svgrid.com/docs/help/fields/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 14 Oct 2026. Feature and pricing statements come from the pages listed below.\n\n- at-pricing: Free plan at no cost with up to 5 creators or editors; Team $20 per user per month billed annually; Business $45 per user per month billed annually; Enterprise Scale pricing is custom; read-only collaborators are not charged on Team or Business (checked 14 Oct 2026) https://airtable.com/pricing\n- at-plans: Team $24 per collaborator per month billed monthly or $20 billed annually; Business $54 monthly; records per base 1,000 on Free, 50,000 on Team and 125,000 on Business; Team and above include timeline and Gantt views (checked 14 Oct 2026) https://support.airtable.com/articles/2277136852-airtable-plans-overview\n- at-embed: Embedding places a live, read-only copy of a view or base inside another web page as an HTML iframe (checked 14 Oct 2026) https://support.airtable.com/articles/6973404921-embedding-airtable-views-and-bases\n- at-tech: Airtable is a cloud-based SaaS product and does not plan on offering an on-premise or self-hosted solution; offline access is not supported (checked 14 Oct 2026) https://support.airtable.com/articles/5016991853-airtable-technical-requirements\n- at-residency: Data residency in the United States by default, Europe or Australia for Enterprise Scale customers; some data stays in US data centers whatever the region (checked 14 Oct 2026) https://support.airtable.com/articles/3345708696-data-residency-at-airtable\n- at-views: Grid is the default view; other types include form, calendar, gallery, Kanban, timeline, list and Gantt (checked 14 Oct 2026) https://support.airtable.com/articles/5189551686-getting-started-with-airtable-views\n- at-fields: Field types include linked record, lookup, rollup, count, formula, attachment, rating, barcode, button, autonumber, created and last modified time and by, user, duration, currency and percent (checked 14 Oct 2026) https://support.airtable.com/articles/4808831313-supported-field-types-in-airtable-overview\n- at-automations: Triggers include record created, updated, entering a view or matching a condition, form submitted, scheduled time, webhook received and button clicked; actions include record actions, send email and run a script, unavailable on Free; runs per workspace per month from 100 on Free to 500,000 on Enterprise Scale (checked 14 Oct 2026) https://support.airtable.com/articles/3669392397-getting-started-with-airtable-automations\n- at-comments: Commenting is available on all plan types for collaborators with commenter permissions or higher (checked 14 Oct 2026) https://support.airtable.com/articles/1999477400-commenting-in-airtable\n- at-history: Record revision history covers the past 2 weeks on Free, 1 year on Team, 2 years on Business and 3 years on Enterprise Scale (checked 14 Oct 2026) https://support.airtable.com/articles/3516802427-record-level-revision-history-in-airtable\n- at-permissions: Field and table editing permissions are available on Team, Business and Enterprise Scale and do not affect who can see information (checked 14 Oct 2026) https://support.airtable.com/articles/2296468758-airtable-field-and-table-editing-permissions\n- at-guide: Teams work from the same data sources, updated in real time (checked 14 Oct 2026) https://www.airtable.com/guides/start/what-is-airtable\n- at-import: Native import of CSV and Excel files, and imports from Google Sheets and Smartsheet, on all plan types (checked 14 Oct 2026) https://support.airtable.com/articles/9412806945-importing-third-party-data-into-airtable\n- at-forms: The Airtable label can be removed from forms on paid plans, but it is not currently possible to remove all Airtable branding or add custom branding within the Airtable UI (checked 14 Oct 2026) https://support.airtable.com/articles/8588280258-getting-started-with-airtable-form-views\n- at-mobile: iOS and Android apps exist; automations, Gantt, timeline and CSV import and export are not available in them (checked 14 Oct 2026) https://support.airtable.com/articles/9609457174-airtable-desktop-and-mobile-feature-differences\n"
     },
     {
         "slug": "compare/baserow",
         "path": "docs/_data/comparisons/baserow.json",
         "title": "SvGrid vs Baserow",
         "section": "Comparisons",
-        "markdown": "# SvGrid vs Baserow\n\nCanonical URL: https://svgrid.com/compare/baserow/\nFacts verified: 2026-10-14\nCompetitor site: https://baserow.io/\n\nBaserow is an open-source table-database app with an application builder and automations, run on its cloud or self-hosted with Docker on PostgreSQL.\n\n## Verdict\n\nBaserow is the pick for a team that wants an open-source app to sign into, self-hosted for free. SvGrid Base is the pick when the table database has to be part of your own Svelte app: editable in your pages, on your database, with Kanban, calendar, Gantt and comments in the one licence.\n\nMigration guide: moving from Baserow to SvGrid: https://svgrid.com/docs/help/migrating-from-baserow/\n\n## At a glance\n\n| Fact | SvGrid | Baserow | Checked |\n| --- | --- | --- | --- |\n| What it is | A Svelte 5 component (<SvBase>) inside your own app, on your database | Hosted web app (cloud), Self-hosted web app (Docker) | 14 Oct 2026 |\n| Pricing | SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT | Baserow's self-hosted open-source edition is free with unlimited rows. baserow.io/pricing lists Premium at $10 per user per month billed yearly ($12 monthly), Advanced at $18 per user per month billed yearly ($22 monthly) and Enterprise on request, at the same prices on cloud and self-hosted; cloud Free is $0 with 3,000 rows per workspace | 14 Oct 2026 |\n\n## Overview\n\nBaserow gives a team tables of typed fields with grid, form and gallery views for free, and Kanban, calendar, timeline and survey views on paid plans. It has linked records with lookups, rollups and counts, formulas, an automation builder with email, HTTP and AI actions, an application builder for portals and internal tools, a REST API and real-time collaboration. The core is MIT; premium and enterprise features need a subscription, self-hosted or on cloud.\n\nSvGrid Base is a table database you ship as part of your own Svelte 5 app. It comes in @svgrid/enterprise: your users get typed fields, saved views, filters, groups, row colors, linked records, automations and an expanded record with comments, and you keep the data in the database you already run. Nothing runs beside your app; the base is a component in it.\n\n## Looking for a Baserow alternative for Svelte?\n\nPeople searching for a Baserow alternative usually want the Baserow experience somewhere Baserow does not go: inside their own product. Baserow can show a public view in an iframe, read-only except for forms, or publish an app made in its application builder on its own domain. SvGrid Base is a Svelte component instead: <SvBase> renders editable grid, Kanban, calendar, gallery, Gantt, chart and form views in your pages, behind your login, and writes every change to your Postgres, MySQL, SQLite, Supabase or REST API.\n\n## What they have in common\n\n- Typed fields with grid, form and gallery views, and saved filters, sorts and groups per view.\n- Linked records between tables, with lookup, rollup and count fields and formulas.\n- Autonumber, created and last-modified fields, and collaborator fields.\n- Automations triggered by record changes, a schedule or a webhook, with email and HTTP actions.\n- Data kept in PostgreSQL.\n- Real-time updates when other people change records.\n\n## Where SvGrid is stronger\n\n- It is a component, not an app: <SvBase> renders inside your own Svelte pages and edits records there, where Baserow's embed is a read-only iframe of a public view.\n- Kanban, calendar, Gantt, chart, row colors and record comments are all in the one Suite licence; Baserow puts Kanban, calendar, timeline, comments and row coloring on paid plans.\n- Works on your own tables: it reads your schema, columns and foreign keys and writes back to them, where Baserow keeps data in its own database and syncs other sources in.\n- No vendor branding to remove: the base takes your app's look from --sg-* tokens.\n- Automations run in the browser or on your server with no credits to count, and their secrets stay on your server.\n- Priced per developer, not per user: the people who use the app do not need seats.\n\n## Where Baserow is stronger\n\n- Open source with an MIT core, and free to self-host with unlimited rows and storage.\n- A finished product with sign-in, workspaces, roles and sharing; no developer needed to start.\n- An application builder for portals and internal tools on top of the data, with custom domains.\n- Long row change history, audit logs on Advanced, and a REST API and MCP server.\n- File import (CSV, Excel, JSON, XML, and Airtable bases) and AI fields and an AI assistant.\n- No record limit per table when self-hosted; SvGrid Base keeps each table's records in the page, up to a configurable limit.\n\n## Feature by feature\n\nYes: 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.\n\n| Feature | SvGrid | Baserow |\n| --- | --- | --- |\n| Runs inside your own app's pages | Yes - a Svelte 5 component, <SvBase> | No - public views embed as an iframe; no UI component or SDK found |\n| Edit records from the embedded view | Yes | No - shared views are read-only except forms |\n| Source licence | Paid tier - commercial (Enterprise Suite); the grid underneath is MIT | Yes - MIT core; premium and enterprise code needs a subscription in production |\n| Works on your existing database | Yes - Postgres, MySQL, SQLite, Supabase or a REST API | Partial - data lives in Baserow's PostgreSQL; a PostgreSQL table syncs in, two-way optional, not real time |\n| Grid, form and gallery views | Yes | Yes - every plan |\n| Kanban and calendar views | Yes | Paid tier - Premium and up |\n| Gantt or timeline view | Yes - Gantt view with dependencies and progress | Paid tier - timeline view on Premium and up |\n| Linked records, lookup, rollup, count and formula fields | Yes | Yes |\n| Autonumber, created and last-modified fields | Yes | Yes |\n| Automations | Yes - in the browser or on your server, no credits | Yes - credits per month on cloud, unlimited self-hosted |\n| Record comments | Yes - stored wherever your app stores them | Paid tier - paid plans |\n| Row colors | Yes - by a field or by conditions, per view | Paid tier - Premium and up |\n| Row change history | Partial - this session's changes in the record; a server audit hook logs every write | Yes - kept by plan on cloud |\n| Who can see and edit what | Partial - your server's authorize hook or the database's row level security; no roles screen | Paid tier - role, field and view permissions on Advanced and Enterprise |\n| Changes from other users appear live | Partial - through a realtime source (Supabase Realtime, a WebSocket, a poll) | Yes |\n| Import CSV or Excel files | Partial - paste a range, or load the file into your database and open it | Yes - CSV, Excel, JSON, XML and Airtable |\n| Your branding only | Yes - your app's look through --sg-* tokens | Paid tier - logo removal on paid plans |\n| Records per table | Partial - the page holds a table's records, up to a limit you set (10,000 by default) | Yes - unlimited self-hosted; capped per workspace on cloud |\n| Usable with no developer | No - a developer adds it to an app | Yes - cloud sign-up or a Docker install |\n\n## When to choose SvGrid\n\n- The table database has to appear, editable, inside your own Svelte or SvelteKit app, under your login and your look.\n- You want Kanban, calendar, Gantt, comments and row colors without per-user paid plans.\n- Your data already lives in Postgres, MySQL, SQLite, Supabase or behind your API and should stay in those tables.\n- You would rather pay per developer than per user.\n\n## When to choose Baserow\n\n- You want an open-source app a team can self-host and use today, with no developer.\n- You need roles, workspaces and sharing managed from a screen.\n- You want an application builder for portals on your own domain without writing a front end.\n- You want file import, AI fields and long row history built in.\n\n## Migration effort\n\nEstimated effort: 1-3 hours per database, plus rebuilding automations.\n\nWhat you give up:\n\n- Workspaces, roles and the sharing screen; who may do what moves into your server's authorize hook or your database's row level security.\n- The application builder; the screens around the base are your own Svelte pages.\n- Long row change history and audit logs kept for you; the base shows a session's changes and your audit hook keeps the rest.\n- File import, AI fields and the AI assistant inside the tool.\n\nMigration guide: moving from Baserow to SvGrid: https://svgrid.com/docs/help/migrating-from-baserow/\n\n## Live example\n\nProject Tracker: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/504-project-tracker/\n\n## The bottom line\n\nBaserow is a good open-source table database for a team that will sign into it, and free to self-host. When the table database belongs inside your own product, SvGrid Base fits better: it renders editable views in your Svelte pages instead of a read-only iframe, keeps the data in the tables you already run, and includes Kanban, calendar, Gantt, comments and row colors in one licence priced per developer.\n\n## Frequently asked questions\n\n### Can I embed Baserow in my own app?\n\nBaserow can embed any publicly shared view with an iframe, and shared views are read-only except form views. Its application builder publishes apps on a domain rather than inside your pages. SvGrid Base is a Svelte component, so its views render and edit records in your own pages, behind your app's login.\n\n### Is SvGrid Base open source like Baserow?\n\nNo. SvGrid Base is commercial and ships in Enterprise Suite of @svgrid/enterprise; the grid it is built on, @svgrid/grid, is MIT. Baserow's core is MIT, and its premium and enterprise directories are under licences that need a subscription in production.\n\n### Can SvGrid Base work on the PostgreSQL database Baserow uses?\n\nNot on Baserow's internal tables, which belong to Baserow. Export each table to CSV, load it into your own PostgreSQL tables, and point createBaseEndpoint at them: it reads the columns and foreign keys and opens the tables with typed fields and links. If your data already lives in your own PostgreSQL and is synced into Baserow, point the base at the source tables directly.\n\n### Which Baserow paid features are included in SvGrid Base?\n\nKanban and calendar views, a timeline (SvGrid Base has a Gantt view with dependencies), row colors and record comments are paid on Baserow and part of SvGrid Base. Role, field and view permissions are Advanced on Baserow; in SvGrid Base they are rules you write in your server or your database.\n\n### How is SvGrid Base priced compared with Baserow?\n\nBaserow's paid plans are per user per month; 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.\n\n### What does SvGrid Base not do that Baserow does?\n\nThere are no workspaces, roles or sharing screen, no application builder, no file import dialog or AI fields in the base itself, no long row history kept for you, 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.\n\n### Is SvGrid a good Baserow alternative for Svelte?\n\nPeople searching for a Baserow alternative usually want the Baserow experience somewhere Baserow does not go: inside their own product. Baserow can show a public view in an iframe, read-only except for forms, or publish an app made in its application builder on its own domain. SvGrid Base is a Svelte component instead: <SvBase> renders editable grid, Kanban, calendar, gallery, Gantt, chart and form views in your pages, behind your login, and writes every change to your Postgres, MySQL, SQLite, Supabase or REST API.\n\n## Related comparisons and docs\n\n- [SvGrid vs Airtable](https://svgrid.com/compare/airtable/)\n- [SvGrid vs NocoDB](https://svgrid.com/compare/nocodb/)\n- [Build a project tracker](https://svgrid.com/docs/help/base/start/)\n- [Ready-to-use bases](https://svgrid.com/docs/help/base/templates/)\n- [Keep a base in a database](https://svgrid.com/docs/help/base/data/)\n- [Automations](https://svgrid.com/docs/help/base/automations/)\n- [Field types](https://svgrid.com/docs/help/fields/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 14 Oct 2026. Feature and pricing statements come from the pages listed below.\n\n- br-pricing: Cloud Free $0 with 3,000 rows per workspace and grid, form and gallery views; Premium $10 per user per month billed yearly or $12 monthly with all views; Advanced $18 billed yearly or $22 monthly with role based permissions and audit logs; Enterprise on request; Kanban, survey, calendar and timeline views and row comments and coloring on Premium and up; the self-hosted tab lists the open source plan free with unlimited rows and storage (checked 14 Oct 2026) https://baserow.io/pricing\n- br-license: Content outside the premium and enterprise directories is under the MIT Expat license; premium code may only be used in production with a valid Baserow Premium Edition subscription (checked 14 Oct 2026) https://gitlab.com/baserow/baserow/-/raw/develop/LICENSE\n- br-sharing: Any publicly shared view can be embedded with an iframe; shared views are read-only except form views; paid subscribers can hide the Baserow logo from shared views (checked 14 Oct 2026) https://baserow.io/user-docs/public-sharing\n- br-datasync: External sources sync into Baserow tables; real-time sync is not available; PostgreSQL sync supports optional two-way sync (checked 14 Oct 2026) https://baserow.io/user-docs/data-sync-in-baserow\n- br-fields: Field types include link-to-table, lookup, count, rollup, formula, autonumber, UUID, created on, last modified, created by, last modified by, duration, file, collaborator, rating and AI prompt (checked 14 Oct 2026) https://baserow.io/user-docs/baserow-field-overview\n- br-automations: Automation triggers include periodic, rows created, updated or deleted, an incoming HTTP request and a manual trigger; actions include sending an email and an HTTP request; cloud automation credits are counted per plan and self-hosted is unlimited (checked 14 Oct 2026) https://baserow.io/user-docs/automation-triggers\n- br-comments: Row comments and mentions are available on paid plans (checked 14 Oct 2026) https://baserow.io/user-docs/row-commenting\n- br-history: Row change history is on every plan with retention that varies by plan (checked 14 Oct 2026) https://baserow.io/user-docs/row-change-history\n- br-permissions: Free and Premium plans offer two workspace-level roles without table-level restrictions; Advanced and Enterprise add roles with granular permissions (checked 14 Oct 2026) https://baserow.io/user-docs/permissions-overview\n- br-faq: Collaborate in real time with changes immediately visible; the self-hosted version has no row, storage or API request limits (checked 14 Oct 2026) https://baserow.io/faq\n- br-import: Tables can be created by pasting or importing CSV, JSON, XML and Excel files; a separate guide imports Airtable bases from a share link (checked 14 Oct 2026) https://baserow.io/user-docs/create-a-table-via-import\n- br-docker: Baserow runs from a Docker image with PostgreSQL and Redis inside by default; DATABASE_URL points it at an external PostgreSQL (checked 14 Oct 2026) https://baserow.io/docs/installation/install-with-docker\n"
+        "markdown": "# SvGrid vs Baserow\n\nCanonical URL: https://svgrid.com/compare/baserow/\nFacts verified: 2026-10-14\nCompetitor site: https://baserow.io/\n\nBaserow is an open-source table-database app with an application builder and automations, run on its cloud or self-hosted with Docker on PostgreSQL.\n\n## Verdict\n\nBaserow is the pick for a team that wants an open-source app to sign into, self-hosted for free. SvGrid Base is the pick when the table database has to be part of your own Svelte app: editable in your pages, on your database, with Kanban, calendar, charts and comments in the one licence.\n\nMigration guide: moving from Baserow to SvGrid: https://svgrid.com/docs/help/migrating-from-baserow/\n\n## At a glance\n\n| Fact | SvGrid | Baserow | Checked |\n| --- | --- | --- | --- |\n| What it is | A Svelte 5 component (<SvBase>) inside your own app, on your database | Hosted web app (cloud), Self-hosted web app (Docker) | 14 Oct 2026 |\n| Pricing | SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT | Baserow's self-hosted open-source edition is free with unlimited rows. baserow.io/pricing lists Premium at $10 per user per month billed yearly ($12 monthly), Advanced at $18 per user per month billed yearly ($22 monthly) and Enterprise on request, at the same prices on cloud and self-hosted; cloud Free is $0 with 3,000 rows per workspace | 14 Oct 2026 |\n\n## Overview\n\nBaserow gives a team tables of typed fields with grid, form and gallery views for free, and Kanban, calendar, timeline and survey views on paid plans. It has linked records with lookups, rollups and counts, formulas, an automation builder with email, HTTP and AI actions, an application builder for portals and internal tools, a REST API and real-time collaboration. The core is MIT; premium and enterprise features need a subscription, self-hosted or on cloud.\n\nSvGrid Base is a table database you ship as part of your own Svelte 5 app. It comes in @svgrid/enterprise: your users get typed fields, saved views, filters, groups, row colors, linked records, automations and an expanded record with comments, and you keep the data in the database you already run. Nothing runs beside your app; the base is a component in it.\n\n## Looking for a Baserow alternative for Svelte?\n\nPeople searching for a Baserow alternative usually want the Baserow experience somewhere Baserow does not go: inside their own product. Baserow can show a public view in an iframe, read-only except for forms, or publish an app made in its application builder on its own domain. SvGrid Base is a Svelte component instead: <SvBase> renders editable grid, Kanban, calendar, gallery, chart and form views in your pages, behind your login, and writes every change to your Postgres, MySQL, SQLite, Supabase or REST API.\n\n## What they have in common\n\n- Typed fields with grid, form and gallery views, and saved filters, sorts and groups per view.\n- Linked records between tables, with lookup, rollup and count fields and formulas.\n- Autonumber, created and last-modified fields, and collaborator fields.\n- Automations triggered by record changes, a schedule or a webhook, with email and HTTP actions.\n- Data kept in PostgreSQL.\n- Real-time updates when other people change records.\n\n## Where SvGrid is stronger\n\n- It is a component, not an app: <SvBase> renders inside your own Svelte pages and edits records there, where Baserow's embed is a read-only iframe of a public view.\n- Kanban, calendar, chart, row colors and record comments are all in the one Suite licence; Baserow puts Kanban, calendar, comments and row coloring on paid plans.\n- Works on your own tables: it reads your schema, columns and foreign keys and writes back to them, where Baserow keeps data in its own database and syncs other sources in.\n- No vendor branding to remove: the base takes your app's look from --sg-* tokens.\n- Automations run in the browser or on your server with no credits to count, and their secrets stay on your server.\n- Priced per developer, not per user: the people who use the app do not need seats.\n\n## Where Baserow is stronger\n\n- Open source with an MIT core, and free to self-host with unlimited rows and storage.\n- A finished product with sign-in, workspaces, roles and sharing; no developer needed to start.\n- An application builder for portals and internal tools on top of the data, with custom domains.\n- Long row change history, audit logs on Advanced, and a REST API and MCP server.\n- File import (CSV, Excel, JSON, XML, and Airtable bases) and AI fields and an AI assistant.\n- No record limit per table when self-hosted; SvGrid Base keeps each table's records in the page, up to a configurable limit.\n\n## Feature by feature\n\nYes: 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.\n\n| Feature | SvGrid | Baserow |\n| --- | --- | --- |\n| Runs inside your own app's pages | Yes - a Svelte 5 component, <SvBase> | No - public views embed as an iframe; no UI component or SDK found |\n| Edit records from the embedded view | Yes | No - shared views are read-only except forms |\n| Source licence | Paid tier - commercial (Enterprise Suite); the grid underneath is MIT | Yes - MIT core; premium and enterprise code needs a subscription in production |\n| Works on your existing database | Yes - Postgres, MySQL, SQLite, Supabase or a REST API | Partial - data lives in Baserow's PostgreSQL; a PostgreSQL table syncs in, two-way optional, not real time |\n| Grid, form and gallery views | Yes | Yes - every plan |\n| Kanban and calendar views | Yes | Paid tier - Premium and up |\n| Linked records, lookup, rollup, count and formula fields | Yes | Yes |\n| Autonumber, created and last-modified fields | Yes | Yes |\n| Automations | Yes - in the browser or on your server, no credits | Yes - credits per month on cloud, unlimited self-hosted |\n| Record comments | Yes - stored wherever your app stores them | Paid tier - paid plans |\n| Row colors | Yes - by a field or by conditions, per view | Paid tier - Premium and up |\n| Row change history | Partial - this session's changes in the record; a server audit hook logs every write | Yes - kept by plan on cloud |\n| Who can see and edit what | Partial - your server's authorize hook or the database's row level security; no roles screen | Paid tier - role, field and view permissions on Advanced and Enterprise |\n| Changes from other users appear live | Partial - through a realtime source (Supabase Realtime, a WebSocket, a poll) | Yes |\n| Import CSV or Excel files | Partial - paste a range, or load the file into your database and open it | Yes - CSV, Excel, JSON, XML and Airtable |\n| Your branding only | Yes - your app's look through --sg-* tokens | Paid tier - logo removal on paid plans |\n| Records per table | Partial - the page holds a table's records, up to a limit you set (10,000 by default) | Yes - unlimited self-hosted; capped per workspace on cloud |\n| Usable with no developer | No - a developer adds it to an app | Yes - cloud sign-up or a Docker install |\n\n## When to choose SvGrid\n\n- The table database has to appear, editable, inside your own Svelte or SvelteKit app, under your login and your look.\n- You want Kanban, calendar, comments and row colors without per-user paid plans.\n- Your data already lives in Postgres, MySQL, SQLite, Supabase or behind your API and should stay in those tables.\n- You would rather pay per developer than per user.\n\n## When to choose Baserow\n\n- You want an open-source app a team can self-host and use today, with no developer.\n- You need roles, workspaces and sharing managed from a screen.\n- You want an application builder for portals on your own domain without writing a front end.\n- You want file import, AI fields and long row history built in.\n\n## Migration effort\n\nEstimated effort: 1-3 hours per database, plus rebuilding automations.\n\nWhat you give up:\n\n- Workspaces, roles and the sharing screen; who may do what moves into your server's authorize hook or your database's row level security.\n- The application builder; the screens around the base are your own Svelte pages.\n- Long row change history and audit logs kept for you; the base shows a session's changes and your audit hook keeps the rest.\n- File import, AI fields and the AI assistant inside the tool.\n\nMigration guide: moving from Baserow to SvGrid: https://svgrid.com/docs/help/migrating-from-baserow/\n\n## Live example\n\nProject Tracker: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/504-project-tracker/\n\n## The bottom line\n\nBaserow is a good open-source table database for a team that will sign into it, and free to self-host. When the table database belongs inside your own product, SvGrid Base fits better: it renders editable views in your Svelte pages instead of a read-only iframe, keeps the data in the tables you already run, and includes Kanban, calendar, comments and row colors in one licence priced per developer.\n\n## Frequently asked questions\n\n### Can I embed Baserow in my own app?\n\nBaserow can embed any publicly shared view with an iframe, and shared views are read-only except form views. Its application builder publishes apps on a domain rather than inside your pages. SvGrid Base is a Svelte component, so its views render and edit records in your own pages, behind your app's login.\n\n### Is SvGrid Base open source like Baserow?\n\nNo. SvGrid Base is commercial and ships in Enterprise Suite of @svgrid/enterprise; the grid it is built on, @svgrid/grid, is MIT. Baserow's core is MIT, and its premium and enterprise directories are under licences that need a subscription in production.\n\n### Can SvGrid Base work on the PostgreSQL database Baserow uses?\n\nNot on Baserow's internal tables, which belong to Baserow. Export each table to CSV, load it into your own PostgreSQL tables, and point createBaseEndpoint at them: it reads the columns and foreign keys and opens the tables with typed fields and links. If your data already lives in your own PostgreSQL and is synced into Baserow, point the base at the source tables directly.\n\n### Which Baserow paid features are included in SvGrid Base?\n\nKanban and calendar views, row colors and record comments are paid on Baserow and part of SvGrid Base. Role, field and view permissions are Advanced on Baserow; in SvGrid Base they are rules you write in your server or your database.\n\n### How is SvGrid Base priced compared with Baserow?\n\nBaserow's paid plans are per user per month; 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.\n\n### What does SvGrid Base not do that Baserow does?\n\nThere are no workspaces, roles or sharing screen, no application builder, no file import dialog or AI fields in the base itself, no long row history kept for you, 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.\n\n### Is SvGrid a good Baserow alternative for Svelte?\n\nPeople searching for a Baserow alternative usually want the Baserow experience somewhere Baserow does not go: inside their own product. Baserow can show a public view in an iframe, read-only except for forms, or publish an app made in its application builder on its own domain. SvGrid Base is a Svelte component instead: <SvBase> renders editable grid, Kanban, calendar, gallery, chart and form views in your pages, behind your login, and writes every change to your Postgres, MySQL, SQLite, Supabase or REST API.\n\n## Related comparisons and docs\n\n- [SvGrid vs Airtable](https://svgrid.com/compare/airtable/)\n- [SvGrid vs NocoDB](https://svgrid.com/compare/nocodb/)\n- [Build a project tracker](https://svgrid.com/docs/help/base/start/)\n- [Ready-to-use bases](https://svgrid.com/docs/help/base/templates/)\n- [Keep a base in a database](https://svgrid.com/docs/help/base/data/)\n- [Automations](https://svgrid.com/docs/help/base/automations/)\n- [Field types](https://svgrid.com/docs/help/fields/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 14 Oct 2026. Feature and pricing statements come from the pages listed below.\n\n- br-pricing: Cloud Free $0 with 3,000 rows per workspace and grid, form and gallery views; Premium $10 per user per month billed yearly or $12 monthly with all views; Advanced $18 billed yearly or $22 monthly with role based permissions and audit logs; Enterprise on request; Kanban, survey, calendar and timeline views and row comments and coloring on Premium and up; the self-hosted tab lists the open source plan free with unlimited rows and storage (checked 14 Oct 2026) https://baserow.io/pricing\n- br-license: Content outside the premium and enterprise directories is under the MIT Expat license; premium code may only be used in production with a valid Baserow Premium Edition subscription (checked 14 Oct 2026) https://gitlab.com/baserow/baserow/-/raw/develop/LICENSE\n- br-sharing: Any publicly shared view can be embedded with an iframe; shared views are read-only except form views; paid subscribers can hide the Baserow logo from shared views (checked 14 Oct 2026) https://baserow.io/user-docs/public-sharing\n- br-datasync: External sources sync into Baserow tables; real-time sync is not available; PostgreSQL sync supports optional two-way sync (checked 14 Oct 2026) https://baserow.io/user-docs/data-sync-in-baserow\n- br-fields: Field types include link-to-table, lookup, count, rollup, formula, autonumber, UUID, created on, last modified, created by, last modified by, duration, file, collaborator, rating and AI prompt (checked 14 Oct 2026) https://baserow.io/user-docs/baserow-field-overview\n- br-automations: Automation triggers include periodic, rows created, updated or deleted, an incoming HTTP request and a manual trigger; actions include sending an email and an HTTP request; cloud automation credits are counted per plan and self-hosted is unlimited (checked 14 Oct 2026) https://baserow.io/user-docs/automation-triggers\n- br-comments: Row comments and mentions are available on paid plans (checked 14 Oct 2026) https://baserow.io/user-docs/row-commenting\n- br-history: Row change history is on every plan with retention that varies by plan (checked 14 Oct 2026) https://baserow.io/user-docs/row-change-history\n- br-permissions: Free and Premium plans offer two workspace-level roles without table-level restrictions; Advanced and Enterprise add roles with granular permissions (checked 14 Oct 2026) https://baserow.io/user-docs/permissions-overview\n- br-faq: Collaborate in real time with changes immediately visible; the self-hosted version has no row, storage or API request limits (checked 14 Oct 2026) https://baserow.io/faq\n- br-import: Tables can be created by pasting or importing CSV, JSON, XML and Excel files; a separate guide imports Airtable bases from a share link (checked 14 Oct 2026) https://baserow.io/user-docs/create-a-table-via-import\n- br-docker: Baserow runs from a Docker image with PostgreSQL and Redis inside by default; DATABASE_URL points it at an external PostgreSQL (checked 14 Oct 2026) https://baserow.io/docs/installation/install-with-docker\n"
     },
     {
         "slug": "compare/devextreme-datagrid",
@@ -7283,7 +7283,7 @@ export const docs = [
         "path": "docs/_data/comparisons/nocodb.json",
         "title": "SvGrid vs NocoDB",
         "section": "Comparisons",
-        "markdown": "# SvGrid vs NocoDB\n\nCanonical URL: https://svgrid.com/compare/nocodb/\nFacts verified: 2026-10-14\nCompetitor site: https://nocodb.com/\n\nNocoDB is a table-database app with a spreadsheet interface, run on its cloud or self-hosted with Docker, that can sit on top of an existing PostgreSQL or MySQL database.\n\n## Verdict\n\nNocoDB 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.\n\nMigration guide: moving from NocoDB to SvGrid: https://svgrid.com/docs/help/migrating-from-nocodb/\n\n## At a glance\n\n| Fact | SvGrid | NocoDB | Checked |\n| --- | --- | --- | --- |\n| What it is | A Svelte 5 component (<SvBase>) inside your own app, on your database | Hosted web app (cloud), Self-hosted web app (Docker) | 14 Oct 2026 |\n| Pricing | SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT | NocoDB self-hosted Community is $0 under the Sustainable Use License. nocodb.com/pricing lists cloud Plus at $12 per seat per month billed annually ($15 monthly), Business at $24 per seat per month billed annually ($30 monthly), Scale at $45 per seat per month billed annually with 3 minimum seats, and Enterprise on request; self-hosted Business and Scale are priced the same per seat | 14 Oct 2026 |\n\n## Overview\n\nNocoDB 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.\n\nSvGrid 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.\n\n## Looking for a NocoDB alternative for Svelte?\n\nPeople 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.\n\n## What they have in common\n\n- A grid of typed fields with saved views: grid, form, gallery, Kanban and calendar.\n- Linked records between tables, with lookup and rollup fields and formulas.\n- Can work on top of an existing PostgreSQL or MySQL database instead of a private store.\n- Automations that react to record changes, send email and call webhooks.\n- Record comments in an expanded record view.\n- Filters, sorts, groups and hidden fields saved per view.\n\n## Where SvGrid is stronger\n\n- 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.\n- 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.\n- Gantt, chart and autonumber are part of the base itself, with no plan above them.\n- Automations run in the browser or on your server with no monthly run quota, and their secrets stay on your server.\n- 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.\n- Priced per developer, not per editor: the people who use the app do not need seats.\n\n## Where NocoDB is stronger\n\n- A finished product: sign up or run one Docker command and a team is working, with no developer involved.\n- Roles out of the box (owner, creator, editor, commenter, viewer) with a sharing screen, and table and field permissions on paid plans.\n- 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.\n- A REST API, an SDK, an MCP server and a workflow builder with integration nodes (Slack, Gmail, GitHub and more).\n- A map view and file import (CSV, Excel, JSON, and Airtable bases) in the free edition.\n- No record limit per table when self-hosted; SvGrid Base keeps each table's records in the page, up to a configurable limit.\n\n## Feature by feature\n\nYes: 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.\n\n| Feature | SvGrid | NocoDB |\n| --- | --- | --- |\n| Runs inside your own app's pages | Yes - a Svelte 5 component, <SvBase> | No - shared views and bases embed as an iframe; no UI component or front-end SDK found |\n| Offered to your customers inside your product | Yes - unlimited apps and end users on the Suite licence | Paid tier - commercial licence needed to embed NocoDB where customers use it |\n| Source licence | Paid tier - commercial (Enterprise Suite); the grid underneath is MIT | Partial - Sustainable Use License since January 2026, not OSI-approved |\n| Works on your existing database | Yes - Postgres, MySQL, SQLite, Supabase or a REST API | Yes - external PostgreSQL or MySQL; SQL Server is an Enterprise add-on |\n| Grid, form, gallery, Kanban and calendar views | Yes | Yes - every plan |\n| Gantt or timeline view | Yes - Gantt view with dependencies and progress | Paid tier - Business plan and above |\n| Chart view | Yes - bar, line, pie and donut, per view | Paid tier - dashboards on Business and above |\n| Linked records, lookup, rollup and formula fields | Yes | Yes |\n| Autonumber field | Yes | Paid tier - Business plan and above, PostgreSQL only |\n| Automations | Yes - in the browser or on your server, no run quota | Partial - 2 workflows per base in Community; cloud runs metered by plan |\n| Email and webhook actions | Yes - email sent by your server; secrets stay server-side | Yes |\n| Record comments | Yes - stored wherever your app stores them | Yes - every plan; mentions on paid plans |\n| Record change history | Partial - this session's changes in the record; a server audit hook logs every write | Yes - kept by plan on cloud, unlimited self-hosted |\n| Who can see and edit what | Partial - your server's authorize hook or the database's row level security; no roles screen | Yes - five roles free; table and field permissions paid |\n| Changes from other users appear live | Partial - through a realtime source (Supabase Realtime, a WebSocket, a poll); no presence | Yes - realtime presence on every plan |\n| Import CSV or Excel files | Partial - paste a range, or load the file into your database and open it | Yes - CSV, Excel, JSON and Airtable |\n| Your branding only | Yes - your app's look through --sg-* tokens | Paid tier - white-label is a self-hosted Enterprise add-on |\n| Records per table | Partial - the page holds a table's records, up to a limit you set (10,000 by default) | Yes - unlimited self-hosted; capped by plan on cloud |\n| Usable with no developer | No - a developer adds it to an app | Yes - cloud sign-up or a Docker install |\n\n## When to choose SvGrid\n\n- The table database has to appear inside your own Svelte or SvelteKit app, under your login and your look.\n- You want to offer it to your customers without a separate commercial agreement for the table tool.\n- You need Gantt, charts and autonumber without moving everyone to a higher plan.\n- Your data already lives in Postgres, MySQL, SQLite, Supabase or behind your API and should stay there, reached through your own server.\n- You would rather pay per developer than per editor seat.\n\n## When to choose NocoDB\n\n- You want a finished app a team can use today, with no developer.\n- You need roles, sharing links and per-table or per-field permissions managed from a screen.\n- You want long record revision history and presence without building anything.\n- You want workflows with ready-made Slack, Gmail or GitHub nodes.\n\n## Migration effort\n\nEstimated effort: 1-2 hours per base on PostgreSQL or MySQL; more to rebuild workflows.\n\nWhat you give up:\n\n- The roles screen and sharing links; who may do what moves into your server's authorize hook or your database's row level security.\n- Long record revision history; the base shows a session's changes and your audit hook keeps the rest.\n- Workflow integration nodes; SvGrid Base automations call webhooks, send email and run actions you register in code.\n- A no-code setup path: someone has to add <SvBase> to a Svelte app.\n\nMigration guide: moving from NocoDB to SvGrid: https://svgrid.com/docs/help/migrating-from-nocodb/\n\n## Live example\n\nProject Tracker: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/504-project-tracker/\n\n## The bottom line\n\nNocoDB 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.\n\n## Frequently asked questions\n\n### Can I embed NocoDB inside my own app?\n\nOnly 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.\n\n### Is NocoDB still open source?\n\nIts 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.\n\n### Can SvGrid Base use the same database NocoDB is connected to?\n\nYes, 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.\n\n### Does SvGrid Base have a Gantt view like NocoDB's paid plans?\n\nYes. 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.\n\n### How is SvGrid Base priced compared with NocoDB?\n\nNocoDB 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.\n\n### What does SvGrid Base not do that NocoDB does?\n\nThere 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.\n\n### Is SvGrid a good NocoDB alternative for Svelte?\n\nPeople 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.\n\n## Related comparisons and docs\n\n- [SvGrid vs Airtable](https://svgrid.com/compare/airtable/)\n- [SvGrid vs Baserow](https://svgrid.com/compare/baserow/)\n- [Build a project tracker](https://svgrid.com/docs/help/base/start/)\n- [From a database to an app](https://svgrid.com/docs/help/base/quick-start/)\n- [Keep a base in a database](https://svgrid.com/docs/help/base/data/)\n- [Automations](https://svgrid.com/docs/help/base/automations/)\n- [Field types](https://svgrid.com/docs/help/fields/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 14 Oct 2026. Feature and pricing statements come from the pages listed below.\n\n- 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) https://nocodb.com/pricing\n- 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) https://nocodb.com/docs/self-hosting/license\n- noco-share: A shared project can be embedded in another application with an HTML iframe; shared views are read-only (checked 14 Oct 2026) https://nocodb.com/docs/product/projects/share-project\n- 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) https://nocodb.com/docs/product/integrations/data-sources/connect-to-data-source\n- noco-views: View types: grid, form, gallery, Kanban, calendar, map, with list, timeline and Gantt marked for paid plans (checked 14 Oct 2026) https://nocodb.com/docs/product/tables/views\n- 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) https://nocodb.com/docs/product/tables/views/view-types/timeline\n- 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) https://nocodb.com/docs/product/account-settings/cloud-enterprise-edition/community-vs-paid-editions\n- 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) https://nocodb.com/docs/product/tables/fields/field-types/identifier-types/auto-number\n- 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) https://nocodb.com/docs/workflows\n- 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) https://nocodb.com/docs/product/tables/records/expand-record\n- 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) https://nocodb.com/docs/product/collaboration/roles-and-permissions\n- noco-presence: Realtime presence shows who else works in a table; it does not lock anything (checked 14 Oct 2026) https://nocodb.com/docs/product/tables/table-operations/realtime-presence\n- noco-import: Create a table by importing a CSV, Excel or JSON file, maximum file size 5 MB (checked 14 Oct 2026) https://nocodb.com/docs/product/tables/create-table-via-import\n- 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) https://nocodb.com/docs/self-hosting/white-label\n- noco-install: One command makes a Docker Compose stack with NocoDB, a worker, Postgres and Redis (checked 14 Oct 2026) https://nocodb.com/docs/self-hosting/installation/quickstart\n"
+        "markdown": "# SvGrid vs NocoDB\n\nCanonical URL: https://svgrid.com/compare/nocodb/\nFacts verified: 2026-10-14\nCompetitor site: https://nocodb.com/\n\nNocoDB is a table-database app with a spreadsheet interface, run on its cloud or self-hosted with Docker, that can sit on top of an existing PostgreSQL or MySQL database.\n\n## Verdict\n\nNocoDB 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.\n\nMigration guide: moving from NocoDB to SvGrid: https://svgrid.com/docs/help/migrating-from-nocodb/\n\n## At a glance\n\n| Fact | SvGrid | NocoDB | Checked |\n| --- | --- | --- | --- |\n| What it is | A Svelte 5 component (<SvBase>) inside your own app, on your database | Hosted web app (cloud), Self-hosted web app (Docker) | 14 Oct 2026 |\n| Pricing | SvGrid Base ships in Enterprise Suite of @svgrid/enterprise, $999 per developer per year, unlimited apps and end users; the grid it runs on is MIT | NocoDB self-hosted Community is $0 under the Sustainable Use License. nocodb.com/pricing lists cloud Plus at $12 per seat per month billed annually ($15 monthly), Business at $24 per seat per month billed annually ($30 monthly), Scale at $45 per seat per month billed annually with 3 minimum seats, and Enterprise on request; self-hosted Business and Scale are priced the same per seat | 14 Oct 2026 |\n\n## Overview\n\nNocoDB 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.\n\nSvGrid 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.\n\n## Looking for a NocoDB alternative for Svelte?\n\nPeople 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 dashboards and autonumber fields they need sit on the Business plan. SvGrid Base answers all three by being a component: <SvBase> renders the grid, Kanban, calendar, gallery, chart and form views inside your Svelte app and reads and writes your Postgres, MySQL, SQLite, Supabase or REST API through your own server.\n\n## What they have in common\n\n- A grid of typed fields with saved views: grid, form, gallery, Kanban and calendar.\n- Linked records between tables, with lookup and rollup fields and formulas.\n- Can work on top of an existing PostgreSQL or MySQL database instead of a private store.\n- Automations that react to record changes, send email and call webhooks.\n- Record comments in an expanded record view.\n- Filters, sorts, groups and hidden fields saved per view.\n\n## Where SvGrid is stronger\n\n- 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.\n- 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.\n- Chart views and autonumber are part of the base itself, with no plan above them.\n- Automations run in the browser or on your server with no monthly run quota, and their secrets stay on your server.\n- 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.\n- Priced per developer, not per editor: the people who use the app do not need seats.\n\n## Where NocoDB is stronger\n\n- A finished product: sign up or run one Docker command and a team is working, with no developer involved.\n- Roles out of the box (owner, creator, editor, commenter, viewer) with a sharing screen, and table and field permissions on paid plans.\n- 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.\n- A REST API, an SDK, an MCP server and a workflow builder with integration nodes (Slack, Gmail, GitHub and more).\n- A map view and file import (CSV, Excel, JSON, and Airtable bases) in the free edition.\n- No record limit per table when self-hosted; SvGrid Base keeps each table's records in the page, up to a configurable limit.\n\n## Feature by feature\n\nYes: 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.\n\n| Feature | SvGrid | NocoDB |\n| --- | --- | --- |\n| Runs inside your own app's pages | Yes - a Svelte 5 component, <SvBase> | No - shared views and bases embed as an iframe; no UI component or front-end SDK found |\n| Offered to your customers inside your product | Yes - unlimited apps and end users on the Suite licence | Paid tier - commercial licence needed to embed NocoDB where customers use it |\n| Source licence | Paid tier - commercial (Enterprise Suite); the grid underneath is MIT | Partial - Sustainable Use License since January 2026, not OSI-approved |\n| Works on your existing database | Yes - Postgres, MySQL, SQLite, Supabase or a REST API | Yes - external PostgreSQL or MySQL; SQL Server is an Enterprise add-on |\n| Grid, form, gallery, Kanban and calendar views | Yes | Yes - every plan |\n| Chart view | Yes - bar, line, pie and donut, per view | Paid tier - dashboards on Business and above |\n| Linked records, lookup, rollup and formula fields | Yes | Yes |\n| Autonumber field | Yes | Paid tier - Business plan and above, PostgreSQL only |\n| Automations | Yes - in the browser or on your server, no run quota | Partial - 2 workflows per base in Community; cloud runs metered by plan |\n| Email and webhook actions | Yes - email sent by your server; secrets stay server-side | Yes |\n| Record comments | Yes - stored wherever your app stores them | Yes - every plan; mentions on paid plans |\n| Record change history | Partial - this session's changes in the record; a server audit hook logs every write | Yes - kept by plan on cloud, unlimited self-hosted |\n| Who can see and edit what | Partial - your server's authorize hook or the database's row level security; no roles screen | Yes - five roles free; table and field permissions paid |\n| Changes from other users appear live | Partial - through a realtime source (Supabase Realtime, a WebSocket, a poll); no presence | Yes - realtime presence on every plan |\n| Import CSV or Excel files | Partial - paste a range, or load the file into your database and open it | Yes - CSV, Excel, JSON and Airtable |\n| Your branding only | Yes - your app's look through --sg-* tokens | Paid tier - white-label is a self-hosted Enterprise add-on |\n| Records per table | Partial - the page holds a table's records, up to a limit you set (10,000 by default) | Yes - unlimited self-hosted; capped by plan on cloud |\n| Usable with no developer | No - a developer adds it to an app | Yes - cloud sign-up or a Docker install |\n\n## When to choose SvGrid\n\n- The table database has to appear inside your own Svelte or SvelteKit app, under your login and your look.\n- You want to offer it to your customers without a separate commercial agreement for the table tool.\n- You need charts and autonumber without moving everyone to a higher plan.\n- Your data already lives in Postgres, MySQL, SQLite, Supabase or behind your API and should stay there, reached through your own server.\n- You would rather pay per developer than per editor seat.\n\n## When to choose NocoDB\n\n- You want a finished app a team can use today, with no developer.\n- You need roles, sharing links and per-table or per-field permissions managed from a screen.\n- You want long record revision history and presence without building anything.\n- You want workflows with ready-made Slack, Gmail or GitHub nodes.\n\n## Migration effort\n\nEstimated effort: 1-2 hours per base on PostgreSQL or MySQL; more to rebuild workflows.\n\nWhat you give up:\n\n- The roles screen and sharing links; who may do what moves into your server's authorize hook or your database's row level security.\n- Long record revision history; the base shows a session's changes and your audit hook keeps the rest.\n- Workflow integration nodes; SvGrid Base automations call webhooks, send email and run actions you register in code.\n- A no-code setup path: someone has to add <SvBase> to a Svelte app.\n\nMigration guide: moving from NocoDB to SvGrid: https://svgrid.com/docs/help/migrating-from-nocodb/\n\n## Live example\n\nProject Tracker: open it in the gallery for the source and the full-size version. https://svgrid.com/demos/504-project-tracker/\n\n## The bottom line\n\nNocoDB 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 charts, autonumber and server-side automations without plan gates, and its licence already covers putting it in front of your customers.\n\n## Frequently asked questions\n\n### Can I embed NocoDB inside my own app?\n\nOnly 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.\n\n### Is NocoDB still open source?\n\nIts 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.\n\n### Can SvGrid Base use the same database NocoDB is connected to?\n\nYes, 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.\n\n### How is SvGrid Base priced compared with NocoDB?\n\nNocoDB 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.\n\n### What does SvGrid Base not do that NocoDB does?\n\nThere 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.\n\n### Is SvGrid a good NocoDB alternative for Svelte?\n\nPeople 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 dashboards and autonumber fields they need sit on the Business plan. SvGrid Base answers all three by being a component: <SvBase> renders the grid, Kanban, calendar, gallery, chart and form views inside your Svelte app and reads and writes your Postgres, MySQL, SQLite, Supabase or REST API through your own server.\n\n## Related comparisons and docs\n\n- [SvGrid vs Airtable](https://svgrid.com/compare/airtable/)\n- [SvGrid vs Baserow](https://svgrid.com/compare/baserow/)\n- [Build a project tracker](https://svgrid.com/docs/help/base/start/)\n- [From a database to an app](https://svgrid.com/docs/help/base/quick-start/)\n- [Keep a base in a database](https://svgrid.com/docs/help/base/data/)\n- [Automations](https://svgrid.com/docs/help/base/automations/)\n- [Field types](https://svgrid.com/docs/help/fields/)\n\n## Sources and last verified\n\nEvery claim on this page was last checked on 14 Oct 2026. Feature and pricing statements come from the pages listed below.\n\n- 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) https://nocodb.com/pricing\n- 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) https://nocodb.com/docs/self-hosting/license\n- noco-share: A shared project can be embedded in another application with an HTML iframe; shared views are read-only (checked 14 Oct 2026) https://nocodb.com/docs/product/projects/share-project\n- 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) https://nocodb.com/docs/product/integrations/data-sources/connect-to-data-source\n- noco-views: View types: grid, form, gallery, Kanban, calendar, map, with list, timeline and Gantt marked for paid plans (checked 14 Oct 2026) https://nocodb.com/docs/product/tables/views\n- 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) https://nocodb.com/docs/product/tables/views/view-types/timeline\n- 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) https://nocodb.com/docs/product/account-settings/cloud-enterprise-edition/community-vs-paid-editions\n- 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) https://nocodb.com/docs/product/tables/fields/field-types/identifier-types/auto-number\n- 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) https://nocodb.com/docs/workflows\n- 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) https://nocodb.com/docs/product/tables/records/expand-record\n- 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) https://nocodb.com/docs/product/collaboration/roles-and-permissions\n- noco-presence: Realtime presence shows who else works in a table; it does not lock anything (checked 14 Oct 2026) https://nocodb.com/docs/product/tables/table-operations/realtime-presence\n- noco-import: Create a table by importing a CSV, Excel or JSON file, maximum file size 5 MB (checked 14 Oct 2026) https://nocodb.com/docs/product/tables/create-table-via-import\n- 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) https://nocodb.com/docs/self-hosting/white-label\n- noco-install: One command makes a Docker Compose stack with NocoDB, a worker, Postgres and Redis (checked 14 Oct 2026) https://nocodb.com/docs/self-hosting/installation/quickstart\n"
     },
     {
         "slug": "compare/primevue-datatable",
@@ -7430,8 +7430,8 @@ export const apiReference = {
     ]
 };
 export const apiSurface = {
-    "gridVersion": "3.0.12",
-    "enterpriseVersion": "3.1.9",
+    "gridVersion": "3.0.13",
+    "enterpriseVersion": "3.1.10",
     "grid": {
         "values": [
             "ALL_FILTER_OPERATORS",

package/dist/preview.d.ts

@@ -8,7 +8,7 @@ export declare const UI_RESOURCE_URI = "ui://svgrid/preview.html";
  * start failing in a way nobody is watching for. `tools/mcp-tools.test.ts` checks these
  * against the workspace so they cannot quietly rot either.
  */
-export declare const PREVIEW_GRID_WC_VERSION = "3.0.14";
+export declare const PREVIEW_GRID_WC_VERSION = "3.0.15";
 export declare function previewResource(): {
     uri: string;
     name: string;

package/dist/preview.js

@@ -27,7 +27,7 @@ const UI_RESOURCE_META_KEY = 'ui/resourceUri';
  * start failing in a way nobody is watching for. `tools/mcp-tools.test.ts` checks these
  * against the workspace so they cannot quietly rot either.
  */
-export const PREVIEW_GRID_WC_VERSION = '3.0.14';
+export const PREVIEW_GRID_WC_VERSION = '3.0.15';
 const EXT_APPS_VERSION = '1.7.5';
 const CDN = 'https://cdn.jsdelivr.net/npm';
 /**

package/package.json

@@ -5,7 +5,7 @@
     "type": "commercial",
     "url": "https://svgrid.com/pricing"
   },
-  "version": "3.0.15",
+  "version": "3.0.17",
   "description": "Model Context Protocol server for SvGrid, the Svelte 5 data grid: checks the code your AI writes against the real API surface, plus version-pinned docs, API reference and 373 demo sources.",
   "license": "MIT",
   "author": "jQWidgets <sales@jqwidgets.com>",
@@ -33,7 +33,7 @@
     "@modelcontextprotocol/sdk": "^1.0.4",
     "svelte": "^5.55.5",
     "zod": "^3.23.8",
-    "@svgrid/enterprise": "^3.1.9"
+    "@svgrid/enterprise": "^3.1.10"
   },
   "devDependencies": {
     "@types/node": "^22.10.7",

package/server.json

@@ -3,7 +3,7 @@
   "name": "com.svgrid/svgrid",
   "title": "SvGrid",
   "description": "Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.",
-  "version": "3.0.15",
+  "version": "3.0.17",
   "websiteUrl": "https://svgrid.com/docs/help/mcp-server/",
   "repository": {
     "url": "https://github.com/sv-grid/sv-grid",
@@ -15,7 +15,7 @@
       "registryType": "npm",
       "registryBaseUrl": "https://registry.npmjs.org",
       "identifier": "@svgrid/mcp",
-      "version": "3.0.15",
+      "version": "3.0.17",
       "runtimeHint": "npx",
       "transport": {
         "type": "stdio"