Start here
Control plane
How Fork’s accounts, organizations, spaces, services, and usage controls fit together.
The resource model
Fork keeps product identity and policy in the control plane. A space is the isolated runtime where an application actually executes; an organization owns spaces, memberships, billing, and service installations.
Organizationownership · membership · wallet
Users + roleswho can do what
Spacesisolated applications
Servicesinstalled providers
Inside a space
Each space brings the pieces needed to build and operate an application:
- A persistent
/workspacefilesystem and an isolated Firecracker microVM. - A live web address, app runtime, logs, previews, and optional custom domains.
- The embedded Fork Agent plus scoped access for connected local agents.
- Fork Database, application secrets, model access, and installed organization services.
- Automatic checkpoints for agent and remote-development changes.
Terminology
The product UI uses space. Some APIs, tools, and older implementation surfaces still use workspace or sandbox for the same runnable boundary. MCP tools therefore accept a workspace argument even when you selected a space in the UI.