How to Install Coolify on Hostinger VPS (2026)

Coolify is a free, open-source, self-hosted alternative to platforms like Heroku and Vercel: you get Git-push deployments, automatic SSL, and database management on your own server. Installing it on a Hostinger VPS takes one command — curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash — and about five minutes.

This guide covers the requirements, the install steps, securing the dashboard, and deploying your first application. One important caveat up front: Coolify wants a fresh server. If your VPS already runs Docker Manager projects or other services, install Coolify on a separate VPS to avoid port and reverse-proxy conflicts.

Prerequisites

A Hostinger VPS with a clean Ubuntu 22.04 or 24.04 install (Debian 11/12 also works). No existing Docker apps, web servers, or panels on it.
Minimum: 2 vCPU, 2 GB RAM, 30 GB free disk. Recommended: 4 GB RAM or more, especially if you will build apps and run databases on the same server.
Root SSH access (or a sudo user). Hostinger gives you root credentials for the VPS at provisioning.
Ports 80, 443, and 8000 reachable. Port 8000 is where the Coolify dashboard lives during setup.

A Hostinger KVM 2 plan comfortably covers the recommended specs for Coolify plus a handful of small apps and databases. Check current VPS pricing before you provision.

Step 1 – Connect and update the server

Connect to your VPS via SSH:
```
ssh root@YOUR-VPS-IP
```
(You can also use the browser terminal in the VPS dashboard, though a local terminal is more comfortable for a longer session.)

Update packages and make sure curl is present:

apt update && apt upgrade -y
apt install curl -y

Step 2 – Run the Coolify installer

Execute the official installation script:

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

Wait. The script installs Docker, pulls Coolify’s own containers, configures a Traefik reverse proxy and the firewall. Expect roughly 3–10 minutes depending on the server.
When it finishes, it prints your dashboard URL, typically http://YOUR-VPS-IP:8000. Copy it.

Note: if your provider’s Ubuntu image ships Docker installed via snap, Coolify does not support that — remove the snap Docker first and let the installer set up Docker properly.

Step 3 – Create your admin account immediately

Open http://YOUR-VPS-IP:8000 in your browser.
Register the first administrator account right away. Until an admin account exists, anyone who reaches that URL first can claim your instance — this is the single most time-sensitive step of the whole install. Do not leave the tab sitting open unattended.
Use a strong, unique password and store it in a password manager.

Step 4 – Complete the initial setup

After login, Coolify walks you through a short onboarding:

Choose your server: for a single-VPS setup, select Localhost (deploy on this same server) and validate it. You can add more servers later over SSH.
Connect a Git provider: link GitHub, GitLab, or Bitbucket via OAuth app or deploy key so Coolify can pull your code and listen for push webhooks.
Point a domain (recommended): create an A record pointing your domain (or a subdomain like coolify.yourdomain.com) at the VPS IP, then assign it to the dashboard so you stop using the raw IP:port URL. Coolify provisions a free Let’s Encrypt certificate automatically.

Step 5 – Deploy your first application

In the dashboard, create a Project, then Add Resource → Application.
Pick your connected Git provider and choose the repository.
Coolify usually auto-detects the framework and picks a build pack (Dockerfile or Nixpacks). Adjust the port if your app does not listen on the default.
Paste your environment variables (the contents of your .env file) into the environment section.
Hit Deploy. Coolify pulls the code, builds the image, and starts the container — then shows you build and runtime logs live.
Assign your domain to the app for automatic HTTPS, or use the generated preview URL for testing.

From here, every git push to your deploy branch triggers a new deployment automatically — the core “Vercel-like” workflow, minus the per-seat bill.

Security hardening checklist

Coolify becomes the control plane for everything on the box, so the box underneath deserves proper lockdown:

Key-only SSH: disable SSH password login on the VPS (PasswordAuthentication no in sshd_config) and use SSH keys.
Keep Coolify updated: security fixes ship regularly — leave the auto-update mechanism on unless you have a documented reason to pin a version.
Firewall: expose only 80, 443, 22 (SSH), and 8000 during setup; close 8000 or restrict it once the dashboard is on a domain with HTTPS.
Backups: Coolify can back up databases, but also take regular VPS snapshots from the Hostinger dashboard — see our backup and restore guide.
Separate concerns: run Coolify on its own VPS rather than alongside Docker Manager catalog apps or manual Docker projects.

Troubleshooting

Installer hangs or fails partway. Confirm the server meets the minimum specs (2 GB RAM will OOM during builds on smaller plans) and that you started from a clean OS. Re-running the script on a half-installed system often works, but a fresh OS reinstall is cleaner.

Dashboard URL does not load. Check that port 8000 is open in the VPS firewall and that nothing else is bound to it. Also confirm you are using http://, not https://, for the initial IP-based URL.

Builds fail with out-of-memory errors. You are building and running on the same small server. Enable swap as a stopgap, but plan to upgrade RAM — builds are the hungriest part of the workflow.

Domain shows the app but without HTTPS. DNS must fully propagate before Let’s Encrypt can validate. Wait, then re-trigger certificate issuance from the app’s domain settings.

Git webhooks do not trigger deploys. Re-check the Git provider connection and confirm the webhook URL is reachable from the internet (not blocked by firewall rules).

FAQ

Is Coolify really free?

Yes, the self-hosted version is free and open source — you only pay for the VPS underneath it. Coolify also offers a hosted cloud version, but self-hosting on your own VPS is the cost-effective route this guide covers.

Can I install Coolify on shared hosting?

No. Coolify needs root access, Docker, and control over system ports, so it requires a VPS (or dedicated server). Shared hosting cannot run it.

Coolify vs Hostinger’s Docker Manager — which should I use?

Use Docker Manager for simple container deployments from Hostinger’s catalog with minimal setup. Use Coolify when you want Git-push deployments, preview environments, and a Heroku-style workflow for your own code. They solve different problems — see our Docker Manager guide for the panel route.

How much RAM does Coolify need?

Coolify itself runs comfortably on 2 GB, but builds need headroom — 4 GB or more is the practical recommendation if you build apps and run databases on the same server. Monitor usage and upgrade the VPS plan before the server starts swapping heavily.