GitHub Actions vs Drone CI, and where Drone went

By Kaveh Alemi·Latchkey

GitHub Actions vs Drone CI is no longer only a comparison of two pipeline engines, because github.com/drone/drone now returns a 301 to github.com/harness/harness and Drone survives there as a feature branch whose last commit was 20 April 2026. Before you weigh YAML syntax, read the license: commercial use of the Enterprise Edition is limited to a trial period of 32 consecutive calendar days unless you qualify for one of two waivers.

Drone is a continuous delivery system built on container technology that uses a simple YAML build file to define and execute build pipelines inside Docker containers. That description is from the project's own readme, and it is still an accurate description of what the software does.

What changed is where it lives. Harness Open Source now occupies the repository, and its readme has a section headed "Where is Drone?" that says Harness Open Source represents a massive investment in the next generation of Drone, that a snapshot of Drone was taken as a feature branch so it can continue development, and that the goal is for Harness to eventually be at full parity with Drone in terms of pipeline capabilities, while expecting this to take some time.

The facts below were read from the redirect itself, from the readme and LICENSE on that drone branch, and from the drone-runners organization on 21 September 2026. They are checkable in a browser in under two minutes, and they matter more to this decision than any syntax difference.

GitHub Actions against Drone CI, as things stand (read 21 September 2026)

The license, which is the part most comparisons skip

The LICENSE file on the drone branch splits the project in two. The Community Edition is licensed under the Apache License, Version 2.0, and the source files carry headers saying which license each is under. The Enterprise Edition is under the Drone Non-Commercial License, and its first rule is the one to read: you must limit use of this software in any manner primarily intended for or directed toward commercial advantage or private monetary compensation to a trial period of 32 consecutive calendar days.

Two waivers follow, and most small teams land inside one of them. The individual and small business waiver applies to companies with worldwide annual gross revenue under $5 million US dollars and less than $5 million in all-time aggregate debt and equity financing, counting subsidiaries and affiliates as one. The low usage waiver applies to companies that executed fewer than 5,000 total pipelines with the software in the preceding year. The file also says the contributor will not revoke these waivers but may change terms for future versions.

None of that makes Drone a bad choice. It does make "Drone is free and open source" an incomplete sentence, and it is the sentence the previous version of this page shipped. If your company clears either threshold and you are running the Enterprise Edition, the 32-day clause is a procurement conversation rather than a footnote.

What the redirect actually tells you

A 301 is not an obituary. Harness has been explicit that the drone branch exists so Drone can continue development, and the runner repositories under the drone-runners organization are not all frozen: drone-runner-aws was pushed within the last week, and drone-runner-docker within the year. Four other runners are archived, which is a normal amount of pruning for a project this old.

What the dates do say is where the effort is going. The drone branch's most recent commit and the most recent Drone release are both 20 April 2026, five months before this page was written, while the main branch carrying Harness Open Source is pushed daily. Harness's own framing is that Harness will eventually reach parity with Drone so users can migrate, and that this is expected to take some time.

For a team choosing today, that is the signal that matters. Adopting Drone now means adopting software whose stewards have published their intention to replace it, on a timeline they have not committed to.

Speed

Not benchmarked yet. Both run your build in a container, so the honest expectation is that the wall clock is set by the machine and the cache rather than by the engine, and a benchmark comparing our Drone host to GitHub's fleet would measure our hardware.

The one mechanical difference worth knowing is the pickup path. A Drone runner is a daemon that polls the server for pending pipelines, so there is a poll interval between a webhook arriving and a runner taking the work. GitHub dispatches a job to a matching runner. On a busy server neither is the bottleneck; on an idle one the polling model adds a small floor that dispatch does not.

Cost: free software, two long-lived processes

The Community Edition costs nothing to license, and the bill is a server plus runner hosts, both running between pipelines. That is genuinely cheap at high utilization and genuinely expensive at low utilization, which is the same trade every self-hosted CI system offers.

On the other side the arithmetic is published. Ten thousand Linux minutes a month is $60 at GitHub's $0.006 rate for a 2 vCPU runner, $42 on a Team plan once the 3,000 included minutes are applied, and $25 at $0.0025 a minute on a managed runner at the same size. Against that, a small always-on server and one runner host is often the more expensive option once somebody's time is counted, and it carries a licensing question that metered minutes do not.

Why there is no recorded run on this page

Standing up a Drone server and a runner to record a build would be commercial use of the software by a company selling CI, which is exactly the activity the Non-Commercial License rule limits to 32 days. Rather than reason about which edition and which waiver our own reproduction would fall under, we read the license, the readme and the commit dates instead. Those are the facts the page rests on, and every one of them is a file you can open yourself.

When each one is right

• Drone when you already run it, it works, and nothing on this page describes your situation: the software did not stop working when the repository moved.
• Drone when your code is not on GitHub. Actions is coupled to GitHub repositories, and Drone is not.
• GitHub Actions for a new project on GitHub, because the alternative is adopting software whose stewards have announced a successor.
• Harness Open Source, or something else entirely, if you are migrating off Drone. Moving to the drone branch of a repository that redirects is not a destination.
• Neither, if the real problem is cost. A self-hosted CI server is the expensive answer to expensive minutes unless it runs hot all day. Changing the runner under an existing Actions workflow is one line and no license review.

The verdict

Drone was a good design and the parts of it that were good are still there: container-native steps, a small YAML file, a server and a runner you can understand in an afternoon. But a comparison has to report the state of the thing, and the state is that the canonical URL redirects to a different product, the last release and the last commit on the Drone branch are both 20 April 2026, the stewards have published their intention to reach parity and migrate users away, and the Enterprise Edition carries a 32-day commercial use limit with revenue and financing thresholds attached. If you run Drone today, none of that breaks anything this week. If you are choosing today, choose something whose roadmap is not a plan to replace it.

Frequently asked questions

Related guides

References

• harness/harness, the repository drone/drone now redirects to, and its Drone branch
• The LICENSE file on the Drone branch, including the Non-Commercial terms and waivers
• The drone-runners organization, where the published runners live
• GitHub Actions runner pricing, read for the per-minute rates quoted here
• GitHub Actions documentation