Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host GoCD
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A continuous delivery server built around pipelines: each pipeline is a chain of stages and jobs, run by agents, with a value stream map that shows how a change flows from commit to production. Pipelines are edited in the web UI or kept as code in a repository (YAML, JSON or Groovy), and plugins add authentication, secrets and elastic agents. The server stores its configuration, history and artifacts in one data directory.
Pick GoCD when you want to model delivery as a chain of stages and watch it as one value stream: each pipeline has stages and jobs, a pipeline can be triggered by another pipeline's output, and the value stream map shows how a commit travels towards production. You can edit pipelines in the web UI or keep them as code (YAML, JSON or Groovy) in a repository, and plugins add authentication, secrets and elastic agents. It is Java and TypeScript on Jetty, licensed Apache-2.0, and keeps its configuration, history and artifacts under one data directory. Our snippet runs the official `gocd/gocd-server:v26.1.0` image (released 2026-07-06) with that directory on a bind mount. GoCD's system requirements give 1 GB of RAM as the minimum and 2 GB as recommended, 2 CPU cores and 1 GB of free disk for the server; our 1024 MB floor is the minimum, so give it 2 GB for real use. In the catalog, Jenkins is the plugin-heavy general automation server, Woodpecker and Drone run a YAML file per repository, and Concourse also treats the pipeline as the unit but as YAML resources and fresh containers; GoCD is the one built around the pipeline-of-pipelines model and its dependency graph, and it does not need a forge login.
What you need
Any VPS with at least 1024 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
About an afternoon — budget time for troubleshooting
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# GoCD server — adapted from the gocd-server image README, pinned to v26.1.0 (no agent included: see the note below)mkdir -p godata && sudo chown 1000:1000 godatacat > docker-compose.yml <<'EOF'services: gocd-server: image: gocd/gocd-server:v26.1.0 restart: unless-stopped ports: - 8153:8153 volumes: - ./godata:/godataEOFdocker compose up -dtimeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:8153/go/api/v1/health; do sleep 3; done'# → http://SERVER_IP:8153 — no login is required until you configure authentication (Admin → Security), so do that before exposing the port; builds need an agent (gocd/gocd-agent-wolfi) approved under the Agents tab
GoCD's documentation and the server image's README flag these before you rely on it:
non-negotiableThe server runs with no authentication until you configure it: anyone who can reach port 8153 has access to the whole UI. Set up a password file or an authentication plugin under Admin, Security before you expose the port.
non-negotiableThe server alone builds nothing. Jobs run on agents, and our snippet does not include one: start the gocd/gocd-agent-wolfi image (or another agent image) with GO_SERVER_URL=http://<server>:8153/go, then enable it under the Agents tab; the agent image README says GO_SERVER_URL must end in /go.
non-negotiableStartup is not instant, since this is a Java server: wait for the health endpoint (/go/api/v1/health) instead of trusting the first page load. The image runs as the go user (uid 1000), so the /godata bind mount must be writable by it; our snippet chowns the directory.
non-negotiableThe default embedded H2 database is fine for a trial but the docs offer PostgreSQL and MySQL for larger installations; the system requirements page also recommends a separate partition for artifacts. Back up the godata directory, which holds the database, configuration and artifacts.
non-negotiableRunning agents in containers needs a decision about how they get a Docker daemon (socket mount or an elastic-agent plugin), which the server image does not make for you.