Woodpecker CI
App Definition & DeliveryWoodpecker CI is a self-hosted, container-native CI/CD pipeline engine written in Go. It executes pipelines defined in YAML, with each pipeline step running as its own container — the same execution model Drone CI popularized.
What it is
Woodpecker CI is a self-hosted, container-native CI/CD pipeline engine written in Go. It executes pipelines defined in YAML, with each pipeline step running as its own container — the same execution model Drone CI popularized. It's not a hosted SaaS product; you run the server, agents, and (optionally) a database yourself, and wire it up to your Git forge (GitHub, GitLab, Gitea, Forgejo, Bitbucket).
It's a fork of Drone CI, created after Drone's license moved to a source-available/BSL model and its governance shifted toward CloudBees' commercial roadmap. Woodpecker kept the Apache-2.0 license and the community-driven governance model.
Who builds it and why
Woodpecker is community-maintained — no single vendor owns it, no CNCF backing (not currently a CNCF project; maturity level not publicly available). 625 contributors on GitHub is a meaningful signal of a distributed maintainer base rather than a single-company side project. Commit activity through mid-2026 shows it's still actively worked on, not abandoned.
The project exists specifically because a chunk of the Drone user base didn't want to follow Drone into a more commercially-gated future. That's the core motivation: keep a simple, forkable, Apache-licensed CI engine alive under community control, without a company deciding which features go behind a paywall.
Production readiness signal
- 7,334 GitHub stars — respectable adoption for a self-hosted CI tool, well below Jenkins/GitLab CI/Tekton scale but not a toy project.
- 625 contributors — healthy bus factor, reduces single-maintainer risk.
- Latest release v3.16.0 — a major version number that high suggests years of iteration and breaking-change cycles already absorbed; this isn't a v0.x experiment.
- Last commit 2026-06-30 — actively maintained, not stale.
- Apache-2.0 — no license-change risk hanging over your head the way Drone users experienced.
- No CNCF maturity rating exists because it's not in CNCF's project pipeline as far as public data shows — so you don't get that external vetting signal. You're relying on GitHub activity and community reputation instead.
Net: it looks stable enough for production use by teams comfortable operating their own CI infrastructure, but you won't find a vendor SLA or enterprise support contract backing it.
Who should use this
- Teams already running Gitea, Forgejo, or self-hosted GitLab who want CI that integrates natively without SaaS dependency.
- Organizations burned by (or wary of) Drone's licensing shift, wanting an Apache-2.0 escape hatch with a similar mental model.
- Platform teams comfortable running and patching their own CI server/agent infrastructure, and who want simple, container-first pipeline semantics without Jenkins' plugin sprawl or Tekton's Kubernetes-native complexity.
- Small-to-mid-size engineering orgs that want straightforward YAML pipelines and don't need enterprise governance features (audit logs, SSO at scale, RBAC depth) out of the box.
Who should NOT use this
- Teams that need vendor support contracts or SLAs — there isn't a commercial entity behind Woodpecker to call when something breaks at 3am.
- Organizations already deep in Kubernetes-native CI/CD (Tekton, Argo Workflows) — Woodpecker's execution model isn't Kubernetes-native by design, so you'd be running a parallel system.
- Enterprises needing mature RBAC, compliance certifications, or audit trails — this isn't where Woodpecker's contributor effort has concentrated.
- Anyone wanting hosted/managed CI with zero ops burden — Woodpecker gives you no managed offering; you own the uptime.
- Teams heavily invested in GitHub Actions' marketplace ecosystem — Woodpecker's plugin ecosystem is smaller and you'll be writing more custom container steps yourself.
Alternatives
- Drone CI — the project Woodpecker forked from; now BSL-licensed and commercially steered by CloudBees, similar architecture but different licensing philosophy.
- Tekton — Kubernetes-native CI/CD building blocks, CNCF-graduated, better fit if you're already Kubernetes-first and want deep K8s integration over simplicity.
- GitLab CI — bundled into GitLab, far larger ecosystem and enterprise features, but ties you to GitLab as your Git host.
Pricing
Fully open source, Apache-2.0, no paid tier, no dual-license model. You pay only in compute/infrastructure and your own engineering time to run it.