DevOps & CI/CD Hosting — Self-host Your Pipelines

Choose your DevOps tool

Five tools to build a complete CI/CD and deployment pipeline on your own infrastructure.

Your pipeline. Your infra.

Git push

CI runner builds

Docker image

Deploy via Coolify

Live

All steps run on your own servers. No cloud provider bills, no minutes cap.

Docker & Portainer

Container management

From €3.90/mo

Docker lets you run any application in isolated containers on your own server. Portainer CE adds a web UI for managing containers, stacks, volumes, and networks — no command line required for day-to-day operations.

Cloud VPS Dedicated

Our Docker & Portainer recommendations

GitHub Actions runners

Self-hosted CI/CD

From €19.00/mo

Self-hosted GitHub Actions runners let your existing workflows run on your own server. Same workflow YAML, no changes needed. Builds run on dedicated NVMe with warm caches, no cold starts, no queue waiting.

VPS Dedicated

Our GitHub Actions runners recommendations

GitLab CI runners

Self-hosted CI/CD

From €19.00/mo

Self-hosted GitLab CI runners work with GitLab.com or your self-hosted GitLab instance. No quota limits, no per-minute billing, full access to your private network. Docker executor provides isolated builds per job.

VPS Dedicated

Our GitLab CI runners recommendations

Jenkins

Automation server

From €19.00/mo

Jenkins is the original open-source automation server. 1,800+ plugins, pipelines-as-code (Jenkinsfile), distributed builds across multiple agents, and 20+ years of enterprise production use. Java-based — plan for 4+ GB RAM.

VPS Dedicated

Our Jenkins recommendations

Want to run something else?

Linux · Docker · Any stack

Any DevOps tool that runs on Linux runs on a Dedimax server. Gitea, Drone CI, Tekton, ArgoCD, Ansible Tower, Nexus — full root access, Docker ready, no restrictions.

Browse all servers →

Why self-host your CI/CD?

No per-minute billing

Self-hosted CI runners run unlimited builds for one flat monthly server cost. No per-job charges, no usage quotas, no surprise bills at the end of the month.

Faster builds

Dedicated NVMe storage, warm dependency cache, no cold start, no queue waiting during peak hours. Docker layers, npm packages, and test dependencies persist across builds for consistently fast jobs.

No vendor lock-in

GitHub Actions YAML works on self-hosted runners unchanged. GitLab CI pipelines work on your own runner unchanged. Your pipeline logic is yours — switching providers does not require rewriting CI configuration.

Private network access

Self-hosted runners run on your infrastructure and can reach private databases, staging servers, and internal APIs — things that are impossible to access from cloud-hosted runners.

Frequently asked questions

Should I use Coolify or Docker/Portainer?

Coolify is the right choice if you want a git-push-to-deploy experience — auto SSL, preview deployments, database provisioning, all from a web UI. Docker/Portainer is the right choice if you want lower-level container management — deploy any Docker image, manage stacks manually, full control over networking. Many teams use both: Portainer for server management, Coolify on top for app deployments.

What are the server specs recommended for CI runners?

For a single runner handling sequential jobs: 4 cores, 8 GB RAM, 60 GB NVMe. For 2-3 parallel runners: 6 cores, 16 GB RAM, 100 GB NVMe. For heavy CI with matrix builds or large Docker images: 8+ cores, 32 GB RAM, 200 GB NVMe on a dedicated server.

Can I run the CI runner and the app on the same server?

Yes, for small teams. A single VPS can run Coolify (for deployments) and a GitHub Actions or GitLab CI runner simultaneously. Separate them once builds become resource-intensive — heavy Docker builds compete with running applications for CPU and memory.

Do I need a dedicated server or is a VPS enough?

A VPS handles most teams. 4-6 cores and 8-16 GB RAM covers Coolify with 5-10 apps, or 2-3 parallel CI runners. Move to a dedicated server when you need 4+ parallel runners, large Docker builds, or Coolify hosting 20+ services.

How do I handle SSL certificates?

Coolify handles SSL automatically — it provisions Let's Encrypt certificates for every deployed app with no manual steps. For Docker-only setups, use Nginx Proxy Manager or Traefik as a reverse proxy — both handle Let's Encrypt automation. Jenkins does not handle SSL directly; put it behind a reverse proxy.

Can I use GitHub Actions with a self-hosted runner AND GitLab CI?

Yes. Both runners can run on the same server. Register a GitHub Actions runner for your GitHub repos and a GitLab CI runner for your GitLab repos. They operate independently and share the server's CPU and RAM. For heavy parallel workloads, give each its own server.

DevOps & CI/CD on your own servers Ship faster. No per-minute billing. No vendor lock-in.