Is Woodpecker CI free and open source?

Updated

Yes. Woodpecker CI is open source and, according to its website, "is and always will be totally free." That statement covers the software itself: you can download, run, modify, and contribute to it without paying a license fee. It does not mean your total CI/CD cost is zero, because you still supply the infrastructure the pipelines run on.

What "free" actually covers

The project's own framing is straightforward: the source code is open source, and the software is free to use. In practice that means:

  • No license cost. You are not buying seats, build minutes, or a subscription from the project.
  • You can contribute. Because the code is open source, you can help evolve the project — bug fixes, features, docs, or plugins.
  • You can inspect and modify it. Open source means the implementation is available to read and change, which matters if you need to audit behavior or adapt it to your setup.

What it does not cover

Free software is not the same as free hosting. Woodpecker runs your pipeline steps in Docker containers, so the compute, storage, and network come from wherever you deploy it. If you self-host on your own machine or a server you already pay for, the marginal cost can be near zero. If you rent a VPS or cloud instance to run it, that bill is yours.

The same logic applies to maintenance: no vendor is charging you, but someone has to run upgrades, manage secrets, and keep the server healthy.

Open source and extensibility

The open-source nature connects directly to how you extend Woodpecker. Pipelines execute as Docker containers, and when a plain Docker image is not enough, you can write plugins to add pipeline features. Because the engine is open source, plugin and pipeline behavior is something you can verify rather than take on faith — useful when a step needs to do something unusual.

Woodpecker also supports multiple workflows for a project, and those workflows can depend on each other. That lets you split a large pipeline into stages that run in a controlled order instead of one long job.

How this differs from commercial CI/CD services

Dimension Woodpecker CI Typical commercial CI/CD service
Software cost Free, per the project Usually subscription or usage-based
Source code Open source, contributable Usually closed
Where pipelines run Your Docker environment Vendor-hosted runners (often with paid tiers)
Cost driver Your infrastructure and upkeep Seats, build minutes, or plan tier
Extension model Docker images and custom plugins Vendor-defined integrations and marketplace

The practical takeaway: choose Woodpecker when you want no license fee, control over where builds run, and the ability to read and modify the engine. Choose a commercial service when you would rather pay someone else to host runners and handle operations.

Before you decide

Two things are worth confirming for your own situation, since the project page does not spell them out:

  1. Where you will host it. Self-hosting shifts cost from a subscription to servers and maintenance.
  2. What your pipelines need. If your steps fit standard Docker images, setup is simpler; if not, plan for plugin work.

If you want to check current capabilities, workflow configuration, or contribution paths, the project's documentation is the authoritative source.