Woodpecker CI vs GitHub self-hosted runners
Both are alternatives to GitHub Actions. Here's how they stack up — verified facts, no spin.
Also searched as GitHub self-hosted runners vs Woodpecker CI — same comparison, one verdict.
Woodpecker CI
TOP PICKA small, container-native CI server you can run on one box.
Woodpecker is a community fork of Drone that stayed Apache-2.0 after Drone's licence changed. Every pipeline step is a container, the config is a single YAML file, and the whole server is one Go binary plus an agent — it will run comfortably on hardware you would otherwise consider too small for CI. It plugs into GitHub, GitLab, Gitea, Forgejo and Bitbucket, so you can keep hosting code where it is and simply move the build minutes onto your own machine. Of everything here it is the least ceremony for the most control.
GitHub self-hosted runners
Keep the workflows, move the minutes onto your own machine.
Not a replacement for Actions but the cheapest fix for its bill: register your own machine as a runner and change one line — `runs-on: self-hosted`. The workflows, the marketplace actions, the pull-request integration and the secrets all stay exactly as they are, and the per-minute charge stops. It is the highest-leverage move in this comparison for most teams. Two cautions. Self-hosted runners are not recommended for public repositories, because a pull request from anyone can execute code on your hardware. And the free status of these minutes is a policy, not a guarantee: GitHub announced a $0.002/min fee on them for March 2026 and postponed it indefinitely after the reaction, which tells you both that the risk is real and that pushing back worked.
Side by side
| Woodpecker CI | GitHub self-hosted runners | |
|---|---|---|
| Sovereignty Score | 93 | 45 |
| Open source | Yes | No |
| Self-hostable | Yes | Yes |
| Local-first | Yes | No |
| License | Apache-2.0 | Proprietary (runner agent is MIT; the service is GitHub's) |
| Pricing | Free and open source. You pay only for the machine it runs on. | No per-minute charge as of 2026-07-30 — you pay only for the machine. The announced platform fee remains postponed, not cancelled. |
Woodpecker CI is Macrostack's recommended GitHub Actions alternative, so it's our pick here.
Woodpecker CI
Strengths
- +Genuinely Apache-2.0 with no enterprise carve-out
- +Container-per-step model — the pipeline is portable by construction
- +Runs against GitHub, GitLab, Gitea, Forgejo and Bitbucket
- +Light enough for a small VPS; no database cluster required
Trade-offs
- −Small ecosystem — no marketplace of ready-made actions
- −You own the runner: patching, disk space and caching are yours
- −No hosted option, so there is nobody to page at 3am
- −Windows and macOS builds need machines you supply
GitHub self-hosted runners
Strengths
- +Zero migration: one line of YAML, everything else unchanged
- +Removes the minute bill immediately, including for large runners
- +Lets you use hardware GitHub does not offer — GPUs, ARM, big disks
- +Keeps the marketplace ecosystem and PR integration intact
Trade-offs
- −You are still entirely inside GitHub's pricing decisions — the fee was deferred, not withdrawn
- −Unsafe on public repositories: forked PRs would run on your machine
- −You own patching, isolation and cleanup between jobs
- −No sovereignty gain — this is a cost fix, not an independence fix
Related alternative guides
Facts verified 2026-07-30. Licenses and pricing change — spotted something out of date? That's a correction we want.