Install Coolify on a VPS — Your Own Heroku in One Command
Watch on YouTube ↗ — if the player asks you to sign in, YouTube is flagging your network; the video itself is public and plays on YouTube directly.
On this page
Coolify is a self-hosted platform-as-a-service: think Heroku or Vercel, but running on your own server. Point it at a Git repo, a Dockerfile, or a Docker Compose file, and it builds, deploys, and wires up HTTPS — no per-app platform fees, ever.
In this guide we install Coolify v4.7.6 on a fresh Ubuntu 24.04 server with the official one-line installer, create the admin account, deploy a first application from a three-line Dockerfile, attach a custom domain, and finish with a valid Let's Encrypt certificate. Everything below was tested end to end on 2026-11-21.
What you need
- A fresh Ubuntu server (24.04 LTS used here) with root or sudo access. Our test machine ran 2 cores and 4 GB of RAM; Coolify itself is light, your apps decide the real sizing.
- A domain with two DNS records pointing at the server: one for the Coolify panel (we used
coolify.deploysaga.com) and one for your app (we usedapp.deploysaga.com).
If you need a server, InterServer runs about $3 a month for the first slice, and it is what this machine class is comparable to (affiliate link — it helps keep these guides free). Any other VPS with a public IP works exactly the same way; Coolify itself is free and open source either way.
Step 1 — Run the one-line installer
SSH into the server and run the official installer:
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bashThat is the entire install. The script sets up Docker if it is missing (ours was already present and was reused), pulls the Coolify images, and starts the stack: the Coolify app, its PostgreSQL database, Redis, and a Traefik reverse proxy that will handle your domains and certificates. On our machine the whole run took about two minutes.
Verify everything is up:
sudo docker psYou should see coolify, coolify-db, coolify-redis, and coolify-proxy containers, all healthy.
Step 2 — Create the admin account (within 10 minutes)
Open the panel at http://coolify.deploysaga.com:8000 (your panel domain, port 8000). The first visit lands on the registration form — create the root account right away. Coolify only allows the first account to be created within about 10 minutes of the server starting. If the window closes, restart the app container to reopen it:
sudo docker restart coolifyAfter registering, the onboarding wizard walks through three short steps:
- Welcome — click Continue.
- Server type — choose This machine (localhost). Coolify validates the server and its own SSH connection automatically.
- Project setup — click Create "My First Project".
You land on "Setup complete" with three green checks: server, project, and Docker engine.
Step 3 — Deploy your first app from a Dockerfile
Click Deploy Your First Resource and choose Dockerfile. Paste this three-line Dockerfile into the editor — it builds a tiny nginx image with a static page baked in:
FROM nginx:alpine
RUN printf '<!doctype html><title>Hello from Coolify</title><h1>Deployed with Coolify</h1><p>DeploySaga demo app.</p>' > /usr/share/nginx/html/index.html
EXPOSE 80Click Create Application. On the app's General page, rename it to something friendly (we used hello-app) and press Save changes in the bar that appears at the bottom — the rename only takes effect once you save.
Now click Deploy. Coolify builds the image with BuildKit and does a rolling update into the Traefik proxy. Our deploy finished in under a minute, and the app status turned to Running.
At this point the app is already reachable on its generated sslip.io address. Next we give it a real domain.
Step 4 — Attach a custom domain
Open the app's Domains page and click Add Domain:
- Protocol:
https - Domain:
app.deploysaga.com - Port:
80— change this from the default 3000; it must match the port your container actually serves (nginx listens on 80) - Path: leave empty
Save, then click Redeploy so the proxy picks up the new route. Coolify also adds the www. variant of the domain automatically; it is harmless if you never point DNS for it anywhere.
Step 5 — HTTPS
On a normal public VPS, you are already done. Traefik requests a Let's Encrypt certificate automatically over the HTTP challenge as soon as your domain resolves to a public IP, and redirects HTTP to HTTPS for you.
Our test server sits on a private network address, and Let's Encrypt cannot validate that with the HTTP challenge — the proxy falls back to its self-signed default certificate. If you are in the same situation (home lab, internal network), issue the certificate once through the DNS challenge instead and hand it to the proxy as a file:
sudo certbot certonly --manual --preferred-challenges dns \
-d app.deploysaga.com --agree-tos -m admin@deploysaga.comCertbot shows you a TXT record to create under _acme-challenge.app in your DNS; create it, wait a few seconds, and press Enter to finish. Then install the certificate into Traefik's file provider:
sudo mkdir -p /data/coolify/proxy/certs
sudo cp /etc/letsencrypt/live/app.deploysaga.com/fullchain.pem /data/coolify/proxy/certs/app.crt
sudo cp /etc/letsencrypt/live/app.deploysaga.com/privkey.pem /data/coolify/proxy/certs/app.key
printf "tls:\n certificates:\n - certFile: /traefik/certs/app.crt\n keyFile: /traefik/certs/app.key\n" \
| sudo tee /data/coolify/proxy/dynamic/deploysaga-certs.yamlTraefik watches that folder and hot-loads the certificate within seconds — no restart. Verify:
curl -s https://app.deploysaga.com<!doctype html><title>Hello from Coolify</title><h1>Deployed with Coolify</h1><p>DeploySaga demo app.</p>The browser shows a valid padlock, issued by Let's Encrypt. Note that a manually issued certificate is not auto-renewed; repeat the certbot command before it expires (90 days), or move the server to a public IP and let Traefik handle everything.
Gotchas worth knowing
- The 10-minute registration window is real. If the first account is not created in time, the form locks;
docker restart coolifyreopens it. - The port field defaults to 3000. If your app serves a different port, the domain will route to nothing until you fix it — this is the most common "my domain 503s" cause.
- The generated sslip.io domain always stays alongside your custom domains. It is a handy fallback for checking whether the app itself is up when DNS is in doubt.
- Back up
/data/coolify/source/.envafter install; it holds the secrets Coolify generated for its own database and services.
Where to go next
Coolify's real power is one-click services and Git-driven deploys: connect a repository and every push becomes a rolling deployment with its own domain and certificate. In the next guide in this series we deploy Cal.com — the open-source scheduling platform — onto this same Coolify server.
