Self-Host Coolify: Open Source Vercel Alternative 2026
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).
Full comparison of self-hosted PaaS options at OSSAlt.
Related: Coolify vs Dokploy vs CapRover · Self-Host Dokploy