# A self-hosted PaaS deploys from Git on your server. You still operate the host.

A self hosted PaaS deploys from Git on your server. You still run the OS, backups, patches, TLS, and recovery when that host is down.

Canonical URL: https://unbroker.cloud/blog/self-hosted-paas
Published: 2026-11-12
Reviewed: 2026-11-12
Author: Timoteo Borgobello

## The short answer

A self hosted PaaS gives you Git deploys on a server you operate. Coolify is the example here. It is open source and self-hostable. It builds each commit and ships it to any server you connect over SSH. You still run the operating system, the patches, the backups, DNS, the Coolify update, and the recovery when that host is down.

That is the middle of two pages you may already have open. A raw virtual machine and a managed platform are [VPS vs PaaS](https://unbroker.cloud/blog/vps-vs-paas). This page is Coolify vs managed PaaS: same Git deploy, different operator. If you already want the platform run for you, the commercial page is the [Coolify alternative](https://unbroker.cloud/alternatives/coolify).

## What a self-hosted PaaS is

Self-hosting Coolify means you run the Coolify instance on infrastructure you control. To self host Coolify you need a Linux server with SSH. Coolify only runs on Linux. The documented minimum for the instance itself is 2 CPU cores, 2 GB of RAM, and 10 GB of free disk, on amd64 or arm64. The same page says a smaller server can start Coolify and is not recommended, and that running builds on that same server can make it unresponsive. Keep more disk than the minimum for images, volumes, and backups. The table is [Start with self-hosted](https://coolify.io/docs/start-with-self-hosted).

What does Coolify manage? The [product page](https://coolify.io/) describes one dashboard for the servers, applications, databases, and services you connect. Builds can use Nixpacks, Railpack, a Dockerfile, or Docker Compose. Coolify can also serve a static site or run a prebuilt image. One-click databases on that page include PostgreSQL, MySQL, MariaDB, MongoDB, Redis, KeyDB, Dragonfly, and ClickHouse. Push to deploy is the Git path, for hosted and self-hosted Git platforms.

Coolify Cloud does not move the workloads. The database guide says Coolify Cloud hosts the Coolify instance only. In both cases the database runs on a server you provide. Applications, databases, services, and persistent data run on your servers. This page does not quote a Coolify Cloud price. The source is [Databases](https://coolify.io/docs/databases).

## What you still operate

Coolify is a privileged control plane. It stores credentials and uses SSH to deploy and manage Docker resources on your servers. The [security model](https://coolify.io/docs/core/security-model) draws the line. Coolify provides dashboard authentication, optional two-factor authentication, team access, encrypted storage for supported secrets, webhook checks, server-local proxy routing, and HTTPS certificate automation for configured domains. You remain responsible for the operating system and Docker updates, SSH, the firewall, application code and images, DNS, workload data, backups, restore tests, monitoring, and incident response. Coolify Cloud changes who operates the Coolify instance. It does not transfer the servers, applications, databases, and services you provide.

| | Coolify on your server | Managed PaaS (Unbroker Cloud Apps) |
| --- | --- | --- |
| Operating system | You patch the OS, Docker, SSH, and the firewall. Server Patching can list package updates. It does not install them unless you choose to. | You do not administer the host OS. You ship the app. [Cloud Apps](https://docs.unbroker.cloud/apps/overview) builds and runs the service. |
| Control plane | You update a self-hosted instance, or you enable automatic updates. Coolify Cloud updates are done by the Coolify team. The update changes Coolify, not your apps. | Unbroker runs the platform. There is no control-plane release for you to install. |
| Deploys | Coolify builds the commit and ships it over SSH to a server you connected. | Unbroker records the commit, builds, rolls out, and checks health. A failed health check does not go live. |
| TLS and DNS | Coolify automates HTTPS certificates for domains you configured. DNS records, and any port the challenge needs, stay with you. | Custom domains and managed TLS require Pro. You create the DNS record Unbroker shows. Verification and the certificate are separate stages. |
| Backups | An instance backup skips data inside apps, databases, and volumes. Some engines have a scheduled dump. You test the restore. | A volume can back up to an S3-compatible destination you configure. The volume is not itself a backup. |
| Monitoring | You configure monitoring, alerts, and the response. Coolify can notify you. That does not replace the plan. | Runtime logs are on Free and on Pro. Resource metrics are on Pro. How to read them is [logs, metrics and alerts](https://unbroker.cloud/blog/logs-metrics-alerts). |
| Capacity | The instance minimum is 2 CPU cores, 2 GB of RAM, and 10 GB of disk, plus the apps. Shared build load can make the server unresponsive. | Free is one replica, up to 250m CPU and 256 MiB, and it sleeps when idle. Pro bills configured CPU and memory while replicas run. |
| Host down | A reboot stops every container on that server. A one-click database is one container, without replication or failover in that resource. | Cloud Apps is not a machine you reboot. A [Linux cloud server](https://unbroker.cloud/cloud-servers) is a separate machine, and you operate it. |

## Backups and restore

Coolify has two backups, and they do not cover the same data.

An instance backup saves Coolify's own data: projects, resources, settings, and deployment history. It does not back up data stored inside your applications, databases, or volumes. For a self-hosted instance you configure it under Settings, then Backup. The default schedule is daily at midnight in the instance timezone. Keep a copy on another server or on your computer. Do not keep the only copy on the Coolify server. The Coolify team manages Coolify Cloud instance backups. You still back up the applications and databases on the servers you connected. The procedure is [Back up Coolify](https://coolify.io/docs/core/backup-and-recovery/instance-backup).

The instance backup also omits the encryption key. Coolify encrypts saved credentials and private keys before storing them. The `APP_KEY` in `/data/coolify/source/.env` is that key. A database backup does not include the file. Without the matching key, a restored database cannot be read. Save the key outside the server before you need it. The same warning is in the [security model](https://coolify.io/docs/core/security-model).

Database data needs its own schedule. [Databases](https://coolify.io/docs/databases) lists scheduled backups for PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, and experimental SQLite. Dashboard restore works for those except ClickHouse. Redis, Dragonfly, and KeyDB do not show a Backups page, so they have no scheduled backup and no dashboard restore. They still have persistent storage, and persistent storage is not a database-aware backup. Each schedule writes a local file on the database server and can upload a copy to S3-compatible storage, SFTP, FTPS, or WebDAV. If the database is stopped when the schedule fires, Coolify skips that run. A successful backup only proves that Coolify created a file. Restore a copy into a disposable database and check that the application can read it. It is not point-in-time recovery. The dump is the copy from the time the job ran. Local files live on the same server as the database, so a lost server takes the only copy with it unless you enabled an off-server destination.

The mechanics of the dump, retention, and the import dialog are [Database backups](https://coolify.io/docs/databases/backups). How a Postgres restore is checked on Unbroker, which is a different product, is [Postgres in production](https://unbroker.cloud/blog/postgres-in-production).

## Updates and security patches

Two updates are easy to mix up.

Updating Coolify changes the self-hosted control plane. It does not update the applications, databases, services, or servers you manage with Coolify. Before you update, create an instance backup, read the release notes, and check for active deployments. Deployments during the update can fail. If an instance backup is configured, Coolify runs it before a dashboard update and before an automatic update. A failed database backup prevents that update from starting. Running the upgrade script directly does not get that step. You create the backup yourself. Automatic updates are optional. While they apply, Coolify restarts and the dashboard is unavailable briefly, usually for less than a minute. If you use Coolify Cloud, the Coolify team manages instance updates. The page is [Update Coolify](https://coolify.io/docs/core/instance-management/update).

The operating system is the other update. [Server Patching](https://coolify.io/docs/core/infrastructure/servers/server-patching) lets you check for package updates and install them from the dashboard. It is marked Beta. By default Coolify does not install updates automatically. You choose one package or all of them. On Debian, Ubuntu, and RHEL-family servers you can turn on automatic security updates. Docker, kernel, and system updates can restart services or require a reboot. Review them, back up important applications and databases, and pick a maintenance window before Update all packages. A scheduled check can notify you. It does not install the packages.

The security model asks you to keep the operating system, Docker Engine, and the Coolify proxy updated, to use a dedicated SSH key, and to open only the ports you mean to expose. A compromised Coolify instance can reach connected servers, because Coolify stores SSH private keys and uses them to run commands. Restrict who can administer it.

## When the server goes down

The apps and databases run on the server you selected. If that server reboots, every container on it stops. Containers with a restart policy start again after the reboot. Coolify then checks the server for updates again five minutes later. That is [Server Patching](https://coolify.io/docs/core/infrastructure/servers/server-patching), in the reboot step.

A one-click database does not add a second node. The database guide says a one-click database is a single container. Replication, failover, and multi-node topologies are not part of that resource. Use a Compose service or an external database when you need those.

Recovery depends on a copy that is not on the failed disk. Instance backups should have a copy off the Coolify server. Database backups should have an off-server destination, and you should have restored one before the outage. The instance `APP_KEY` has to be in that same recovery set, or the restored secrets stay unreadable.

TLS fails in a quieter way. Coolify uses Let's Encrypt for domain certificates. The HTTP challenge needs port 80 reachable from the internet. The TLS-ALPN challenge needs port 443. You create the DNS records. Let's Encrypt looks up the name, and a bad A or AAAA record can fail the challenge. Certificates last 90 days. Coolify keeps using a certificate that is still valid. When it expires, a failed challenge means Coolify cannot issue a replacement. The troubleshooting page is [Let's Encrypt not generating SSL certificates](https://coolify.io/docs/troubleshoot/dns-and-domains/lets-encrypt-not-working).

## When self-hosting makes sense

Self-host Coolify when the control plane has to live on infrastructure you control, and the team will actually operate it.

That work is concrete. Someone patches the OS and Docker, saves `APP_KEY`, keeps instance backups off the box, schedules database dumps for the engines that have them, and restores a dump before trusting it. Someone also watches disk, SSH, and the certificate challenge. The [security model](https://coolify.io/docs/core/security-model) lists that as your layer, on self-hosted Coolify and on Coolify Cloud.

It also fits when the software is not a platform service and you already wanted a Linux host. How to decide that the workload needs the machine at all is [how to choose a Linux cloud server](https://unbroker.cloud/blog/linux-cloud-server).

## When a managed PaaS makes sense

A managed PaaS is the better fit when the team wants the Git deploy and does not want the host.

On Unbroker, Cloud Apps is that path. Unbroker builds the source when it has to, creates a deployment, rolls it out, checks health, and gives the service a URL. Web services can use custom domains with TLS. A failed health check prevents an unhealthy revision from being treated as live. Those two pages are [Cloud Apps](https://docs.unbroker.cloud/apps/overview) and [Deployments](https://docs.unbroker.cloud/deployments/overview).

Choose it when nobody is on the hook for sshd, the host firewall, a control-plane upgrade, or a restore drill. The longer split between a raw server and this platform is [VPS vs PaaS](https://unbroker.cloud/blog/vps-vs-paas). The page for choosing Unbroker instead of operating Coolify is the [Coolify alternative](https://unbroker.cloud/alternatives/coolify).

## How it works on Unbroker

Cloud Apps is the managed path. A service can come from a Git repository, a Dockerfile, a container image, or an uploaded static site. You do not assemble the deployment platform, and you do not patch the host that runs the service. The description is [Cloud Apps](https://docs.unbroker.cloud/apps/overview).

Free is $0. It is one project, two services in total, and three deploy requests per UTC day. Unused deploys do not carry forward. Each Free service runs one replica, up to 250m CPU and 256 MiB, and sleeps when idle. The first request after a sleep can take longer. Static sites and managed Node.js are included. Dockerfile builds, other framework recipes, persistent volumes, managed databases, Linux cloud servers, custom domains, and managed TLS are not on Free. They require Pro. Pro applications are not paused for inactivity unless Serverless is enabled. The rows are [Plans](https://docs.unbroker.cloud/billing/plans) and the [pricing page](https://unbroker.cloud/pricing).

Pro is $25 a month with $25 of usage credit. The credit resets each billing cycle, does not roll over, and has no cash value. If eligible usage stays under the credit, the monthly charge is still the plan price. If eligible usage is above the credit, only the difference is added. Prices are in USD and exclude applicable taxes. Those terms are effective from September 23, 2026. App CPU is $0.03 per configured vCPU-hour and memory is $0.015 per configured GiB-hour while replicas run. A short utilization spike does not change that line. The meters are [Billing and usage](https://docs.unbroker.cloud/billing/billing-and-usage).

On Pro, repository and upload services can run more than one replica. Image services, workers, and any service with a persistent volume run one. On the shared cell a service can run up to 3 replicas. With autoscale, new replicas start within about 30 seconds of sustained load, and extra replicas are removed after about 5 minutes of low load. You are billed for the replicas that are actually running. The limits are [Service types](https://docs.unbroker.cloud/apps/services).

Custom domains and managed TLS require Pro. You add the hostname, create the DNS record Unbroker shows, and wait for verification and certificate readiness. Keep the default hostname. The steps are [Domains and TLS](https://docs.unbroker.cloud/deployments/domains).

Files on a container filesystem are temporary. A persistent volume is a durable path for one service. It can grow and it cannot shrink. Deleting the service deletes the volume. Cloud Apps can send volume backups to an S3-compatible destination you control. A volume is not itself a backup. Configure one and test a restore before the data matters. That is [Persistent storage and backups](https://docs.unbroker.cloud/apps/storage).

Runtime logs are available on Free and on Pro. Resource metrics are part of Pro. Alerts help you notice a problem. They do not replace application telemetry. The signals and the plan split are [logs, metrics and alerts](https://unbroker.cloud/blog/logs-metrics-alerts) and [monitoring](https://docs.unbroker.cloud/apps/monitoring).

A Linux cloud server is the other Unbroker product, for software that needs the machine. Unbroker shows the region, plan, state, image, and address, and it can power, reboot, or delete the machine. You are responsible for the operating system, software installation, security updates, the firewall, process supervision, deploys, monitoring agents, and the data on the disk. Servers require Pro. On the [pricing page](https://unbroker.cloud/pricing), the S size is $17.95 a month for 4 vCPU, 8 GB of RAM, and 100 GB of SSD, with unlimited traffic under fair use. It is a monthly contract. Cancelling schedules the stop at the end of the month you have paid for. The responsibility split is [Servers](https://docs.unbroker.cloud/infrastructure/servers). The decision in front of that machine is [how to choose a Linux cloud server](https://unbroker.cloud/blog/linux-cloud-server).

## Checklist

1. Count the Coolify instance first: 2 CPU cores, 2 GB of RAM, and 10 GB of disk, on Linux, before the apps. A smaller box is documented as not recommended.
2. Name who patches the OS, Docker, and SSH. Server Patching does not install packages until you tell it to.
3. Save `APP_KEY` outside the server. An instance backup does not include `/data/coolify/source/.env`.
4. Turn on database backups only for engines that have them. Copy the file off the server. Restore it once into a disposable database.
5. Do not expect that schedule for Redis, Dragonfly, or KeyDB. They have no Backups page.
6. Create the DNS records yourself. Confirm the Let's Encrypt challenge can reach the server before the 90-day certificate expires.
7. Treat a one-click database as one container. Replication and failover are not part of that resource.
8. If nobody will do the steps above, use Cloud Apps. Read [Plans](https://docs.unbroker.cloud/billing/plans) before you assume Free includes volumes, Dockerfiles, or servers.
9. If the workload needs root, use a [Linux cloud server](https://unbroker.cloud/cloud-servers) and keep operating it. The size and the monthly price are on [pricing](https://unbroker.cloud/pricing).
10. Compare a raw VPS with the managed platform in [VPS vs PaaS](https://unbroker.cloud/blog/vps-vs-paas) before you add a control plane to a machine you already have to patch.

## FAQ

### What is a self hosted PaaS?

A self hosted PaaS deploys from Git onto a server you operate. Coolify is the example on this page. It is open source and self-hostable, and it builds each commit and ships it to a server you connect over SSH. You still run the operating system, Docker updates, backups, DNS, and recovery when that host is down. The product description is on [coolify.io](https://coolify.io/). The install requirements are in [Start with self-hosted](https://coolify.io/docs/start-with-self-hosted).

### What does Coolify manage?

Coolify is the control plane. It stores credentials, connects to your servers over SSH, and deploys Docker resources. It provides dashboard sign-in, optional two-factor authentication, team access, encrypted storage for supported secrets, and HTTPS certificate automation for configured domains. It does not replace host hardening, application security, or an incident plan. That split is the [security model](https://coolify.io/docs/core/security-model).

### What is the difference in Coolify vs managed PaaS?

On Coolify you supply the servers. Applications, databases, and persistent data run there, including when Coolify Cloud operates the control plane. On Unbroker Cloud Apps, Unbroker builds the revision, rolls it out, and checks health. You do not administer that host OS. A Linux cloud server on Unbroker is a different product: you operate the machine. The Coolify boundary is in the [security model](https://coolify.io/docs/core/security-model). The Unbroker app path is [Cloud Apps](https://docs.unbroker.cloud/apps/overview).

### Does Coolify back up my database?

An instance backup does not. It saves Coolify's projects, settings, and deployment history, not data inside applications, databases, or volumes. Scheduled database backups exist for PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, and experimental SQLite. Dashboard restore works for those except ClickHouse. Redis, Dragonfly, and KeyDB have no Backups page. A successful backup only proves that a file was created. The pages are [Instance backup](https://coolify.io/docs/core/backup-and-recovery/instance-backup) and [Databases](https://coolify.io/docs/databases).

### What happens when the server running Coolify goes down?

Workloads on that server stop with it. A reboot from Server Patching stops every container on the server. Containers with a restart policy start again after the reboot. A one-click database is a single container, and replication and failover are not part of that resource. A backup that exists only on that disk is unavailable while the disk is down. Those limits are in [Server Patching](https://coolify.io/docs/core/infrastructure/servers/server-patching) and [Databases](https://coolify.io/docs/databases).

### When should I self host Coolify instead of a managed PaaS?

Self host Coolify when you want the control plane on infrastructure you control and someone will patch the OS, save the instance key, and restore a backup before you need it. Use a managed PaaS when you want Git deploys and health checks without that work. The commercial comparison, for the case where Unbroker runs the platform, is the [Coolify alternative](https://unbroker.cloud/alternatives/coolify).

## Related reading

- [Coolify alternative](https://unbroker.cloud/alternatives/coolify)
- [VPS vs PaaS](https://unbroker.cloud/blog/vps-vs-paas)
- [How to choose a Linux cloud server](https://unbroker.cloud/blog/linux-cloud-server)
- [Postgres in production](https://unbroker.cloud/blog/postgres-in-production)
- [Logs, metrics and alerts](https://unbroker.cloud/blog/logs-metrics-alerts)
- [Pricing](https://unbroker.cloud/pricing)
- [Linux cloud server hosting](https://unbroker.cloud/cloud-servers)
