CI pipelines
build, test, lint, package on every commit

// screenshot of drone.io ↗
Drone is a container-native CI/CD platform — pipelines defined in YAML, executed as Docker containers, integrated with Git providers (GitHub, GitLab, Gitea, Bitbucket). The OSS edition is Apache 2.0 licensed and production-capable.
Drone is a container-native CI/CD platform — pipelines defined in YAML, executed as Docker containers, integrated with Git providers (GitHub, GitLab, Gitea, Bitbucket). The OSS edition is Apache 2.0 licensed and production-capable.
For teams who want GitHub Actions / GitLab CI experience without committing to a single vendor's ecosystem.
Concrete scenarios where teams pick Drone CI over the SaaS alternative.
build, test, lint, package on every commit
deploy to staging/production on branch / tag
any language with a Docker image works
same model, your infrastructure
any container as a pipeline step
If your team profile matches one of these, Drone CI is a strong fit out of the box.
building self-hosted CI/CD pipelines
with multi-repo monorepos or polyrepo strategies
keeping CI in-network for proprietary code
moving away from per-minute GitHub Actions billing
preferring container-native CI design
When evaluating self-hosted options for this category, here are the dimensions on which Drone CI consistently lands above the alternatives.
The stack you'll plug Drone CI into — services, protocols, and adjacent apps in the BluixApps catalog.
drone/drone:2 (release-tagged)Operational guidance from running this in production — what to do before you scale, what to lock down, what surprises people.
8000:80 · drone/drone:2