Self-Host Coolify: Open Source Vercel Alternative 2026

TL;DR

Coolify is the leading self-hosted PaaS — an open-source alternative to Vercel, Heroku, and Netlify with 50,000+ GitHub stars. It gives you push-to-deploy workflows, automatic HTTPS, 280+ one-click service templates, database management, and preview deployments on servers you own. The one-line installer gets you running in under 5 minutes. At scale, self-hosting Coolify on a $6/month VPS is 85–95% cheaper than equivalent Vercel Pro/Enterprise bills.

Key Takeaways

Coolify v4: ~50K GitHub stars, Apache 2.0 license, actively maintained by coolabs.io
One-line install: curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
280+ one-click templates: databases, monitoring stacks, CMS platforms, AI tools
Multi-server support: manage deployments across multiple VPS instances from one dashboard
Git integration: GitHub, GitLab, Bitbucket — push to deploy with automatic SSL
Nixpacks support: auto-detects your framework and builds without a Dockerfile
Vercel comparison: a $5/month Hetzner VPS running Coolify handles what would cost $50–200/month on Vercel at production scale
Requirements: 2GB RAM, 1 vCPU minimum (2GB RAM, 2 vCPU recommended)

Why Switch From Vercel to Coolify?

Vercel is excellent for getting started. It's less excellent when your bill arrives.

Vercel pricing reality (2026):
  Hobby: Free (personal projects only)
  Pro: $20/month + usage

  Usage charges on Pro:
    Bandwidth: $0.15/GB over 1TB
    Edge Function executions: $2/million over 500K
    Function GB-hours: $18/GB-hr over 1,000
    Image optimization: $5/1000 images over 5,000

Real Pro bills at moderate scale:
  10-person startup with active traffic: $80-300/month
  Mid-size app (50K MAU): $200-600/month

Coolify equivalent:
  Hetzner CX22 (2 vCPU, 4GB RAM): €3.79/month (~$4/month)
  Hetzner CX32 (4 vCPU, 8GB RAM): €7.49/month (~$8/month)
  Hetzner CCX23 (4 dedicated vCPU, 8GB): €15.59/month (~$17/month)

The math only works if you're comfortable managing a Linux server. Coolify abstracts most of that — but it's still infrastructure you're responsible for.

What Coolify Includes

Feature	Coolify	Vercel	Netlify
Push-to-deploy	✅	✅	✅
Auto SSL (Let's Encrypt)	✅	✅	✅
Preview deployments	✅	✅	✅
Database management	✅	❌	❌
One-click services	✅ 280+	❌	❌
Multi-server	✅	❌	❌
Docker Compose deploy	✅	❌	❌
Nixpacks	✅	✅	❌
GitHub Actions	✅	✅	✅
Edge functions	❌	✅	✅
Global CDN	❌ (need Cloudflare)	✅	✅
Analytics	Basic	✅	✅
Cost	VPS only	$20+/mo	$19+/mo

The major Coolify gaps: no global CDN (add Cloudflare free tier) and no edge functions (use Workers or Deno Deploy for that use case). Everything else is covered.

Installation

One-Line Install (Recommended)

# Run on a fresh Ubuntu 22.04 / Debian 12 server
# Requires root or sudo
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash

The script installs Docker, configures the network, and deploys Coolify as a set of containers. Takes 2–3 minutes.

Access the dashboard at http://your-server-ip:8000.

Manual Docker Compose Install

For more control over the deployment:

# Download the official Coolify compose files
mkdir -p /data/coolify/source
curl -fsSL https://cdn.coollabs.io/coolify/docker-compose.yml -o /data/coolify/source/docker-compose.yml
curl -fsSL https://cdn.coollabs.io/coolify/docker-compose.prod.yml -o /data/coolify/source/docker-compose.prod.yml
curl -fsSL https://cdn.coollabs.io/coolify/.env.production -o /data/coolify/source/.env

# Generate required secrets
sed -i "s|APP_ID=.*|APP_ID=$(openssl rand -hex 16)|g" /data/coolify/source/.env
sed -i "s|APP_KEY=.*|APP_KEY=base64:$(openssl rand -base64 32)|g" /data/coolify/source/.env
sed -i "s|DB_PASSWORD=.*|DB_PASSWORD=$(openssl rand -base64 24)|g" /data/coolify/source/.env
sed -i "s|REDIS_PASSWORD=.*|REDIS_PASSWORD=$(openssl rand -base64 24)|g" /data/coolify/source/.env

# Start Coolify
docker compose -f /data/coolify/source/docker-compose.yml \
               -f /data/coolify/source/docker-compose.prod.yml \
               --env-file /data/coolify/source/.env \
               -p coolify up -d --pull always --remove-orphans

Server Requirements

# Verify your server meets minimum requirements
free -h      # Need at least 2GB RAM
nproc        # Need at least 1 vCPU (2+ recommended)
df -h /      # Need at least 30GB disk

# Open required ports (if using UFW)
ufw allow 22    # SSH
ufw allow 80    # HTTP
ufw allow 443   # HTTPS
ufw allow 8000  # Coolify dashboard (close after setting up domain)
ufw enable

Deploying Your First App

Connect a Git Repository

Open dashboard → Sources → Add → select GitHub/GitLab/Bitbucket
Install the Coolify GitHub App on your account/org
Go to Projects → New Project → New Resource → Application
Select your repository and branch

Coolify auto-detects your stack with Nixpacks:

Detected: Next.js 15 application
Build command: npm run build
Start command: npm run start
Port: 3000
Build pack: Nixpacks ✅

Environment Variables

# Set via dashboard UI, or via API:
curl -X POST "https://your-coolify.domain/api/v1/applications/{uuid}/envs" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "key": "DATABASE_URL",
    "value": "postgresql://user:pass@localhost:5432/mydb",
    "is_secret": true
  }'

Deploy a Database (One-Click)

Dashboard → New Resource → Database → PostgreSQL 16

Coolify provisions:
  - PostgreSQL container with persistent volume
  - Automatic backups to S3 (if configured)
  - Internal hostname: postgresql.coolify.internal
  - Generated credentials visible in dashboard
  - pgAdmin UI option

One-Click Service Templates

Coolify's 280+ templates cover common self-hosted services:

AI/LLM:
  - Ollama          - Local LLM inference
  - Open WebUI      - ChatGPT-like UI for Ollama
  - Flowise         - LangChain visual builder
  - n8n             - AI workflow automation

Databases:
  - PostgreSQL, MySQL, MariaDB, MongoDB
  - Redis, KeyDB, DragonFly
  - ClickHouse, CockroachDB

CMS:
  - Ghost, WordPress, Strapi, Directus, Payload

Monitoring:
  - Grafana + Prometheus stack
  - Uptime Kuma
  - Plausible Analytics

Dev Tools:
  - Gitea (GitHub alternative)
  - Drone CI / Woodpecker CI
  - Minio (S3 storage)
  - Vaultwarden (Bitwarden server)

Setting Up a Custom Domain + HTTPS

Coolify handles Let's Encrypt certificates automatically:

1. Point your domain DNS to your server IP:
   Type: A
   Name: app.yourdomain.com
   Value: YOUR_SERVER_IP

2. In Coolify dashboard → Application → Domains:
   Add: app.yourdomain.com

3. Toggle "Enable HTTPS" → Coolify requests Let's Encrypt cert

4. Done — your app is live at https://app.yourdomain.com

For wildcard certificates (multiple subdomains):

# Coolify supports Let's Encrypt wildcard via DNS challenge
# Configure in: Settings → SSL → Wildcard Certificate
# Requires DNS provider API (Cloudflare, etc.)

Adding a CDN with Cloudflare (Free)

Coolify doesn't include a CDN, but Cloudflare's free tier covers it:

1. Add your domain to Cloudflare (free plan)
2. Update nameservers at your registrar to Cloudflare
3. In Cloudflare DNS: point your subdomain to your server IP
4. Enable Cloudflare proxy (orange cloud icon)
5. Cloudflare now caches static assets globally

Result:
  - Global CDN caching for static assets
  - DDoS protection
  - Cloudflare Analytics
  - Cost: $0

Multi-Server Setup

Coolify's multi-server feature lets you deploy services to remote servers from a single dashboard:

Architecture:
  Coolify Server (your management node)
    ├── Server 1 (apps)   — connected via SSH key
    ├── Server 2 (databases) — connected via SSH key
    └── Server 3 (staging) — connected via SSH key

Setup:
  1. Settings → Servers → Add Server
  2. Enter IP, SSH port, and paste your private key
  3. Coolify tests the connection and validates Docker is present
  4. Deploy resources to any connected server from the same dashboard

Migrating from Vercel

# 1. Export your environment variables from Vercel
#    Vercel Dashboard → Project → Settings → Environment Variables → Download

# 2. Identify your build/start commands from vercel.json or package.json

# 3. In Coolify: create new application from your repo
#    - Set same environment variables
#    - Set same build/start commands

# 4. Add your custom domain to Coolify
#    - Update DNS to point to Coolify server

# 5. Verify deployment, then remove from Vercel

The main migration consideration: if your app uses Vercel Edge Functions, Vercel KV, Vercel Blob, or Vercel Postgres — those are Vercel-specific services you'll need to replace with self-hosted or third-party equivalents (Upstash, Cloudflare KV, MinIO, PostgreSQL).

Why Self-Host Coolify?

The case for self-hosting Coolify comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Coolify means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Coolify, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Coolify headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Coolify data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Coolify without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Coolify's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Coolify backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Coolify's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Coolify's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Coolify's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Coolify's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f coolify

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Coolify's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats coolify. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Coolify Updated

Coolify follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Coolify is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

Full comparison of self-hosted PaaS options at OSSAlt.

See open source alternatives to Coolify on OSSAlt.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)