Connect a VPS
Forge Cloud does not require you to install the Forge control plane on your VPS. You connect a server by installing only the Forge Agent generated for your workspace.
Requirements
Section titled “Requirements”- A customer-owned VPS running a supported Ubuntu release.
- SSH access with
sudofor the initial installation. - A static public IP address.
- Outbound HTTPS access so the Agent can register and receive signed jobs.
- Ports
80and443available when the server will host public web services. - PostgreSQL, Redis and other database ports closed publicly unless you explicitly enable a supported public endpoint.
- No unrelated customer workloads on a server intended for qualification or recovery testing.
Create The Server Registration
Section titled “Create The Server Registration”- Sign in at
app.forgecloud.ccand select the correct workspace. - Open Servers.
- Choose Connect server.
- Enter a name that identifies the VPS and its purpose.
- Create the shortest practical one-time registration token.
- Copy the exact installation command shown by Forge.
The command contains a short-lived registration credential. Treat it as a secret, do not add it to shell history or source control, and discard it after installation.
Install The Agent
Section titled “Install The Agent”SSH into the VPS and run the exact command produced by Forge. Do not substitute a command from another workspace or server registration.
The installer creates a dedicated Agent installation, registers the server once, installs its service, and starts the Agent. It does not install a second Forge control plane and does not grant a general interactive shell through Forge.
Return to Servers and require all of the following before selecting the server for a workload:
- the server belongs to the expected workspace;
- its status is healthy;
- its trust and Agent version are visible;
- its reported hostname and addresses match the VPS;
- no warning indicates an expired registration, unsupported Agent, or missing capability.
Network Boundary
Section titled “Network Boundary”The Agent initiates its control-plane connection over HTTPS. Do not expose Docker, the Docker socket, PostgreSQL, Redis or an Agent management port to the public internet.
Public application traffic is separate. Forge opens and routes only the application or database endpoints you explicitly configure. Review every generated DNS record before publishing it.
Removing A Server
Section titled “Removing A Server”Move or remove project workloads before revoking a server. Revocation prevents new Agent work but does not prove that application containers, volumes, DNS records or credentials have been removed from the VPS. Complete the cleanup and recovery checks shown by Forge before deleting or repurposing the host.
Next Step
Section titled “Next Step”Continue to First Project and select this server when a supported service asks for a deployment target.