Architecture

Forge Cloud has two primary runtime boundaries:

• the control plane at app.forgecloud.cc, where customers manage workspaces, projects and authorized operations;
• the Forge Agent on each connected VPS, which executes signed, typed jobs for resources owned by its workspace.

Customers do not install or operate the Forge Cloud control plane on their VPS.

Ownership Model

The control plane owns tenant identity, authorization, project configuration, deployment history, audit records and encrypted credentials. Every customer resource resolves through its workspace, project and service ownership before Forge can issue work to an Agent.

An Agent registration belongs to one workspace server record. It does not make the VPS visible to another workspace and it is not a general remote shell.

Workload Runtime

Application and data-service containers run on the selected connected server. Forge uses isolated runtime networks, persistent volumes where required, and explicit service placement. Web traffic is routed only for services configured with a public domain or generated hostname. Workers run without a public HTTP route.

Source services are built from their configured repository and root directory. Docker image services use their configured image directly. Deployment health checks must pass before a replacement web service becomes current.

Databases And Backups

Database services use persistent storage on their selected VPS. Private project connection details are preferred. Public database access is a separate explicit workflow with authentication and engine-specific TLS requirements.

Backup storage verification and restore testing are separate. An encrypted, checksummed off-site object proves that backup bytes are available; only a successful isolated restore can prove the supported recovery path.

Transactional Email

Project email domains, sender identities, DKIM material, API keys and delivery history remain scoped to their project. The current public API supports transactional sending. Forge Cloud platform messages use a separate delivery boundary and do not reuse tenant API keys or sender credentials.

External Providers

Workspace or project provider connections are used only within their recorded ownership and capability. Platform-owned DNS, storage, email and source-provider credentials are not customer variables and are not sent to customer workloads.

Migration

The current customer migration path imports supported Railway project metadata into a selected Forge workspace and project. Review imported services, variables, database actions and domains before deploying them to a connected server.