How much RAM does Woodpecker CI need?

Plan on 2 GB for typical use; add headroom if you expect many concurrent users.

What stack does Woodpecker CI run on?

Docker + Woodpecker server/agent.

Yes — size the plan so Woodpecker CI plus your other workloads fit in RAM with room to spare.

Development

A lightweight, community-driven CI/CD engine.

A simple container-based CI with a clean UI, built to integrate with Gitea, Forgejo and GitHub and run on modest hardware.

Woodpecker is one of the easiest CI systems to self-host alongside a small Git forge, without GitLab’s footprint.

1
Provision a VPS
Pick a Debian/Ubuntu template and get root SSH in about a minute.
2
Install the runtime
Install Docker + Woodpecker server/agent.
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.

Give Woodpecker CI its own database user with rights only on its own schema.
Reverse-proxy Woodpecker 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 Woodpecker CI patched — most self-hosting incidents are unpatched software.

How much RAM does Woodpecker CI need?: Plan on 2 GB for typical use; add headroom if you expect many concurrent users.
What stack does Woodpecker CI run on?: Docker + Woodpecker server/agent.
Can I run other things on the same VPS?: Yes — size the plan so Woodpecker CI plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include Drone CI, Gitea Actions, Jenkins — browse all app guides.