---
title: "Key concepts"
description: "How organisations, suites, apps, the Studio, and the Runtime fit together, and why the split between builder and user planes matters."
canonical: "https://grid82.com/docs/start/key-concepts"
updated: "2026-11-20"
---

# Key concepts

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.

```text
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 it      | Builders who create and manage apps                                                    | App users (team members, clients, partners)                                                      |
| Web address      | `https://studio.grid82.app`                                                            | `https://{suite}.grid82.app/{app}`                                                               |
| What it controls | Schema, roles, permissions, suite domains, team invites, Interface code, app workflows | Data grid, comments, personal views, approval queue, Interface pages, personal pages/automations |
| OpenAPI spec     | Public spec at `https://studio.grid82.app/v1/openapi.json`                             | Generated per caller at `/{app}/v1/openapi.json`                                                 |
| REST base URL    | `https://studio.grid82.app/v1`                                                         | `https://{suite}.grid82.app/{app}/v1`                                                            |
| MCP endpoint     | `https://studio.grid82.app/mcp`                                                        | `https://{suite}.grid82.app/mcp`                                                                 |

> **Info: Strict plane separation**
>
> Credentials never cross planes. An API key created inside a Runtime app returns `401` on the Studio API, and an end user's OAuth consent screen can never offer builder scopes like `schema:write`.

## 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](/docs/build/roles-and-permissions) to see how builders combine table, record, field, and action rules.
