An instance is an independent PostgreSQL database on a specific host. It contains projects, users, objects, and data. Each instance has a versioned schema that can be migrated independently.
| Area | Description |
|---|---|
| Projects | Workspaces containing object structures, data tables, objects, and data |
| Users | Cached (synced from DBM) users with instance-level permissions |
| Devices | User-created automated agents, each with own API keys |
| Groups | User-organized roles for sharing permissions |
| Templates | OT/DT blueprints available across projects |
| Client Manuals | Documentation and files for available services |
The instance detail page shows:
Each instance stores: version, size limits, and default permissions for users and devices. Default permissions are the baseline that gets added to every user's or device's effective permission set.
Instance and project schema versions are shared. Migration order: instance first, then projects. Some migrations may affect only the instance or only projects.
Instance-level user permissions extend project permissions:
| Permission | Effect |
|---|---|
ALL_PROJECTS_ACCESS |
Grants access to all projects (equivalent to having null→0 on every project) |
GROUP_ORGANIZER |
Can create groups |
Plus all project-level permissions (ARCHITECT, ROLE_MODERATOR, ADMIN, etc.) which also apply at instance scope.
ALL_PROJECTS_ACCESS)Devices skip step 1 (they're always inside the instance). See Permissions for the full breakdown.