Drone CI cost in 2026
./drone --self-hosted --docker-native
Drone CI is the open-source, Docker-native CI/CD platform that powered a generation of self-hosted pipelines before GitHub Actions and GitLab CI absorbed most of the market. It is still actively maintained under Harness ownership, still free, and still the simplest self-hosted option for teams that want a clean Docker-first model without the operational weight of Jenkins. This page works through what Drone actually costs to run in 2026, where it sits versus alternatives, and the trade-offs that show up in production.
The Drone community edition source and binaries are published at github.com/harness/drone. Documentation and configuration reference are at docs.drone.io. Cloud rates used below come from the AWS EC2 pricing page.
The licence and ownership picture
Drone CI core is Apache 2.0 licensed. You can download the binary, run it on any infrastructure, charge users to access it if you want to, and the project authors will not invoice you. Drone Enterprise is a commercial distribution from Harness that adds SSO, RBAC, audit logs and dedicated support. Most production Drone deployments use the community edition because the feature gap is small for teams that already run Drone-compatible auth (typically via the upstream Git provider's OAuth).
After the 2020 Harness acquisition, the project lost some of the community velocity it had during peak adoption (2018-2020). The Woodpecker CI fork formed in 2022 to maintain a fully community-governed alternative, and many teams who were uncertain about Harness's long-term intentions moved to Woodpecker. Drone itself remains supported and well-tested but it is a steady-state project rather than an aggressively growing one.
Self-hosted infrastructure cost
Drone is a single Go binary controller plus separate runner binaries that you point at your VMs, Kubernetes cluster, or container hosts. The architecture is small enough that the controller and a single Docker runner can share one VM for low-volume teams.
| Setup | AWS instance | Monthly cost | Throughput |
|---|---|---|---|
| Solo dev | t3.small (controller + runner) | ~$15 | 10-20 builds / day |
| Small team | t3.medium (controller + 1 runner) | ~$30 | 40-80 builds / day |
| Mid team | t3.medium controller + 2 m5.large runners | ~$110 | 200-400 builds / day |
| High volume | EKS with autoscaled runner pods | ~$300-500 | 1000+ builds / day |
# Add 10-15 percent for EBS storage and bandwidth. Spot instances cut runner costs 50-70 percent for stateless build workloads.
Operational overhead, honestly accounted
The dollar cost of Drone is small. The operator cost is also small relative to Jenkins, which is the comparison most teams care about. A single-VM Drone setup typically needs 1-2 hours per month of admin time: pulling occasional updates, rotating secrets, restarting the controller after the rare OOM. Compared to a Jenkins setup of comparable scope (4-8 hours per month for plugin upgrades, security patches and config drift), Drone is a meaningful saving on the human side.
The catch is that Drone's ecosystem is small. There is no marketplace of pre-built actions equivalent to GitHub's, and the community plugin set is in the low hundreds rather than the tens of thousands. Pipelines are written as YAML referencing Docker images, which is clean and portable but means you build each capability yourself or via a published Docker image rather than dropping in a one-line action. For teams that want CI infrastructure to be small and uniform, this is a feature. For teams that want CI infrastructure to do everything out of the box, it is a friction.
Backups and disaster recovery are also your problem. Drone's controller stores pipeline state in a database (SQLite by default, Postgres recommended at scale). Losing the database loses the build history, not the pipeline definitions (those live in the repo) but the recoverable state about which builds ran when. Most teams run the controller against an external Postgres for this reason, which adds another $10-20 per month for an RDS instance.
When Drone is the right pick
Small to mid-size teams that want a self-hosted, Docker-native pipeline without the heaviness of Jenkins are Drone's natural audience. The configuration model is YAML referencing Docker images, which fits modern microservice and container-first workflows. The single-binary controller is genuinely easy to operate compared to Jenkins's plugin maze, and the resource footprint is small enough to run alongside other workloads on a shared cluster.
Drone also fits teams with strict data-residency requirements who cannot adopt SaaS CI. Because the entire system runs on your infrastructure, no source code, build artefact or environment variable ever crosses the boundary. The same applies to Jenkins, self-hosted GitLab CI and self-hosted Buildkite agents, so the choice between these is mostly about operator preference and ecosystem fit.
Open-source projects that want to provide CI for contributors without paying for SaaS often run Drone because the project is free, the cost of running it is small enough to absorb in donations, and the GitHub/GitLab/Bitbucket OAuth integration handles the auth without custom user management.
When to pick something else
Teams that need macOS or Windows builds find Drone harder than alternatives. Drone runs Linux Docker pipelines first-class; native macOS or Windows support requires the exec runner on a host of that OS, which is supported but receives less attention than the Docker runner. Teams shipping iOS apps often pair Drone for backend services with Buildkite or Bitrise specifically for mobile.
Teams that want a large ecosystem of pre-built integrations should pick GitHub Actions or GitLab CI. Drone's smaller plugin set means writing or wrapping integrations more often, which is a productivity tax that adds up across hundreds of pipelines.
Teams uncertain about Harness's long-term commitment to the open-source edition might choose Woodpecker CI instead. Woodpecker forked from Drone in 2022 specifically to maintain a community-governed alternative and has stayed close to Drone's design while moving slightly faster on community feature requests. The pricing picture is identical (free, self-hosted) so the choice is mostly about which project's future you prefer to bet on.
Related platforms and comparisons
Frequently Asked Questions
# click any question to expand