toolfreebie

Posted on Aug 20 Originally published at toolfreebie.com

Coolify: Free Self-Hosted App Hosting (Your Own Heroku)

#hosting #devops

Quick answer: Coolify is a free, open-source (Apache 2.0) self-hosted PaaS — a Heroku/Vercel/Netlify alternative you install on your own server with one command. There are no feature gates, user limits, or usage meters: the only cost is the server itself, which can be $0 if you run it on an Oracle Cloud Always Free ARM VPS. The optional Coolify Cloud ($5/month) only hosts the control panel, not your apps.

Managed platforms give you push-to-deploy for free — until traffic, a database, and a worker turn the free tier into an $80/month bill. Coolify closes that gap: it gives a cheap VPS you own the same Git-driven deploys, automatic HTTPS, and one-click databases you were renting. You bring the server; Coolify brings the platform.

Free Tier at a Glance

Dimension	Coolify (self-hosted)
Cost	$0 — Apache 2.0, no feature gates. You pay only for the server, which can be $0 on an Oracle Always Free VPS
Resources	Whatever your server has. Coolify needs min 2 vCPU / 2 GB RAM / 30 GB disk (idles ~800 MB); 4 cores / 8 GB is comfortable
What you can deploy	Anything containerizable — Node, Python, Go, PHP, Rust, static sites, Docker Compose — plus 280+ one-click services and managed databases
What you can’t	Nothing is platform-gated; you’re limited only by your server’s size. It’s not managed hosting — no one runs the box for you
Sleeps?	No — it’s your always-on server
Expires?	No — free forever, no trial clock
Commercial use	Yes — Apache 2.0, no restrictions
Region / country	Wherever your server is — you choose the provider and location
Credit card	Not for Coolify itself (free software). Your server provider may require one

What Is Coolify?

Coolify is a self-hosted Platform-as-a-Service. You install it on a Linux server you control — a VPS, bare metal, even a Raspberry Pi — and it becomes a control plane that orchestrates Docker containers, configures a reverse proxy, provisions TLS, and watches your Git repos for changes. You manage everything from a web dashboard instead of hand-editing docker-compose and Nginx. It’s 57,000+ GitHub stars on coollabsio/coolify as of mid-2026.

Git-driven deploys. Connect GitHub, GitLab, Bitbucket, or Gitea and Coolify rebuilds on every push — via Nixpacks (zero-config buildpacks), a Dockerfile, or Docker Compose.
Automatic HTTPS. Traefik (or Caddy) handles routing and Let’s Encrypt certificates. Point a domain at your server, type it in, and you get a working https:// URL — no manual certbot.
No vendor lock-in. Coolify writes standard Docker configs to your server. Stop using it and your containers and data are still sitting on a machine you own.

Is Coolify Really Free?

Yes — the cleanest “free” in this category, because there’s no usage meter to run out of. Self-hosted Coolify is Apache 2.0 with no feature gates, no user/app/server limits, no “upgrade to unlock” walls. Everything Coolify does, the free version does. Your only cost is the server you were paying for anyway.

The paid product, Coolify Cloud, does not host your apps — you still bring your own servers. It hosts the Coolify control panel itself, so you don’t dedicate a server to running Coolify or keep it patched.

Option	Cost	What you get
Self-hosted (Apache 2.0)	$0	Full platform, all features, unlimited apps/users/servers. You host the Coolify instance.
Coolify Cloud	$5/month (≈$4 billed annually)	Coolify hosts the control panel; connect up to 2 servers. +$3/mo per extra server.

The honest reading: the free self-hosted version is the real product, and most individuals and small teams never need anything else. Cloud’s $5/month only buys you out of maintaining the Coolify instance — worth it if you run many servers and don’t want a single point of failure, but unnecessary for “one VPS, Heroku-on-it.”

What You Get on the Free Version

Because there are no tiers, the free version is the entire feature set:

280+ one-click services — WordPress, Ghost, n8n, Plausible, Uptime Kuma, MinIO, Appwrite, Supabase, and hundreds more, deployed with sensible defaults.
Managed databases — PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly, or ClickHouse, with scheduled backups to S3-compatible storage.
Flexible builds — Nixpacks, Dockerfile, Docker Compose, or static site — covering Node, Python, Go, PHP, Rust, Ruby, anything containerizable.
Preview deployments — spin up a temporary environment per pull request, torn down when the PR closes.
Multi-server orchestration — one instance manages many remote servers over SSH.
Auto-SSL, auto-deploy, notifications — Traefik/Caddy with Let’s Encrypt, Git webhooks, and deploy alerts to Discord, Telegram, Slack, or email.

Where to Run It (System Requirements)

From the official installation docs:

Spec	Minimum	Comfortable (production)
CPU	2 cores	4 cores
RAM	2 GB	8 GB
Storage	30 GB free	150 GB
Architecture	64-bit AMD64 or ARM64

Coolify idles at roughly 800 MB of RAM, so 2 GB is fine to learn on but a couple of real apps plus a database want 4 GB+. The key detail: Coolify runs on ARM64, and the Oracle Cloud Always Free tier gives you a 4-core, 24 GB ARM VPS at no cost, forever. That combination is the closest thing to a permanently free, full-featured self-hosted Heroku in 2026.

Install Coolify in 5 Minutes

SSH into a fresh server (as root or sudo) and run the official script — it installs Docker if missing, sets up Coolify’s containers, and starts the dashboard:

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

It prints a URL, typically http://YOUR_SERVER_IP:8000. Open it and you land on a one-time registration screen. Register immediately — the first account becomes admin, and leaving that open on a public IP is the one security mistake to avoid. Then point Coolify at a domain (add an A record, set it in settings) and Traefik issues Let’s Encrypt certificates automatically.

Deploy Your First App from Git

Create a project — a container for related resources (app, database, cache). Pick the server and environment.
Add a resource → Public/Private Repository — paste a GitHub URL, or connect via the Coolify GitHub App for private repos and webhooks.
Pick a build pack — leave it on Nixpacks (auto-detects Node, Python, Go, PHP, Rust) or choose Dockerfile/Compose if your repo has one.
Set domain and env vars — Coolify wires up the proxy and SSL; env vars are stored encrypted.
Deploy — Coolify clones, builds, starts the container, routes the domain, issues a certificate, and streams build logs live.

After this, every push to the configured branch triggers a zero-downtime redeploy (health-checked before switching traffic). Need a database? Add a resource → Database → PostgreSQL and Coolify gives you a managed instance with an internal connection string — no apt install postgres.

One-Click Services and Self-Hosted Apps

A huge part of Coolify’s appeal is the 280+ one-click templates — pre-packaged deployments of popular open-source software. You click, tweak a few settings, and Coolify stands up the whole stack (app, database, volumes, proxy routes):

Content & sites: WordPress, Ghost, Directus, Strapi, Outline
Automation & dev tools: n8n, Gitea, Appsmith, NocoDB, Metabase
Analytics & monitoring: Plausible, Umami, Uptime Kuma, Grafana
Backend & storage: Supabase, Appwrite, MinIO, PocketBase
AI & productivity: Open WebUI, Nextcloud, Vaultwarden

This is where Coolify becomes “your personal cloud.” Each service lands on your server, behind your domain, with SSL, in minutes — and costs nothing beyond the server you’re already paying for.

Coolify vs Dokploy vs CapRover vs Managed Hosting

Platform	Model	Cost	Strengths	Watch-outs
Coolify	Self-hosted PaaS (Apache 2.0)	Free (your server)	Huge catalog, multi-server, Docker Compose, big community, preview deploys	You own uptime & security
Dokploy	Self-hosted PaaS (Apache 2.0)	Free (your server)	Clean UI, Docker Swarm-based, Traefik built in	Younger, smaller template library
CapRover	Self-hosted PaaS (Apache 2.0)	Free (your server)	Mature, stable, CLI-friendly	Older UI, Swarm only, less active
Railway	Managed PaaS	~$5/mo + usage	Zero ops, instant, great DX	Costs scale; you don’t own infra
Render	Managed PaaS	Free tier + paid	True free tier, managed databases	Free services sleep; usage-based above it

Coolify, Dokploy, and CapRover are the same category — you bring a server, they give it a platform. Coolify wins on breadth (largest catalog, Compose support, multi-server, most active community), Dokploy is the sleek Swarm-based up-and-comer, and CapRover is the battle-tested veteran. Railway and Render are the other side — they manage the server for you, worth real money when your time is scarce, but you pay per usage and never own the machine.

When to Self-Host — and When Not To

One small app, want zero ops? → Use a managed free tier like Render or other free hosting. Don’t take on server maintenance for a single hobby project.
Static sites or a frontend? → Use Vercel, Netlify, or Cloudflare Pages — a self-hosted PaaS is overkill.
Several apps, want managed databases, hate per-usage bills, comfortable with a server? → This is Coolify’s sweet spot. One VPS, many apps, auto-SSL, push-to-deploy, flat cost (or free on Oracle).
Can’t tolerate being responsible for uptime, patching, and backups? → Stay managed. Self-hosting means you are the on-call engineer.

Limits and Honest Caveats

You are the ops team. Coolify automates deploys, SSL, and proxying, but OS updates, firewall config, disk monitoring, and disaster recovery are still yours. Configure the built-in S3 backups on day one.
A single server is a single point of failure. If Coolify and all your apps share one VPS and it goes down, so does the dashboard you’d fix it from. For anything important, separate the control panel from production apps.
The 2 GB minimum is really a minimum. Coolify idles near 800 MB, and builds (especially Node) are memory-hungry. Budget 4 GB+ for real workloads — or take the 24 GB Oracle ARM box.
Beta cadence. Coolify moves fast and the v4 series spent a long stretch in beta. Read release notes and back up before upgrading a production instance.

Frequently Asked Questions

Is Coolify really free?

Yes. The self-hosted version is Apache 2.0 with no feature gates, user limits, or application limits — the full platform is free software. Your only cost is the server. The optional Coolify Cloud ($5/month) doesn’t host your apps; it hosts the control panel so you don’t maintain that instance yourself.

What are the minimum requirements?

A 64-bit Linux server (AMD64 or ARM64) with at least 2 CPU cores, 2 GB RAM, and 30 GB free storage. For comfortable production use with several apps and databases, 4 cores and 8 GB is a better target. Coolify itself idles at roughly 800 MB of RAM.

Can I run Coolify for free forever?

Effectively yes, if you pair it with a free server. Coolify supports ARM64, and the Oracle Cloud Always Free tier provides a 4-core, 24 GB ARM VPS at no cost indefinitely. Free software on free hardware is a permanently free, full-featured self-hosted PaaS.

Coolify vs Railway — what’s the difference?

Railway is fully managed: it owns the servers and you pay per usage with zero ops. Coolify is self-hosted: you own the server and pay only your hosting provider, but you’re responsible for upkeep. Choose Railway to never touch a server; choose Coolify for predictable flat cost and full control.

Bottom Line

Coolify closes the gap that used to force you onto a managed platform: it gives a server you already own the same push-to-deploy, auto-SSL, one-click-database experience you were renting — for free, as Apache-2.0 software, with no usage meter and no feature gates. Have a VPS and several apps? Install it with one command. Want it truly free? Run it on an Oracle Cloud Always Free ARM VPS. Just one small app with no desire to own a server? Reach for a managed free tier like Render instead.

DEV Community