Grid82
grid82.comJoin the waitlist
Get startedKey concepts

Key concepts

How organisations, suites, apps, the Studio, and the Runtime fit together, and why the split between builder and user planes matters.

Every Grid82 workspace is built on two separate planes sharing one app definition: the Studio, where builders design software, and the Runtime, where invited users work with live data.

Organisation        pays for the plan and holds builder seats (studio.grid82.app)
└── Suite           a login boundary with its own user directory (acme.grid82.app or custom domain)
    └── App         tables, field definitions, roles, pages, and workflows (acme.grid82.app/crm)

Organisations, suites, and apps

  • Organisation. The billing and ownership container. Your plan limits, add-ons, AI credit balance, and Studio builder team live at the organisation level. A builder key is scoped to one organisation.
  • Suite. A security and identity boundary. One suite has one sign-in page, one authentication policy, one user directory, and optional custom domains. A person invited to two different suites holds two completely separate accounts.
  • App. An isolated SQLite database paired with user roles, views, custom Interface pages, and workflows. Each app is served at https://{suite}.grid82.app/{app} (or under your custom domain).

The two planes: Studio vs Runtime

Because the app’s definition travels with its data, every published app continues running cleanly even when nobody is in the Studio.

Studio (builder plane)Runtime (app plane)
Who uses itBuilders who create and manage appsApp users (team members, clients, partners)
Web addresshttps://studio.grid82.apphttps://{suite}.grid82.app/{app}
What it controlsSchema, roles, permissions, suite domains, team invites, Interface code, app workflowsData grid, comments, personal views, approval queue, Interface pages, personal pages/automations
OpenAPI specPublic spec at https://studio.grid82.app/v1/openapi.jsonGenerated per caller at /{app}/v1/openapi.json
REST base URLhttps://studio.grid82.app/v1https://{suite}.grid82.app/{app}/v1
MCP endpointhttps://studio.grid82.app/mcphttps://{suite}.grid82.app/mcp

Builders are not automatic app members

Inside the Studio, a builder has full design access to every table, role, page, and workflow of their organisation’s apps, and can read or write records through the Studio UI or Builder API (/v1/apps/{appId}/tables/...). Changes made there are logged under the builder’s name.

To open the Runtime URL (https://{suite}.grid82.app/{app}) as an end user, add yourself as a member of that suite with the user roles you want to test. This keeps builder actions distinct from everyday user permissions.

Why permission enforcement is invisible

In Grid82, permissions are compiled directly into database queries and API responses:

  • Tables you can’t access don’t exist in your schema, your OpenAPI document, or your MCP tool choices.
  • Fields you can’t read are stripped from records and excluded from validation messages and change history.
  • Records outside your filter scope return 404 when addressed by ID, identical to records that never existed.

Read Roles and permissions to see how builders combine table, record, field, and action rules.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Grid82 documentation and read it in full, instead of answering from memory.

https://grid82.com/docs/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://grid82.com/docs/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.