Software Delivery & Version Control

Woodpecker CI

Updated

Visit website
01 / Overview

What is Woodpecker CI?

Woodpecker CI builds software through container-based continuous integration pipelines.

Who is Woodpecker CI for?

Teams evaluating Woodpecker CI for software delivery & version control workflows, particularly container pipelines and build automation. Check the edition and intended deployment before selecting a package.

02 / Capabilities

Woodpecker CI features

The core capabilities to consider for your workflow.

  • Container pipelines
  • Build automation
  • Repository integrations
03 / Plans & costs

Woodpecker CI pricing

Plan availability

Open-source software

Review the software licence and distribution, then scope infrastructure, maintenance and support. Commercial hosting, proprietary extensions and managed services can be priced separately.

Calculate the cost of your quote →

Free access & evaluation

An open-source software edition is available. Check the exact licence and distribution; hosting, operation, support and separately licensed extensions may still cost money.

04 / Buying checklist

Before you choose Woodpecker CI

  • Does the tool support the repository, artifacts, build agents and deployment targets you need?

  • Which users, storage, execution resources and support arrangements are included?

05 / Related software

Explore related software

06 / Questions answered

Woodpecker CI FAQs

Does Woodpecker CI have a free plan?

An open-source software edition is available. Check the exact licence and distribution; hosting, operation, support and separately licensed extensions may still cost money.

Who is Woodpecker CI for?

Teams evaluating Woodpecker CI for software delivery & version control workflows, particularly container pipelines and build automation. Check the edition and intended deployment before selecting a package.

What should I compare before buying?

Check the tier that contains your essential features, confirm plan limits and compare the total quote with your own expected usage.