What is Coolify

Coolify is an open source, self-hostable platform for deploying and managing applications, databases, and services on servers you control.

Coolify gives you a platform-as-a-service (PaaS) workflow for configuring, deploying, and operating a resource from a dashboard or API, while the workloads remain standard Docker resources on your infrastructure.

The short version

Coolify is the control plane for your infrastructure. Coolify connects to each server over SSH, prepares the server to run Docker workloads, and coordinates builds, deployments, domains, HTTPS, health checks, and day-to-day operations.

You can run the Coolify instance yourself or use Coolify Cloud. In both cases, you provide the servers where applications, databases, and services run.

What Coolify manages

Coolify calls each deployable item a resource. A resource belongs to a project and environment, then runs on a server connected to Coolify.

ApplicationsDeploy from a Git repository, Dockerfile, Docker Compose file, or prebuilt Docker image.

DatabasesRun supported databases with persistent storage, lifecycle controls, and backup configuration.

One-click servicesLaunch preconfigured software from maintained Docker Compose templates.

Resource operationsManage domains, environment variables, deployments, health checks, logs, storage, and container lifecycle.

A single Coolify instance can manage resources on one or more connected servers.

How Coolify fits into your infrastructure

The Coolify instance coordinates work. Docker runs the resulting resources on the servers you connect.

From configuration to running containers

Most resources follow the same basic model whether they start from source code, a container image, a database, or a one-click template.

Connect a server

Create a resource

Build or pull an image

Start Docker containers

Route traffic when needed

Coolify validates SSH access and the Docker environment on the connected server.
You choose the source, image, database, or service template and configure its settings.
Coolify builds an image when needed or pulls an existing image from a registry.
Docker runs the containers and keeps persistent data in volumes or mounted storage.
For HTTP resources, the proxy on that server routes configured domains to the correct containers and handles HTTPS.

The Coolify instance coordinates this lifecycle from the dashboard and API. Traffic for HTTP resources goes to the proxy on the server running the resource.

Because deployed resources use standard Docker containers, networks, and storage on your servers, they do not depend on a proprietary Coolify runtime. If the Coolify instance becomes unavailable, resources that are already running keep running; you lose Coolify automation and dashboard control until the Coolify instance returns.

Workload data and persistent storage remain on the connected servers. Read How Coolify works for a closer look at the control plane, connected servers, Docker, and proxy traffic.

What stays in your control

Coolify is not a hosting provider for workload servers. Coolify automates deployment work on infrastructure you supply, but you still operate that infrastructure.

The responsibility boundary

The responsibility boundary applies to both self-hosted Coolify and Coolify Cloud. If you self-host, you also operate the Coolify instance.

Coolify coordinates

Server connection validation and Docker setup
Application builds, image pulls, deployments, and lifecycle actions
Resource configuration, environment variables, logs, and health checks
Proxy routing, domains, and HTTPS certificate automation

You remain responsible for

Choosing and paying for the connected servers
Operating system updates, SSH access, firewall rules, and DNS
Application data, database data, and a tested backup and restore strategy
Secrets, access permissions, and the security of exposed workloads
Coolify instance updates, backups, and recovery when you self-host

Read the Security model before placing production workloads on a connected server.

Self-hosted or Coolify Cloud

Coolify has two deployment models. The resource workflow stays the same; the difference is who operates the Coolify control plane.

Choose who runs the Coolify instance

Your applications, databases, and services still run on servers you connect in either model.

Self-hosted

Install the Coolify instance on infrastructure you control.
Choose when to update the Coolify instance and manage its backups and recovery.
Use the instance to manage one or more connected servers.

Coolify Cloud

Use the Coolify instance hosted and maintained by the Coolify team.
Connect your own servers to the managed control plane.
Keep responsibility for the operating system, network, and workloads on those servers.

Compare self-hosted Coolify and Coolify Cloud for a detailed responsibility and pricing breakdown.

Start using Coolify

If you are new to Coolify, choose a control plane model first. Then connect a server and deploy a first resource.

Choose your path

Compare the two starting paths before setting up a Coolify instance.

Start with self-hosted

Install Coolify on infrastructure you control and prepare the first server.

Start with Coolify Cloud

Use the managed control plane and connect your own workload server.

Understand the platform

Learn how the control plane, Docker, builds, networking, and security fit together.

1How Coolify works 2Docker and containers 3Build and deployment model 4Networking in Coolify 5Security model

Deploy a first resource

Verify your setup with one of the beginner deployment guides.

1Deploy your first app 2Deploy your first database 3Deploy your first service