Development
Self-host Drone CI on a VPS
A container-native CI/CD system.
Run pipelines defined in YAML, executing each step in a container, on your own infrastructure and tied to your Git forge.
Why self-host Drone CI?
Drone is a compact CI engine that pairs well with Gitea/Forgejo and keeps your build secrets inside your network.
How to install Drone CI
- 1
Provision a VPS
Pick a Debian/Ubuntu template and get root SSH in about a minute.
- 2
Install the runtime
Install Docker + Drone server and runner.
- 3
Deploy the application
Net what you need from the project’s official source and run it.
- 4
Put it behind TLS
Reverse-proxy with Nginx and issue a Let’s Encrypt certificate.
- 5
Add it to your backups
Include the data directory and database in your backup routine before you rely on it.
Practical tips
- Give Drone CI its own database user with rights only on its own schema.
- Reverse-proxy Drone CI and terminate TLS at the proxy so certificates are managed in one place.
- Take a VPS snapshot before major upgrades so you can roll back cleanly.
- Keep Drone CI patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does Drone CI need?
- Plan on 2–4 GB for typical use; add headroom if you expect many concurrent users.
- What stack does Drone CI run on?
- Docker + Drone server and runner.
- Can I run other things on the same VPS?
- Yes — size the plan so Drone CI plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include Woodpecker CI, Gitea Actions, GitLab CI — browse all app guides.