Forge Docs

Forge Cloud access

Forge Cloud may restrict new registration while a production qualification or email-delivery incident is active. If registration is unavailable, use a valid workspace invitation or wait until the registration gate reopens. Existing accounts can continue to sign in.

Choose Your Path

Set up your accountVerify your account, enroll MFA when required, and understand account and workspace boundaries.

Connect a VPSRegister a customer-owned server and install only the signed Forge Agent using its one-time command.

Create a projectKeep related application services, databases, variables, domains, logs, and backups in one project.

Deploy servicesDeploy supported GitHub repositories or use a prebuilt Docker image.

Provision databasesCreate project-scoped data services and review their access, persistence, and recovery capabilities.

Send transactional emailVerify a project domain, create a sender and use a scoped API key for transactional messages.

Back up databasesConfigure supported backup destinations and distinguish stored backup bytes from restore evidence.

Migrate from RailwayImport supported Railway project metadata and complete the required data-service follow-up steps.

Before You Connect A Server

• Use a VPS owned or controlled by your organization.
• Start with a supported Ubuntu host that does not contain unrelated customer workloads.
• Keep the SSH access you need to run the one-time Agent installation command.
• Allow the web ports required by the applications you choose to expose.
• Keep database ports private unless you deliberately enable Forge’s authenticated public-access workflow.
• Keep DNS access for every custom domain you attach.

Common Sequences

First deployment: Account Setup → Connect a Server → First Project.

First app: Source Services → Deployment Lifecycle → Domains.

First database: Database Overview → Backups → Restore.

First email: Email Overview → Domains and Senders → Transactional Email.

What Forge Manages

Forge Cloud keeps tenant accounts, workspaces, projects, services, credentials, domains, deployments and audit records in the control plane. A signed Forge Agent performs typed, authorized workload actions on a connected VPS. The Agent is not a general workspace shell and does not grant one workspace access to another workspace’s servers or projects.

Currently documented customer email behavior is transactional sending. Email automation, bulk broadcasting, inbound mailbox hosting and forwarding are not part of the supported public surface.