Pick Namespace if
cI teams who will stay on Developer at $0 (pay-as-you-go) while they open a first GitHub Actions Overview, then buy Team at $100 / month when they want the included build pack and more cache allowance.
Read the Namespace pageNamespace vs Woodpecker
Our take
Pick Namespace if cI teams who will stay on Developer at $0 (pay-as-you-go) while they open a first GitHub Actions Overview, then buy Team at $100 / month when they want the included build pack and more cache allowance. Pick Woodpecker if teams who already run Gitea / Forgejo / GitHub and will stay on the Apache self-host at $0 while they open a first pipeline log, then keep self-hosting because Woodpecker does not
Woodpecker
open-source CI desk
Best for
Namespace Actions minutes and remote boxes you start at $0
Woodpecker Pipelines you start at $0 on your host
Free plan
Namespace $0 · pay as you go. Devbox from $0.004 / min. Builds $0.05 / build. Registry / Turbo / Gradle / GitHub Artifacts $0.2 / GB-month
Woodpecker $0 · apache-2.0. You run the server + one or more agents + a forge. Confirmed by the repo LICENSE (“Apache License / Version 2.0”)
Lowest paid
Namespace Meters that stay on every tile $0.004
Woodpecker Not published by the vendor
Next step up
Namespace Business $250
Woodpecker
Coding agent
Namespace
Woodpecker Pipelines
Runs where
Namespace Local or hosted
Woodpecker
Watch out
Namespace Developer $0 is pay-as-you-go, not unlimited minutes
Woodpecker $0 is the license, not the agent VM
Last checked
Namespace 2026-10-23 · namespace.so/pricing
Woodpecker 2026-10-23 · github.com/woodpecker-ci/woodpecker/blob
Which one, then?
Pick Woodpecker if
teams who already run Gitea / Forgejo / GitHub and will stay on the Apache self-host at $0 while they open a first pipeline log, then keep self-hosting because Woodpecker does not print a hosted Cloud dollar.
Read the Woodpecker page