Freedom251 › Continuous Integration Software
Woodpecker CI
What Woodpecker CI is
Woodpecker CI is a free, open-source CI/CD engine for running project pipelines in a self-hosted installation. Pipeline steps run in Docker containers, and plugins can add capabilities. A project can use several workflows that depend on one another, with pipeline configuration written in YAML. Supported forges can start pipelines for events such as pushes, tags, and pull requests. Woodpecker documents connections to GitHub, Gitea, Forgejo, GitLab, Bitbucket, and Bitbucket Datacenter, although available features vary across them. Release events are not supported for the two Bitbucket options.
Agents can run jobs through Docker, Kubernetes, or Local backends, depending on the host operating system. The Local backend executes commands directly on the agent host without isolation, so it is intended for trusted private setups. Woodpecker is distributed as container images and pre-built binaries; official DEB and RPM packages are available for Linux amd64 and arm64. It uses OAuth2 through a configured forge for user authentication, with no separate Woodpecker registration. SQLite is the default database, and PostgreSQL and MySQL are also supported. The project says the software will remain free. Founded in 2019, Woodpecker began as a fork of Drone 0.8.
Who it suits
Woodpecker CI suits teams that want a free, self-hosted pipeline engine connected to a supported code forge. It can fit projects that need YAML pipelines, dependent workflows, plugins, and a choice of execution backends, provided the selected backend is available on their operating system.
What it does well
- Free, open-source software with self-hosted installation.
- Pipeline steps run in Docker containers.
- Supports dependent workflows and YAML configuration.
- Forge connections include GitHub, Gitea, Forgejo, GitLab, and Bitbucket.
- Docker, Kubernetes, and Local execution backends are available.
- Artifact or dependency caching is supported.
What to know first
- There is no hosted option.
- Backend availability varies by operating system.
- The Local backend runs without isolation.
- Bitbucket and Bitbucket Datacenter do not support release events.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Woodpecker CI | Free; Woodpecker says it will always be free. · Open-source CI/CD engine · self-hosted installation | Free |
As woodpecker-ci.org lists them, read 7 Oct 2026. The maker's own page has the final word.
Getting started
- Open the Woodpecker CI website.
- Choose a supported installation route: container image, pre-built binary, or an official Linux DEB or RPM package.
- Deploy a server and agent; the Docker Compose guide uses persistent server data and shared-secret authentication between them.
- Configure OAuth2 authentication through a supported forge.
- Connect a project and define its pipeline in YAML.
Verdict
Pick Woodpecker CI if you want free, self-hosted CI/CD with forge integrations and configurable execution backends. Teams running untrusted code should account for the Local backend's lack of isolation and choose an available backend suited to their setup.
Questions
Is Woodpecker CI free?
Yes. The project describes Woodpecker as open source and free, and says it will always be free.
Is there a hosted version?
No hosted option is listed; the installation is self-hosted.
Which forges can connect to Woodpecker?
Documented integrations include GitHub, Gitea, Forgejo, GitLab, Bitbucket, and Bitbucket Datacenter. Feature support differs by forge.
How does user authentication work?
Woodpecker uses OAuth2 through the configured forge and does not provide its own user registration.
Which databases are supported?
SQLite is the default. PostgreSQL and MySQL are also listed.
What should I know about the Local backend?
It runs pipeline commands on the agent host without isolation and is recommended only for trusted private setups.
Facts from Woodpecker CI's own pages
- Database
- Woodpecker uses SQLite by default; PostgreSQL and MySQL are also listed as database options. · woodpecker-ci.org, 7 Oct 2026
- Deployment
- The Docker Compose guide shows a server and agent deployment, persistent server data, and shared-secret authentication between the server and agents. · woodpecker-ci.org, 7 Oct 2026
- Execution backends
- Agents can use Docker, Kubernetes, or Local backends, with backend availability varying by host operating system. · woodpecker-ci.org, 7 Oct 2026
- Extensions
- External HTTP extensions can modify or generate pipeline configuration and provide registry credentials or secrets. · woodpecker-ci.org, 7 Oct 2026
- Extension security
- Woodpecker signs HTTP requests to extensions, which may receive private information and return configurations that can be executed. · woodpecker-ci.org, 7 Oct 2026
- Forge integrations
- Built-in forge support includes GitHub, Gitea, Forgejo, GitLab, Bitbucket, and Bitbucket Datacenter. · woodpecker-ci.org, 7 Oct 2026
- Founded
- 2019 · woodpecker-ci.org, 28 Sept 2026
- Installation
- Woodpecker is distributed as container images and pre-built binaries; official DEB and RPM packages are built for Linux amd64 and arm64. · woodpecker-ci.org, 7 Oct 2026
- Local backend limitation
- The local backend runs pipeline commands on the agent host without isolation and is recommended only for trusted private setups. · woodpecker-ci.org, 7 Oct 2026
- Multiple forges
- Connecting multiple forges is described as experimental and is not recommended for public or otherwise untrusted environments. · woodpecker-ci.org, 7 Oct 2026
- Pipeline events
- Supported forges can trigger pipelines on events such as pushes, tags, and pull requests; release events are not supported for Bitbucket or Bitbucket Datacenter. · woodpecker-ci.org, 7 Oct 2026
- Pipeline execution
- Woodpecker runs pipeline steps in Docker containers, and plugins can extend pipeline features. · woodpecker-ci.org, 7 Oct 2026
- Platform support
- The supported-platforms page lists Windows, macOS, and Linux builds for selected components and architectures; backend availability varies by operating system. · woodpecker-ci.org, 7 Oct 2026
- Price
- The project says Woodpecker is open source and free, and will always be totally free. · woodpecker-ci.org, 7 Oct 2026
- Project history
- Woodpecker was forked from Drone 0.8 in 2019 and was originally forked by @laszlocph. · woodpecker-ci.org, 7 Oct 2026
- Purpose
- Woodpecker is a CI/CD engine with extensibility. · woodpecker-ci.org, 7 Oct 2026
- Secret handling
- Woodpecker supports repository, organization, and global secrets, and warns that externally sourced secrets may be exposed in pipeline logs. · woodpecker-ci.org, 7 Oct 2026
- Security limitation
- The Local backend runs pipeline commands without isolation and is recommended only for private setups where code and pipelines are trusted. · woodpecker-ci.org, 7 Oct 2026
- Support channels
- The project lists Matrix, Mastodon, and Bluesky as community links. · woodpecker-ci.org, 7 Oct 2026
- User access
- Woodpecker uses OAuth2 authentication through the configured forge and does not have its own user registration. · woodpecker-ci.org, 7 Oct 2026
- Workflows
- A project can have multiple workflows that depend on one another. · woodpecker-ci.org, 7 Oct 2026
Where Woodpecker CI stands on Freedom251
- Continuous Integration Software#38 of 58
- Ci Cd Platforms#20 of 28
- Game Build Automation Software#33 of 43