Self-hosting Coolify vs managed Coolify: how to choose

You've used Coolify and you like it. Git push, automatic SSL, one-click databases, no per-seat pricing. The question now is not whether to use Coolify. It's who runs it.

There are three answers, and they're often confused with each other. You can install Coolify yourself on a VPS. You can use Coolify Cloud, which hosts the control panel but not your apps. Or you can pay someone to run the whole thing, server included.

They're priced differently because they're different products. Here's what each one actually involves.

Option 1: self-host Coolify on your own VPS

This is the default, and for a lot of people it's the right call.

Coolify is open source under Apache 2.0 and free forever when you host it yourself. You rent a VPS, run the single-command install script, and you have a working deployment platform. The only bill is the server.

The install is easy. The part people underestimate is the next two years.

You own the operating system. Kernel patches, package upgrades, reboots after a security advisory. Unattended upgrades cover some of it. Some of it needs you.

You own Coolify updates. Coolify checks for new versions on a schedule and shows an upgrade button in the dashboard. You can pick automatic, semi-automatic, or fully manual updates. Coolify's own documentation recommends disabling automatic updates on production instances, which means the update decision comes back to you, along with the job of reading release notes before pressing the button.

You own the security posture. Firewall rules, SSH key authentication, closing the ports the install script didn't. A fresh VPS with a public IP starts getting scanned within minutes.

You own disk pressure. This is the failure mode that bites self-hosters most often. Docker images, build cache, stopped containers, and old volumes accumulate until a deploy fails at 3am with no space left on device.

Coolify has good tooling for this. Automated Docker cleanup runs on a cron schedule, or when disk usage crosses a threshold you set under Servers, Configuration, Advanced. It removes stopped containers, unused images, and build cache. You still have to turn it on and pick sensible values.

You own backups. Coolify can back up your databases to any S3-compatible storage on a schedule with a retention policy. It doesn't back up the server itself. If the VM is lost, you're rebuilding the host, reinstalling Coolify, and restoring from those dumps. That works, if you've tested it.

You're on call. Not in a pager-duty sense, but in the sense that when your side project's Postgres container won't come back up on a Saturday, the person fixing it is you.

None of this is hard. It's just never finished. Self-hosting on a $10 VPS is genuinely a great deal if you enjoy that work, or if your monthly hosting budget matters more than your weekends. Plenty of excellent projects run exactly this way.

Option 2: Coolify Cloud

Coolify Cloud is the part people most often misread, so it's worth being precise.

Coolify Cloud hosts the control panel. The Coolify instance itself runs on Coolify's infrastructure, maintained by the Coolify team, with community support plus limited email support. You don't allocate CPU, RAM, or disk to running Coolify, and you don't maintain the Coolify application.

You still bring your own servers. You connect a VPS, an EC2 instance, or a Raspberry Pi over SSH, and your applications deploy onto that machine. Pricing is $5 USD/month for the base plan covering up to two connected servers, plus $3 USD/month for each additional server, on top of whatever you pay your VPS provider.

Here's the boundary that matters: Coolify Cloud manages the Coolify instance, not your server. The operating system, the firewall, the disk, the security updates on the machine your apps run on, all still yours.

So Coolify Cloud removes one item from the self-hosting list above. It's a good deal at $5/month for what it does. Just don't buy it expecting the server maintenance to go away, because that isn't what it's for.

Option 3: fully managed Coolify

The third option is paying for the server and its upkeep together.

That's what MapleDeploy does. You get a dedicated VM in Toronto with your own Coolify instance on it. Not a shared container on someone else's box. Your own VM, with dedicated RAM, CPU, and storage.

What's handled for you:

• Provisioning. Pick a plan, and the server is ready in minutes.
• Security hardening. SSH key authentication, fail2ban, outbound SMTP blocking, and automatic security patches, applied before you first log in.
• OS patches and maintenance. Operating system updates and kernel patches are applied for you. No SSH sessions, no maintenance windows on your calendar.
• Coolify itself. MapleDeploy runs a public fork of Coolify that we rebase regularly against upstream. Changes are limited to Canadian branding and MapleDeploy integrations, and you can read the diff.
• Snapshots. Weekly full-server snapshots covering the OS, Coolify, containers, volumes, and databases, plus a snapshot taken before any VM termination and retained for 30 days after cancellation.
• Monitoring. CPU and memory metrics stream into the Coolify dashboard. Nothing third-party to wire up.

Two honest caveats.

First, snapshots are disaster recovery, not granular restores. A snapshot can be up to seven days old. For production databases you should still configure Coolify's S3 database backups on a daily schedule. Two layers, different jobs.

Second, MapleDeploy is self-service, not a consulting arrangement. We run the server. You deploy your apps, configure your domains, and manage your databases through the Coolify dashboard. If you need someone to architect your deployment for you, you want a DevOps consultant, and MapleDeploy is the platform they'd deploy onto.

The other axis: where your data lives

Cost and effort are the obvious comparison. Jurisdiction is the one that decides it for some readers.

Self-hosting lets you put Coolify anywhere, including a Canadian provider, so this isn't an argument against it. But most of the cheap, popular VPS options developers reach for are US-owned or US-hosted, which puts your data within reach of the CLOUD Act regardless of which city the machine sits in.

MapleDeploy runs on Canadian infrastructure in Toronto, with a privately owned Canadian provider that has no US parent company. Your code and your data stay under Canadian law, on infrastructure built for PIPEDA compliance. If that matters to you on principle or to your clients in procurement, it's included on every plan rather than sold as an add-on.

How to actually decide

A rough decision rule:

• Self-host if hosting cost is your binding constraint, you're comfortable on a Linux box, and an occasional weekend fixing your own infrastructure sounds fine. This is the honest answer for most hobby projects and side projects.
• Coolify Cloud if you're already managing servers you're happy with and you just don't want the Coolify instance to be one more thing to patch.
• Fully managed if your time is worth more than the price difference, if something is running that customers depend on, or if you need your data in Canada without auditing a VPS provider's ownership structure.

The comparison isn't $10 versus $45. It's $10 plus your evenings versus $45. Some months that's an easy call in one direction, some months in the other.

MapleDeploy starts at $45 CAD/month for a dedicated Toronto VM with 4 GB RAM, 2 vCPUs, and 35 GB of storage, flat, with no per-project or usage fees. See pricing for the full range of plans. Starter and Pro include a 30-day free trial, which is enough time to deploy something real and find out whether the managed version is worth it to you.

If you'd rather start by seeing how Coolify deploys work, our Coolify deployment guide walks through a full app from repo to custom domain. That workflow is identical whichever option you pick, which is exactly the point of building on open source.