Heroku's free tier is long gone, and the paid tiers add up fast once you're running more than a side project. That's the whole reason "self hosted heroku alternative" (or "heroku self hosted alternative," same search, different word order) shows up in Search Console at all, it's not a hypothetical. The good news: you don't need to hand-roll your own Docker and Nginx setup anymore. Coolify, CapRover and Dokploy all give you the same git-push-to-deploy experience Heroku made popular, running on a VPS you actually own.
All three are open source, all three are Apache 2.0 licensed, and all three are free to self-host. The differences that actually matter come down to how mature the project is, how big the one-click app catalog is, and how much server the tool itself needs before your apps even start running.
Quick answer
Jump to a section
Why look for a self-hosted Heroku alternative
Three reasons come up constantly. Heroku's pricing moved from "generous free tier" to "pay per dyno, per add-on, per everything" years ago, and for a team running a handful of apps that bill stings. Vendor lock-in is the second one: your app, your database, and your deploy pipeline all live inside Heroku's world, and moving off it later is its own project. And the third is simpler: some teams just want their data on infrastructure they control, full stop, no third party in the loop.
Coolify, CapRover and Dokploy all solve the same core problem. You point them at a Git repo, they build a Docker image, they handle SSL through Let's Encrypt, and your app is live on a domain. No Kubernetes, no manually wiring up Nginx and Certbot at 11pm.
How to choose between Coolify, CapRover and Dokploy
Skip the exhaustive feature matrix. Three questions get you most of the way there:
- How big is your app catalog need? If you want one-click databases, CMSs, and AI tooling alongside your own apps, Coolify's 280+ service catalog is well ahead of the other two. If you're only ever deploying your own code, that catalog size barely matters.
- How much server can you spare? CapRover is the lightest of the three and runs fine on a 1GB RAM VPS. Coolify and Dokploy both want more headroom, in practice closer to 2GB, before the panel itself and your apps are comfortable together.
- Do you want a managed cloud option later? Coolify Cloud and Dokploy's managed plan both exist if you ever want someone else to run the control panel while you keep your apps on your own servers. CapRover has no such option, it's self-hosted or nothing.
1. Coolify: the most complete open source PaaS
Coolify is the one we deploy for clients and package as an AWS AMI, so this isn't a cold read of the docs. It's an Apache 2.0 licensed, self-hostable alternative to Vercel, Heroku and Netlify, and by mid-2026 it had crossed 55,000 GitHub stars, which is a fast climb for infrastructure software. Connect a Git repo, push, and Coolify handles the Docker build, SSL, domain routing and health checks. The v4.0 catalog covers 280+ one-click services: Postgres, Redis, Ghost, n8n, Ollama, the list keeps growing.
Key features
- 280+ one-click services: databases, CMSs, workflow tools, AI inference engines
- Git push to deploy, with automatic Docker builds and health checks
- Automatic SSL via Let's Encrypt on custom domains
- Multi-server support, so one Coolify instance can manage several VPS targets
- Built-in backups for databases with configurable schedules
- Optional Coolify Cloud managed panel at $5/month per server, entirely optional
Pros
- Largest one-click app catalog of the three by a wide margin
- Fastest-moving project, new features ship constantly
- Genuinely no paid tier required for full functionality
Cons
- Wants more RAM than CapRover for the panel itself
- Moving fast means occasional rough edges between releases
- Multi-server setup takes more planning than a single-box CapRover install
2. CapRover: the lightweight, battle-tested option
CapRover has been around longer than the other two and it shows, in a good way. It's built on Docker Swarm rather than plain Docker, uses Traefik or Caddy as the reverse proxy, and handles Let's Encrypt SSL automatically. The app store ships around 100 pre-built one-click apps, smaller than Coolify's catalog but covering the basics most people actually deploy.
Key features
- Docker Swarm-native, so multi-server scaling is built in rather than bolted on
- Around 100 one-click apps in the store
- CLI deployment alongside the web dashboard
- Web-based terminal to SSH into containers straight from the browser
- Persistent volumes handled through the UI, no manual Docker volume commands
- Runs comfortably on a 1GB RAM VPS for hobby-scale workloads
Pros
- Lightest resource footprint of the three, ideal for small VPS instances
- Years of production use behind it, the codebase is genuinely stable
- Native Docker Swarm clustering without extra tooling
Cons
- The UI feels dated next to Coolify and Dokploy
- Smaller app catalog and a slower feature release cadence
- No managed cloud option if you ever want one
3. Dokploy: built around Docker Compose
Dokploy is the newest of the three and one of the fastest-growing open source deployment tools in 2026. Where Coolify leans on its service catalog, Dokploy leans on flexibility in how you actually build your app: Nixpacks, Heroku-style buildpacks, or a custom Dockerfile, plus native Docker Compose support for projects that are already structured that way. It also covers the database side directly, with managed setups for MySQL, PostgreSQL, MongoDB, MariaDB and Redis.
Key features
- Native Docker Compose deploys for projects already using a compose file
- Supports Nixpacks, Heroku buildpacks, and custom Dockerfiles
- Built-in database management for MySQL, PostgreSQL, MongoDB, MariaDB and Redis
- Multi-server deployment support
- Real-time monitoring dashboards for CPU, memory and logs
- Optional managed cloud plan, priced per server
Pros
- Best fit if your project already ships as a Docker Compose stack
- Wide buildpack support without extra configuration
- Active, fast-moving development in 2026
Cons
- Smaller one-click app catalog than Coolify
- Younger project, so the community and third-party guides are thinner
- Managed cloud plan costs more than Coolify's once you add servers
Coolify vs CapRover vs Dokploy: feature comparison
| Feature | Coolify | CapRover | Dokploy |
|---|---|---|---|
| License | Apache 2.0 | Apache 2.0 | Apache 2.0 |
| Underlying engine | Docker | Docker Swarm | Docker |
| One-click app catalog | 280+ services | ~100 apps | Smaller, growing |
| Docker Compose support | Yes | Limited | Native, first-class |
| Buildpack support | Nixpacks | Dockerfile-based | Nixpacks, Heroku buildpacks, Dockerfile |
| Minimum practical RAM | ~2GB | 1GB | ~2GB |
| Multi-server support | Yes | Yes, Swarm-native | Yes |
| Managed cloud option | Coolify Cloud, $5/mo per server | None | Yes, $4.50/mo base + $3.50/server |
| Project maturity | Established, fast-growing | Oldest, most battle-tested | Newest, fast-growing |
| Best for | Teams wanting the widest app catalog | Small VPS, hobby to small production | Compose-based projects |
Migrating off Heroku: what actually moves and what doesn't
The apps themselves move easily. If your app already runs in a container, or Heroku is already building it from a buildpack, that same Dockerfile or buildpack works on any of these three with little to no change. That part is rarely where migrations get stuck.
Where it gets slower:
- Add-ons. Heroku's marketplace add-ons (Redis, Postgres, scheduled jobs, log drains) don't come with you. You'll stand up the equivalent yourself, which is exactly what Coolify's and Dokploy's one-click database services are for.
- Environment variables and secrets. These export cleanly from the Heroku CLI, but double-check anything tied to a Heroku-specific service URL, it will need to point at your new database instead.
- Review apps and pipelines. Heroku's automatic per-PR review apps don't have a direct equivalent in any of the three. You can approximate it with CI plus the deploy API each tool exposes, but budget time to wire that up rather than assuming it transfers.
- DNS cutover. Point your domain at the new server only after you've confirmed the app runs correctly on the new platform. Keep the Heroku app alive and unbilled (or on a low tier) for a week as a rollback path.
None of this is hard, it's just not zero-effort. Set aside an afternoon per app, not five minutes.
Why we run Coolify on AWS
Most teams who ask us about self-hosted PaaS options aren't trying to replace a huge Heroku bill overnight, they just want somewhere to put a handful of apps without babysitting a raw EC2 instance. Coolify's app catalog and the pace it ships at made it the easy default for us. We package it as a ready-to-launch AMI, so the parts that normally eat a Saturday, Docker setup, reverse proxy, SSL, are already done when the instance boots.
If you'd rather run it yourself first, our Coolify developer guide and single-click AWS setup guide both cover the manual install end to end.
Where I'd start
Want the widest catalog and the most active project to bet on: Coolify. It's the one we run, and for most teams evaluating a self hosted Heroku alternative today, it's the strongest all-round pick.
Running on a single small VPS with a tight budget, or you just want something that hasn't changed much in years because it didn't need to: CapRover. It's the lightest of the three and it's earned its stability the boring way, by being around long enough to sand off the rough edges.
Already have your project structured as a Docker Compose stack and don't want to fight the tool to deploy it as-is: Dokploy. It's the youngest option here, but it's growing fast for a reason.
Whichever you pick, none of them need Kubernetes, none of them charge for the self-hosted core, and all three will get you off Heroku's invoice within an afternoon.
Frequently Asked Questions
What is the best self-hosted Heroku alternative?
Coolify, for most teams. It has the largest one-click service catalog of the three, the fastest development pace, and it's what we deploy and support ourselves. CapRover is the safer pick if you want something older and more battle-tested; Dokploy if you want native Docker Compose deploys.
Coolify vs CapRover: which should I choose?
Coolify if you want a modern interface and a bigger app catalog. CapRover if you want a tool that's barely changed in years, in a good way, and runs fine on a 1GB VPS. Both are Apache 2.0 and free to self-host.
Coolify vs Dokploy: what's the real difference?
Less than the marketing suggests. Both are Apache 2.0, both target the same Heroku-replacement use case, and both update fast. Coolify has the bigger community and app store right now; Dokploy leans harder into native Docker Compose projects rather than buildpacks.
Is Coolify actually free to self-host?
Yes. The self-hosted version is Apache 2.0 licensed with nothing behind a paywall. Coolify Cloud, the optional managed panel, costs $5 a month per server, but you don't need it to run Coolify yourself.
What is a good open source PaaS for a small team?
Coolify, if the team wants one dashboard for apps, databases, and one-click services without touching Kubernetes. If you're a single developer with one VPS and want the lightest possible footprint, CapRover is worth a look too.
Do I need Kubernetes to self-host a Heroku alternative?
No. Coolify and Dokploy run on plain Docker. CapRover runs on Docker Swarm, which is Docker's built-in clustering mode, not Kubernetes. All three work fine on a single VPS with no cluster at all.
Launch Coolify on AWS Without the Manual Setup
Launch a pre-configured Coolify server on AWS with Docker, SSL and the reverse proxy already set up, ready to deploy your first app.
Get Coolify on AWS Marketplace
