How Grid82 apps work
Every app runs inside an isolated SQLite database beside its permission definition, decoupled from the Studio control plane.
Grid82 splits the Studio (where you design apps) from the Runtime (where invited members use them). Understanding how an app is stored helps you model data, isolate workspaces, and keep schema edits safe.
Isolated app databases
Each app in Grid82 runs in its own isolated SQLite database. Rather than putting all customers into shared database tables with a tenant_id column, every app owns a private database together with its compiled schema, role rules, personal views, page metadata, and change history.
Three practical consequences follow from this design:
- Zero Studio dependency at runtime. The Runtime resolves an incoming hostname (
{suite}.grid82.appor your custom domain) straight to the app’s database and rules. Even if the Studio control plane is offline for maintenance, every published app continues serving users, API calls, and MCP sessions. - No noisy cross-tenant locking. Heavy imports, bulk SQL updates, or formula recalculations inside one app never contend with queries in another app.
- Per-app limits and trash. Each app gets the full per-app record quota of your plan (up to 1,000 records on Free, 50,000 on Starter, and 200,000 on Pro). Deleted tables, fields, and apps remain recoverable in the trash for 30 days.
Permanent IDs vs display labels
Every table (tbl_...), field (fld_...), record (rec_...), view (viw_...), and select option (opt_...) receives an opaque random ID at creation.
- Display names can be renamed at any time in the Studio without breaking saved views, formulas, Interface pages, or API clients keyed on IDs.
- Before deleting or renaming a table or field, check its impact report (
schema.impact). Grid82 lists every permission rule, formula, lookup, rollup, Interface page, and personal view referencing that item.
How permissions wrap every operation
Every read and write on an app passes through the same permission compiler before reaching the database:
- The caller’s roles on that app are resolved (for Runtime users) or the builder’s organisation membership is verified (in the Studio).
- Read rules compile directly into query predicates and column masks.
- Computed relations (
lookup,rollup) are hidden if the user cannot read the target table or field, preventing cross-table counts from leaking restricted records. - Every write records an atomic changeset inside the same database transaction so undo and audit logs stay accurate.