Deploy Coolify in one click

FAQ

• Do I need a license or a paid plan to run Coolify?

  No. Coolify is open-source under the Apache License 2.0, and the self-hosted version we deploy includes every feature. There is no limit on how many applications, databases, or servers you run. Coolify Cloud is a separate paid service where the Coolify team hosts the dashboard for you, and it is not part of this deployment. Here you only pay the standard virtual server invoice.

• How do I log in after deployment?

  Open your server's IP address on port 8000, for example http://<VPS-IP>:8000. The first page you see is a registration form, and that is where you create your admin account. Do it as soon as the server is ready, because until that account exists, anyone who opens the page can claim the instance. Then add your domain in Settings – the dashboard starts answering on that domain over https:// with a real certificate, and once that works, you can safely close port 8000 to the outside world.

• How do I get a valid SSL certificate?

  Create an A record for your domain pointing to the server's IP, then open Settings and fill in Instance's Domain using an https:// address. Coolify asks Let's Encrypt for a certificate, installs it, and renews it on its own – certificates last 90 days and renewal needs no attention. Keep port 80 open, because that is how Let's Encrypt confirms the domain is really yours. If that check fails, the proxy serves its own self-signed certificate and the browser shows a warning until DNS or the firewall is fixed.

• Can I move an existing Coolify installation to this server?

  Yes. Coolify keeps its settings in its own PostgreSQL database, and that database is covered by the same scheduled backup feature you use for your own databases. Everything else sits in /data/coolify on the server. Back up both on the old server, restore them here, and run the same Coolify version on both sides during the move. Nothing is tied to a vendor cloud, so your configuration always stays on hardware you control.

• How are updates handled?

  Coolify updates itself, and you choose how. Automatic updates check for new releases and install them on a schedule. Semi-automatic puts an Upgrade button in the top navigation bar when a release is out, and nothing happens until you click it. Manual means running the official install script over SSH, where you can also pin an exact version. The documentation recommends switching automatic updates off on production instances and backing up before any upgrade.

• What if I outgrow this configuration?

  Add CPU, RAM, or storage to the VPS, with no reinstall needed. After that, Coolify grows by adding servers rather than one huge one – connect another server over SSH and deploy to it from the same dashboard. You can also mark a server as a build server, so building images stops slowing down the applications that are already running.

• Should I run my applications on the same server as Coolify?

  It works, and on the smaller plans it is the usual setup. For production the documentation suggests a split – one server for Coolify, one or more for the applications and databases you deploy. Building images is the heavy part, and a long build can slow down everything else on the same server, including the dashboard.

• Does Coolify keep the server secure and up to date?

  Not on its own. Coolify takes care of deployments, routing, and certificates, while the operating system stays your responsibility. It does help you see the work – the Security tab lists the package updates available for your server and can send you a weekly reminder, but nothing is installed until you press Update. Firewall rules and SSH access are yours to set.