Account And Workspace Setup

Use app.forgecloud.cc for your personal account, workspaces, projects and services. Forge staff administration uses a separate identity system.

Get Access

Use one of the currently available access paths:

• create an account when public registration is enabled; or
• accept an invitation sent by an existing workspace administrator.

When registration is unavailable, use a valid workspace invitation or wait until registration reopens. Customer accounts are not created through the Forge staff console.

Verify Your Account

Forge sends a short-lived verification code to the exact email address being registered. Enter that code in the same account flow. Codes expire, are single-purpose, and must not be shared.

After verification, enroll MFA when the workspace policy requires it. Store recovery codes in a password manager.

Your Workspace Plan

A workspace created through public registration starts on the Free plan unless you choose a 14-day trial of Starter or Pro when you sign up. Free does not expire and needs no payment method. It includes:

• one connected VPS;
• one member, so inviting a teammate requires a paid plan;
• 30 deployments per calendar month (UTC);
• no project or service count limit, within the capacity of that VPS and the acceptable-use policy.

Free includes custom domains with automatic HTTPS, served by your own server. It does not include email sending or email domains, database backups or point-in-time recovery, Forge-managed runtime, or add-ons. Backups you already have stay available to download and restore; Free only stops you creating new ones.

A trial needs no card either. When it ends, the workspace moves to Free and you have seven days before Free’s limits apply to what you already have. After that date only the first owner keeps access, other members are suspended rather than removed, and only your oldest connected server can start new deployments. Nothing is deleted, apps already running keep running, and choosing a paid plan restores everything at once. Workspace Settings → Billing shows current usage against these limits and, when billing is enabled, the paid plans you can upgrade to. A limit is enforced when you add a resource.

Understand Workspace Membership

A personal account can belong to multiple workspaces. Each workspace remains an independent authorization boundary with its own projects, members, servers and settings.

Use the workspace selector before creating or changing a resource. The selected workspace controls which projects, servers and invitations are visible. Membership in one workspace does not expose another workspace’s resources.

Workspace roles determine which actions are available. Project-level membership can narrow access further. Forge’s API remains authoritative even when a control is hidden in the interface.

Connect GitHub

Open Workspace Settings → Connections and connect the GitHub App installation that grants the workspace access to the required repositories. Forge verifies the installation against the signed-in GitHub user and records the workspace connection.

The same GitHub installation may be authorized for more than one Forge workspace. Repository access still resolves through the requesting workspace and project, and a service can select only a repository granted by that installation.

Do not paste a GitHub client secret, App private key or platform access token into a project variable. Customer repository access uses the workspace connection and short-lived installation credentials.

Next Steps

1. Connect a VPS.
2. Create your first project.
3. Add project services and variables.
4. Add custom domains only after a service is healthy on the intended server.