Back to catalog
Woodpecker CI
Apache-2.0Woodpecker CI is an open-source, container-based CI/CD engine that replaces CircleCI by running lightweight pipelines across your own infrastructure.
Open-source alternative to — compare it against:
Overview
Woodpecker CI is a container-native continuous integration and delivery engine written in Go. It connects directly to cloud and self-hosted Git repositories to execute automated build, test, and deployment workflows inside isolated containers. Repository YAML files define pipeline steps, keeping automation logic alongside application code under local control.
Why Woodpecker CI instead of CircleCI
CircleCI relies on a hosted cloud service with proprietary execution environments and custom Orbs for pipeline extension. Woodpecker CI shifts execution to your infrastructure, running every step in standard container images. Where CircleCI directs teams toward its cloud ecosystem, Woodpecker integrates natively with diverse Git forges. A single deployment connects to Forgejo, Gitea, GitLab, GitHub, or Bitbucket through webhooks and OAuth, preserving developer logins without routing source code through external SaaS servers.
The operational divide centers on infrastructure integration and plugin architecture. CircleCI workflows depend on proprietary syntax and reusable Orbs that bind pipelines to the vendor platform. Woodpecker uses standard OCI container images as pipeline steps, making plugins language-agnostic executables configured via environment variables. It also integrates with diverse backends, scheduling jobs across local Docker daemons, Kubernetes clusters, or bare-metal agents. Teams trade away CircleCI hosted macOS fleets and managed compute pools for zero per-seat licensing fees, complete data residency, and direct runner control.
What it does well
- Multi-forge authentication: Connects with Gitea, Forgejo, GitLab, GitHub, and Bitbucket, unifying CI workflows across public repositories and internal servers.
- Container step isolation: Runs each pipeline step in a dedicated container image, ensuring clean build environments without residual state.
- Pluggable backends: Dispatches jobs to local Docker daemons, Kubernetes clusters, or SSH targets, supporting single-node servers and auto-scaling clusters.
- Modular plugins: Implements pipeline extensions as container images, enabling developers to create custom build tasks in any language.
- Lightweight footprint: Operates as a minimal Go binary using roughly 100 megabytes of memory on the server with an embedded SQLite database.
- Pipeline DAG dependencies: Defines parallel and sequential execution flows using explicit step dependencies.