Platform
Orgs & workspaces
Organizations and workspaces are how Turbofy scopes and isolates everything you build. Pick the right workspace and the rest of the platform — schema, data, apps — follows.
Organization → workspace
An organization is the billing and membership boundary. Inside it live one or more workspaces. A workspace is the unit of isolation: it owns its own data schema, its records, and any apps built on top.
- Switch the active org/workspace from the switcher in the top-left of the dashboard.
- Each workspace is fully self-contained — tables and data never leak between workspaces.
- Apps live under a workspace and read that workspace's data directly.
Environments
Turbofy runs in two environments, prod and alpha. They expose the same surface; use prod for production work and alpha for staging.
Locally, workspace state is materialized under ~/.turbofy/workspaces/<environment>/<workspaceId>/.
Working with IDs
Every workspace-level tool takes a workspaceId explicitly — there is no hidden "active workspace". Table IDs are workspace-specific and live in your schema.ts; system IDs (apps, pages, blocks) are stable.