//
Open-source CI/CD system with container-native pipelines
Woodpecker CI is a German-led open-source continuous integration system, a community fork of Drone CI, offering container-native pipelines with simple YAML configuration. Created in 2022 when Drone's open-source direction shifted after its acquisition, Woodpecker preserves the original simplicity while adding multi-platform support, improved extensibility, and an active community governance model.
Headquarters
Germany, Germany
Founded
2022
Pricing
EU Data Hosting
Yes
Employees
1-10
Open Source
Yes
Free
Billing: free
Picture this: your team has been running Drone CI for two years. The YAML pipelines are clean, the Docker-based execution model fits your workflow perfectly, and the lightweight agent runs happily on a modest VM alongside your other services. Then Drone gets acquired by Harness, the community edition is restricted, and suddenly your CI/CD system's future is uncertain. Do you migrate to GitLab CI and rewrite every pipeline? Adopt GitHub Actions and accept vendor lock-in? Spin up a Jenkins instance and step back a decade?
Or do you switch to Woodpecker CI — a community fork that picked up exactly where Drone left off, preserving the simplicity while adding the features the community had been requesting.
Woodpecker CI emerged in 2022 as a direct response to Drone CI's acquisition by Harness and the subsequent changes to its open-source licensing. Led by German developers and maintained by an active community, Woodpecker preserves Drone's core philosophy — container-native pipelines defined in simple YAML — while extending it with multi-platform support, improved plugin handling, and transparent community governance under the Apache 2.0 licence.
The result is a CI/CD system that does exactly what a CI/CD system should do: run your pipelines reliably, in containers, on your own infrastructure. It does not try to be a deployment platform, a feature flag service, or an observability tool. It builds and tests your code, runs your defined steps, and reports the results. For teams that value simplicity and data sovereignty over managed convenience, Woodpecker CI is a quiet revelation.
Every pipeline step in Woodpecker runs inside a Docker container. This means your builds are isolated, reproducible, and portable. A pipeline that runs on your local Woodpecker instance will produce the same results in any environment running the same container images. There is no "works on the CI server but not on my machine" problem, because the CI server is running the same containers you use in development.
Pipeline configuration is written in YAML, with a syntax that will be immediately familiar to anyone who has used Drone, GitHub Actions, or GitLab CI. A basic pipeline that checks out code, runs tests, and builds a Docker image takes perhaps 15 lines of YAML. There is no DSL to learn, no plugin framework to master, and no proprietary configuration language.
Woodpecker runs agents on Linux, Windows, macOS, and ARM architectures. This multi-platform support means you can build and test software for any target platform using native execution rather than emulation. ARM support is particularly valuable for teams building for Raspberry Pi, IoT devices, or ARM-based cloud instances.
The agent model is straightforward: install the Woodpecker agent on any machine, point it at your Woodpecker server, and it begins accepting pipeline jobs. You can run as many agents as you need, on any mix of platforms, without per-agent licensing or usage fees.
Woodpecker integrates natively with GitHub, GitLab, Gitea, Forgejo, and Bitbucket. The integration handles webhook events, status reporting, and repository synchronisation. For teams using Gitea or Forgejo — both popular European-led alternatives to GitHub — Woodpecker provides first-class CI/CD support that these platforms do not offer natively.
The forge integration is where Woodpecker adds meaningful value over Drone. Support for Forgejo (the community fork of Gitea) was added in response to community demand, reflecting the project's responsiveness to its user base.
Beyond the Docker-based agent, Woodpecker supports a Kubernetes backend that schedules pipeline steps as Kubernetes pods. This is valuable for teams already running Kubernetes who want their CI/CD workloads to share the same cluster. The K8s backend handles resource allocation, pod scheduling, and cleanup automatically.
Woodpecker plugins are standard Docker images with a defined interface for receiving pipeline metadata. This means any Docker image can function as a Woodpecker plugin with minimal adaptation. The official plugin registry includes common CI/CD tasks — Docker builds, S3 uploads, Slack notifications, SSH deployment — and the community contributes additional plugins regularly.
The plugin ecosystem is smaller than GitHub Actions' marketplace or GitLab's template library. However, the Docker-based plugin model means that anything you can do in a container, you can do in a Woodpecker pipeline step. If a dedicated plugin does not exist for your use case, a few lines of custom shell commands in a standard container will usually suffice.
Woodpecker provides encrypted secret storage at both the repository and global (organisation) level. Secrets are injected as environment variables into pipeline steps and are masked in build logs. While functional, the secret management is more basic than dedicated solutions like HashiCorp Vault — there is no dynamic secret generation, rotation policies, or fine-grained access controls beyond repository-level scoping.
Woodpecker CI is entirely free. The project is released under the Apache 2.0 licence with no paid tiers, no usage limits, no premium features held back, and no commercial support offerings. You can run unlimited pipelines, connect unlimited repositories, and deploy as many agents as your infrastructure supports.
The only cost is the infrastructure to run it. The Woodpecker server and a single agent can comfortably share a VM with 1-2 GB of RAM — a cost of perhaps three to five euros per month on Hetzner or a similar European cloud provider. For the capabilities you get, this makes Woodpecker one of the most cost-effective CI/CD solutions available.
The trade-off, naturally, is that there is no commercial support. If something breaks at 2 AM, your options are the community Matrix channel, GitHub Issues, and your own expertise. For teams with the operational maturity to manage self-hosted infrastructure, this is a reasonable trade-off. For teams that need guaranteed response times and a support hotline, a managed solution like GitLab CI or GitHub Actions may be more appropriate.
Woodpecker CI's compliance story is uniquely straightforward: there is nothing to comply with, because no data leaves your infrastructure. Woodpecker is entirely self-hosted. Build logs, secrets, pipeline configurations, and artifacts all reside on your servers. There is no telemetry, no usage tracking, no external API calls (beyond the forge webhooks you configure), and no cloud dependency.
This makes Woodpecker inherently GDPR compliant for CI/CD purposes. If your source code and build artifacts stay on EU infrastructure, your CI/CD data stays on EU infrastructure. There are no data processing agreements to negotiate, no subprocessor lists to review, and no data transfer impact assessments to conduct.
The open-source codebase is fully auditable. You can inspect every line of code that runs on your infrastructure, verify that no data is exfiltrated, and modify the software to meet specific compliance requirements. For organisations in regulated industries — finance, healthcare, government — this level of transparency is difficult to achieve with any managed CI/CD service.
Self-hosting enthusiasts and small teams who want CI/CD without vendor lock-in or monthly bills. If you are comfortable running Docker on a VPS, you can have Woodpecker running in under an hour.
Gitea and Forgejo users who need native CI/CD integration for their self-hosted Git platform. Woodpecker is the strongest CI/CD option for these increasingly popular European-led forge alternatives.
Regulated organisations that cannot send source code or build artifacts to third-party services. Woodpecker's fully self-hosted model eliminates external data flows entirely.
Teams migrating from Drone CI who want a drop-in replacement with active maintenance and community governance. Woodpecker's pipeline syntax is largely compatible with Drone configurations.
Cost-conscious teams that need CI/CD for multiple projects without per-user or per-minute pricing. Woodpecker's unlimited usage model is particularly attractive for open-source projects and small businesses.
Woodpecker CI embodies a philosophy that is increasingly rare in DevOps tooling: do one thing, do it well, and let the user own their infrastructure. It will not impress with a slick marketing site or a sprawling feature matrix. What it will do is reliably build and test your code in containers, on your hardware, with zero vendor lock-in and zero recurring cost. The trade-offs — no managed offering, smaller plugin ecosystem, community-only support — are real. But for teams that value sovereignty, simplicity, and self-reliance, Woodpecker CI is a tool that earns its place in the stack.
Yes. Woodpecker CI is fully free and open-source under the Apache 2.0 licence. There are no paid tiers, usage limits, or premium features. You only pay for the infrastructure you host it on.
Woodpecker CI is a community fork of Drone CI, created after Drone was acquired by Harness and shifted its open-source direction. Woodpecker preserves Drone's simplicity while adding multi-platform support, improved plugin handling, and community-driven governance.
For many use cases, yes. Woodpecker supports container-native pipelines, matrix builds, and integrates with GitHub, GitLab, and other forges. However, it has a smaller plugin ecosystem and requires self-hosting, whereas GitHub Actions is a managed service.
Because Woodpecker CI is entirely self-hosted, all build data, secrets, and logs remain on your own infrastructure. There is no telemetry, no external data collection, and no cloud dependency. This makes it inherently GDPR compliant.
Woodpecker CI supports GitHub, GitLab, Gitea, Forgejo, and Bitbucket as source code management backends. It can also be extended to work with other Git hosting platforms through its API.
Visual CI/CD pipeline builder for web developers