Announcing Proliferate
Proliferate
DeployGCP

GCP

Run the standard Docker deployment on a Compute Engine VM.

There is nothing GCP-specific about running Proliferate: provision a VM and run the standard Docker deployment on it. This page covers only the GCP-side setup.

Steps

Provision a VM

Create a Compute Engine instance running a recent Linux with Docker and Compose v2 installed. An e2-small (2 vCPU, 2 GB) with a 20 GB disk is enough to start; see Sizing & scaling.

Open ports

Create a firewall rule allowing inbound TCP 80 and 443 to the instance. Port 80 is needed for the automatic HTTPS certificate issuance, 443 for traffic.

Point DNS

Reserve a static external IP for the instance, then point a DNS name (for example proliferate.company.com) at it. Do this before bootstrapping so Caddy can issue a certificate on first boot.

Deploy

On the VM, run the guided installer (inspect it first):

curl -fsSLO https://raw.githubusercontent.com/proliferate-ai/proliferate/main/server/deploy/install.sh
less install.sh
sudo bash install.sh --domain proliferate.company.com

It resolves the newest server release, verifies its checksum, installs to /opt/proliferate, and boots the stack. See Docker on any server for every flag and what it does under the hood, including the manual setup path if you'd rather not run the installer script. It ends by printing a one-time setup token and a claim URL (https://<your-site>/setup); claim the instance in a browser, then work from that same URL. Point desktop apps at your server too if you need local repositories or a local AnyHarness runtime (Connect the desktop app).

On this page