Coolify

Coolify is a self-hostable platform for deploying applications, databases and services to customer-controlled servers. It automates deployment and related operations over SSH. The optional Coolify Cloud service hosts the management interface; application servers and their costs remain the customer’s responsibility.

Key features

• Application builds. Source builds, Dockerfiles, Docker Compose and prebuilt images support different deployment workflows.
• Git integration. Repository connections and pull-request deployments support review and release processes.
• Data services. One-click database deployments and backup integrations help organise application resources.
• Operations. Certificates, environment variables, scheduled tasks, monitoring and notifications are available through the platform.

Who it is for

Developers, founders and small teams that want a platform-style deployment workflow while retaining their own infrastructure. It suits teams willing to take responsibility for server capacity, security and recovery.

Pricing at a glance

The self-hosted edition is free and open source. Coolify Cloud is a paid subscription for the hosted control plane, with server-based allowances. Infrastructure and external services are paid separately in either model.

Pricing model checked on 15 October 2026; confirm current terms on the official product page. No currency conversion or fixed price estimate is used in this profile.

Things to consider

• Deploying a database does not remove responsibility for its upgrades and recovery.
• Self-hosting the control plane introduces another component to patch and back up.
• Plan build resources, disk space and secrets access before adding production services.

Before connecting a production server, make an inventory of its applications, runtime versions, storage and external services. Decide who will maintain the operating system and who can access the panel. Test the software on a compatible non-production server first, and confirm that a failed deployment or panel outage will not prevent you from restoring the applications.

Getting started

1. Read the official documentation and plan information, then write down the features and costs your project needs.
2. Prepare a compatible test server and follow the official installation or connection documentation.
3. Configure restricted access, domain settings and certificates; keep secrets out of source repositories.
4. Test deployment, backups and restoration with representative data before changing production DNS.
5. Review usage and recurring charges after the pilot, and document a migration or cancellation path.