For one person, the core of Baserow is typed tables with a grid, forms, a kanban board, linked records and a REST API, which an agent builds on SQLite in one sitting. What stays behind is the shared side: real-time editing with other people, permissions, the app builder, automations and the AI features. The honest shortcut is that Baserow's own core is MIT-licensed and runs from Docker for free, so for a finished product self-hosting beats building; a prompt only wins when you want a small table tool you fully own.
Before you buildCheck Baserow Free first: 3,000 rows and 2 GB per workspace is plenty for many personal databases.
Build me a personal no-code database to replace Baserow Cloud. Requirements: - Node.js 22 + TypeScript: Next.js (App Router) with Drizzle ORM. `npm start` serves http://localhost:4740. - Storage: better-sqlite3 in ./data/db.db. Workspaces hold databases, databases hold tables, tables hold fields and rows; a row's values sit in one JSON column. Attachments go to ./data/files/. A change log records every cell edit (row, field, old value, new value, time) and is pruned after 90 days. - Field types: text, long text, number, boolean, date, single select, multiple select, URL, email, file, autonumber, created on, link to a row in another table (with a reverse field), lookup, rollup (count, sum, min, max) and formula. - Formulas: parsed with `jsep` against an allow-list (IF, CONCAT, ROUND, SUM, DATEDIFF, TODAY); no eval, no function constructors. Recalculate dependants when a cell changes. - Views per table, each saving its own sort, filters, hidden fields and grouping: grid with inline editing, gallery, kanban on a single-select field, and a form with a random public URL whose submissions become rows. - Import CSV (preview first, guess types). Export a table or a view as CSV. Export a workspace as a ZIP (schema.json, one JSON file of rows per table, attachments) and import such a ZIP. - REST API with a token from .env: list rows with filter, order_by, page and size parameters, and create, update and delete a row. - Single user, one password from .env (signed cookie). No accounts, no telemetry, local-first. - Out of scope: real-time collaboration, an app builder, automations, SSO and AI fields. - README: setup, backing up ./data, and a note that self-hosting Baserow itself is the shorter route if you want everything it has.
Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.
The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Baserow Cloud.
Extend the personal database in this folder. Requirements: - An import page that accepts a Baserow workspace export ZIP. - Read the schema and row files, create the tables and fields, map Baserow field types to ours and list any field type we cannot hold, such as AI or button fields, instead of dropping it. - Rebuild links between tables after all rows exist, and copy file attachments. - Show a report of rows imported and problems found. - Update the README.
Add two views to the personal database in this folder. Requirements: - A month calendar view placed by a date field, with drag to change the date. - A timeline view using a start and end date field, one row per record, zoom by week or month. - Both save their field choices, filters and sort like other views. - Update the README.
Add webhooks to the personal database in this folder. Requirements: - Per table, a list of webhook URLs with the events (created, updated, deleted) each receives. - Send a JSON body signed with an HMAC header using a secret from .env. - Retry a failed call at 1 minute, 10 minutes and 1 hour, and show the last 50 deliveries with their status code. - Update the README.
Add row comments to the personal database in this folder. Requirements: - A side panel on each row with a list of comments, newest last, each with text and a time. - Comments are stored in their own table, shown with a count badge on the grid row and excluded from CSV exports. - Edit and delete my own comments. - Update the README.
Because the core is open source, the fee mostly buys not running a server: hosting, updates and backups, plus shared editing, forms, the API and the app builder in one place. Teams pay per seat once more than one person edits the same tables.
Estimate · Runs on your laptop or a $5 VPS. The build is token usage on your agent plan.
Checked 2026-10-19 against Baserow Cloud's docs: 1, 2, 3, 4, 5
| Plan | Monthly | Annual, per month | What you get |
|---|---|---|---|
| Free | $0/workspace | $0/workspace | 3,000 rows and 2 GB per workspace, 2,000 automation credits a month, 500 external app users, 14 days of row change history, grid, form and gallery views. |
| Premium | $12/user | $10/user | 50,000 rows and 20 GB per workspace, 100,000 automation credits a month, all views, AI features, 90 days of row change history. |
| Advanced | $22/user | $18/user | 250,000 rows and 100 GB per workspace, 500,000 automation credits a month, role-based permissions, audit logs, 180 days of row change history. |
| Enterprise | custom | — | 1,000,000 rows and 1,000 GB per workspace, 2,000,000 automation credits a month, custom external app users, implementation support, payment by invoice. |
Free covers 3,000 rows and 2 GB per workspace with grid, form and gallery views, 2,000 automation credits and 65-plus templates.
Yes. An AI coding agent such as Claude Code, Codex or Cursor can build a usable personal version in one session with the prompt on this page, running on your own machine.
About $12 a month on the Premium plan per seat, $144 a year (checked 2026-10-19).
Real-time collaboration with comments, mentions and role-based permissions; The app builder and portals for external users; Automations, data sync from Jira, GitHub, GitLab and HubSpot, and the AI assistant; Row change history across a team and audit logs; Someone else running the servers, backups and upgrades. If any of those matter to you, keep paying.
Yes: Baserow (self-hosted) (open source), Grist (open source), NocoDB (free).