Self-host Coolify on a no-KYC VPS
Coolify is an open-source alternative to Vercel, Heroku and Netlify that you run on your own server. It builds from git, runs everything as Docker containers and handles HTTPS. No email is needed to sign up, and you can pay in crypto, by card or with cash in the mail.
- Apache 2.0
- Builds from git
- Automatic Let's Encrypt
- Full root
- No KYC
What Coolify replaces
Vercel, Netlify and Render
Push to git and it builds and deploys, with build logs, custom domains, HTTPS and a preview deployment per pull request. There are no build minutes to count.
Heroku
Nixpacks detects the language and the framework (Next.js, Laravel and the like) and builds without a Dockerfile: Node, Python, Ruby, Go, Rust, PHP, Elixir, Java, .NET and more. Railpack, its successor, is there as a beta option. Static sites have their own build pack. Bring a Dockerfile or a Compose file when you want control.
Hosted databases
Coolify covers what most projects use Supabase, PlanetScale or Upstash for: Postgres, MySQL, MariaDB, MongoDB, ClickHouse, Redis, KeyDB and Dragonfly in a few clicks, plus SQLite as an experimental option. All of them except the three Redis-type engines can take scheduled backups to S3-compatible, SFTP, FTPS or WebDAV storage.
CapRover and Dokku
The same push-and-deploy model. Dokku's web interface, Dokku Pro, is a paid add-on. Coolify comes with one, plus several servers under one dashboard and a catalog of one-click services.
A way out
Apps run as ordinary Docker containers with ordinary volumes. If you stop using Coolify, the containers and the data are still there.
More than one server
Add servers over SSH and choose where each app runs. Coolify deploys to all of them from one dashboard.
From a blank server to a first deploy
Signup is a generated credential. There is no email, phone or ID step.
Deploy a server
Blackbox Core or larger, with Ubuntu 24 or Debian 12. Add your SSH key when you order.
Run the installer
One script installs Docker and Coolify. It takes a few minutes and prints the dashboard address when it is done.
Register the admin at once
The first person to open port 8000 becomes the admin. Create your account before anyone else finds the page. Coolify only takes that first account in the 10 minutes after it starts.
Give the dashboard a domain
Point a DNS record at the server and set it as the instance domain. The proxy gets the certificate.
Connect git and push
Add the GitHub App or a deploy key, pick a repository and a build pack, and deploy.
The install
Run as root on a fresh server. The script installs Docker if it is missing.
# Official installer: Docker, Coolify, its database and its proxy
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash
# Then open the dashboard and register the admin straight away:
# http://SERVER_IP:8000
# The first account is accepted for 10 minutes after Coolify starts.
# If the page says the setup window closed: docker restart coolify
# Back up the APP_KEY line now, somewhere off this server:
grep '^APP_KEY=' /data/coolify/source/.env
# Coolify manages this server over SSH as root, with a key it generates.
# Root key logins must stay allowed (prohibit-password or yes, never no):
sshd -T | grep -i permitrootlogin
# Ports it uses: 22, 80, 443, plus 8000 (dashboard),
# 6001 (realtime updates) and 6002 (web terminal).
# Once the dashboard has its own domain, 8000, 6001 and 6002 can be closed.Before you put real apps on it
The open registration page
Until the first account exists, anyone who reaches port 8000 can register as the admin and control the server. Create yours as soon as the installer finishes.
Root SSH to itself
By default Coolify reaches even its own host over SSH as root. Setting PermitRootLogin to no breaks it; prohibit-password keeps key logins and still blocks passwords. A non-root user is possible but still experimental, and it needs passwordless sudo anyway.
Docker and ufw
Docker writes its own iptables rules, so a port a container publishes stays open even when ufw denies it. Test from another machine before you trust a firewall rule.
Builds next to live apps
Coolify builds on the server that runs the app unless you add a separate build server. A large build then competes with your live apps for memory.
Backing up Coolify itself
Database backups cover your apps' databases. Coolify's own projects and settings are in its own database, which Settings > Backup dumps on a schedule. The APP_KEY in /data/coolify/source/.env encrypts every secret it stores and is not in that backup. Keep a copy of both somewhere else.
Reboots with disk encryption on
With full-disk encryption on Blackbox, every reboot stops at an SSH prompt for your passphrase. The dashboard and every app it deployed stay down until you type it.
Plans for Coolify
Coolify's own containers (the dashboard with its realtime server, a Postgres database, Redis and the proxy) take a share of memory before any app runs. Builds take the most: a Node or Rust build can use several gigabytes while it runs.
| Plan | vCPU | RAM | NVMe | Traffic | Where | Price |
|---|---|---|---|---|---|---|
| Blackbox Core | 2 | 4 GB | 50 GB | 4 TB per 31 days | MontrealAmsterdamNew York City (launch pre-order)Singapore (launch pre-order) | $9.99/mo |
| Blackbox Plus | 4 | 8 GB | 100 GB | 8 TB per 31 days | MontrealAmsterdamNew York City (launch pre-order)Singapore (launch pre-order) | $19.99/mo |
| Blackbox Max | 6 | 16 GB | 200 GB | 16 TB per 31 days | MontrealAmsterdamNew York City (launch pre-order)Singapore (launch pre-order) | $39.99/mo |
| Blackbox Ultra | 8 | 32 GB | 400 GB | 32 TB per 31 days | MontrealAmsterdamNew York City (launch pre-order)Singapore (launch pre-order) | $79.99/mo |
Core runs Coolify and a few small apps. Plus is the comfortable size when you build on the same server. Max and Ultra suit a long list of services or several databases. You can move up a tier later and pay the difference for the days left; disks grow but never shrink, so there is no downgrade.
Blackbox or a standard VPS
Coolify runs the same on both. They differ in what the host can see, how traffic is counted and where you can deploy today.
| Blackbox | Standard VPS | |
|---|---|---|
| Memory | Encrypted by the CPU (AMD SEV-SNP) | Not encrypted |
| Disk encryption | Optional, with a passphrase only you hold | Not built in |
| Smallest plan | Core: 2 vCPU, 4 GB RAM, 50 GB NVMe | 4 GB RAM, 40 GB NVMe (VPS-100 or VDS-100, depending on the city) |
| Traffic | 4 to 32 TB per 31 days, then 10 Mbps | Unmetered |
| IPv6 | Routed /64 | None |
| Cities today | Montreal and Amsterdam; pre-order in New York City and Singapore | New York City, Singapore and Hong Kong |
Pick standard if your apps serve large downloads or video and you want unmetered bandwidth, or if you need a city Blackbox does not run in yet. The VDS plans on that line run at a higher clock, which shortens builds. Standard terms under 31 days cost 10% more.
Questions
How big a server does Coolify need?
Coolify asks for at least 2 CPU cores, 2 GB of RAM and 10 GB of disk for itself. Our smallest plan, Blackbox Core, has 2 vCPU and 4 GB, which leaves room for a few small apps and a database. Builds use the most memory, so if you build on the same server on every push, Blackbox Plus with 8 GB is more comfortable. A bigger fleet can spread over several servers run from one dashboard.
Does Coolify renew TLS certificates?
Yes. Its proxy (Traefik by default, Caddy if you switch) requests and renews a Let's Encrypt certificate for every domain you attach to a resource. The DNS record has to point at the server first.
Can I deploy from a private repository?
Yes. Install the GitHub App, or connect a GitLab or Gitea/Forgejo app, or add a deploy key for Bitbucket or any git server reachable over SSH. Pushes trigger deploys through webhooks.
How do backups work?
Coolify dumps Postgres, MySQL, MariaDB, MongoDB, ClickHouse and SQLite databases on a schedule and can send the dumps to S3-compatible, SFTP, FTPS or WebDAV storage. Redis-type databases and files in your apps' volumes are not part of those dumps. Coolify backs up its own database (projects, settings, deployment history) from Settings > Backup. That backup leaves out the APP_KEY in /data/coolify/source/.env, which encrypts the credentials and keys Coolify stores, so save that line somewhere else too. We don't sell a snapshot product, so keep backups off the server.
Will a Coolify upgrade break my apps?
An upgrade replaces Coolify's own containers and does not touch the apps, databases and services it manages. A deployment that runs during the upgrade can fail, so wait until none is running. You can turn off automatic updates in the settings and upgrade by hand after reading the release notes.
Can Coolify create preview deployments for pull requests?
Yes. With the GitHub App, or a repository webhook on GitLab, Gitea or Bitbucket, Coolify builds each pull request into its own container on its own URL and removes it when the pull request is merged or closed. Point a wildcard DNS record at the server for the preview URLs.
Is Coolify open source?
Yes, under the Apache 2.0 license, and self-hosting it is free. Coolify Cloud is a paid, hosted copy of the dashboard that manages servers you bring yourself.
Does Servury log my Coolify traffic?
No. We don't keep traffic logs, so the requests your apps serve and the images Coolify pulls are not recorded on our side. There is no guest agent on Blackbox, so nothing of ours runs inside the server. Like any network, ours sees your addresses, how much data moves and whether the machine is on. Coolify's logs and your apps' logs stay on your disk.
Guides on this topic
- Why Developers Are Self-Hosting AI Agents and LLMs Instead of Relying on Cloud AI PlatformsWhy developers are moving language models and agents onto their own VPS, keeping prompts, documents, and agent memory private instead of sending them to a...
- Self-Hosted Apps vs SaaS: Why Running Your Own Nextcloud, Vaultwarden, or Pi-hole Beats Trusting a Third PartyWhat changes when you run your own Nextcloud, Vaultwarden, or Pi-hole instead of trusting a SaaS provider, and how an anonymous VPS narrows the last privacy...
- Managed vs Unmanaged VPS: Which Do You Actually Need?Managed means someone else has root. Unmanaged means you do. That decides the price, the privacy, and whether you can call anyone at 3 a.m. This guide helps...
- How to Set Up a Self-Hosted VPN with WireGuard on a VPSTen minutes from a fresh Ubuntu server to a WireGuard VPN you control: keys, config, forwarding, firewall, a phone client by QR code, and the two settings that...