selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

woodpecker-ci logo

Self-host woodpecker-ci

v3.20.1

Container-based CI/CD engine driven by your git forge

ReleaseOpen SourceApache-2.0
Updatedlast week
LanguageGo
Setup difficultyModerate
Stars
8 129
RAM
around 100 MB (Server) and 30 MB (Agent) at runtime in idle mode
Ports
8000 (HTTP listener of the server (Web UI and API)), 9000 (gRPC listener the agents connect to), 443 (HTTPS listener, used when SSL is enabled)
Requires
Docker
Docker
woodpeckerci/woodpecker-server
Install with Docker Compose
Woodpecker's pipeline view shown in the README

What is woodpecker-ci?

woodpecker-ci alternatives

Should you self-host woodpecker-ci?

woodpecker-ci scores 74/100 on selfhost.directory (how scoring works) and ranks #5 of 28 in CI/CD. It has 8 129 GitHub stars, +177 in the last 30 days.

It shipped 12 stable releases in the past year. The latest, v3.20.1, came out on 29 October 2026. New versions land roughly every 3 weeks.

Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is Apache-2.0-licensed and written mostly in Go.

Its closest alternative on selfhost.directory is jenkins (83/100, 26 736 stars). It scores higher overall, so compare the two before you pick. See woodpecker-ci vs jenkins side by side.

Features

  • Access control via organizations and admins
  • Addon forges and plugins
  • Autoscaling agents on cloud VMsOptional component, needs a supported cloud provider.
  • CLI Client
  • Cron Job Scheduling
  • Forge-based event triggers
  • Matrix workflows
  • Multiple execution backends (Docker, Kubernetes, Local)
  • Multiple workflows with dependencies
  • Plugin extensibility
  • REST API
  • Secrets Management
  • Services and volumes in workflows
  • Status badges

woodpecker-ci README

How to install woodpecker-ci

Install woodpecker-ci with Docker Compose

Environment variables
WOODPECKER_OPEN, WOODPECKER_HOST, WOODPECKER_GITHUB, WOODPECKER_GITHUB_CLIENT, WOODPECKER_GITHUB_SECRET, WOODPECKER_AGENT_SECRET, WOODPECKER_SERVER
services:
  woodpecker-server:
    image: woodpeckerci/woodpecker-server:v3
    ports:
      - 8000:8000
    volumes:
      - woodpecker-server-data:/var/lib/woodpecker/
    environment:
      - WOODPECKER_OPEN=true
      - WOODPECKER_HOST=${WOODPECKER_HOST}
      - WOODPECKER_GITHUB=true
      - WOODPECKER_GITHUB_CLIENT=${WOODPECKER_GITHUB_CLIENT}
      - WOODPECKER_GITHUB_SECRET=${WOODPECKER_GITHUB_SECRET}
      - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}
  woodpecker-agent:
    image: woodpeckerci/woodpecker-agent:v3
    command: agent
    restart: always
    depends_on:
      - woodpecker-server
    volumes:
      - woodpecker-agent-config:/etc/woodpecker
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      - WOODPECKER_SERVER=woodpecker-server:9000
      - WOODPECKER_AGENT_SECRET=${WOODPECKER_AGENT_SECRET}
volumes:
  woodpecker-server-data:
  woodpecker-agent-config:

Example is wired to GitHub (WOODPECKER_GITHUB=true); you must register an OAuth App with your forge first. The agent needs the host Docker socket.

How to configure woodpecker-ci

  • WOODPECKER_OPENfalseEnable to allow user registration.

    values: true, false

  • WOODPECKER_ADMINComma-separated list of users made administrators.
  • WOODPECKER_HOSTnoneServer fully qualified URL of the user-facing hostname, port (if not default for HTTP/HTTPS) and path prefix.
  • WOODPECKER_GITHUBEnables the GitHub forge driver.

    values: true, false

  • WOODPECKER_GITHUB_CLIENTOAuth App client ID of the GitHub forge.

woodpecker-ci releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

More in CI/CD

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…