How Rootset organises data

One Rootset installation serves one workspace. Members share its logical databases. A logical database groups tables; it does not need a separate PostgreSQL database or a new connection URL.

Object	What it contains
Workspace	People, roles and team API keys.
Database	Named collection of tables.
Table	Field definitions, rows, unique rules and export requests.
Field	A name used as both the column label and JSON key, a type, a required setting, and a default.
Row	Typed values, an opaque ID and a revision.
Cell history	The most recent 200 saved changes to a cell while it exists.

PostgreSQL stores the data and cell changes. The API validates every write. The worker handles operations such as full-table exports and schema changes; the UI shows their progress where the operation was started. The UI and API are independently deployable images. Browsers connect directly to the public API origin. REST and MCP clients use that same API origin; the UI does not proxy those requests. Rootset does not provide database/table backup and restore, imports, search-index management or history archives. Export Requests downloads the full table as CSV or JSONL. Protect the installation with your PostgreSQL and object-storage provider’s backup tools.

Get started

Self-host Rootset

How Rootset organises data