CoolifyCoolify
Your own Heroku, Netlify or Vercel, on one server.
Coolify, the open-source self-hosted PaaS, installed on Ubuntu 24.04. Deploy apps from Git, databases and one-click services with automatic HTTPS on your own server.
Opens the Odinex console with Coolify selected. No licence fee: you pay for the server only.
- Base image
- Ubuntu 24.04 LTS
- Minimum
- 4 GB RAM · 40 GB disk
- Recommended plan
- S3 (2 vCPU · 8 GB RAM · 80 GB NVMe)
- Ready after boot
- 5 to 10 minutes (Coolify is installed on first boot)
- Image slug
coolify
About Coolify
Coolify is an open-source alternative to Heroku, Netlify and Vercel that you run yourself. Connect a Git repository and it builds and deploys your app, provisions databases, issues certificates and keeps everything behind its own reverse proxy.
This image has Docker and Coolify's container images preloaded. On first boot it runs Coolify's official installer unattended and creates your administrator account, so the dashboard is ready when you open it. You pay for the server, not per seat or per deployment.
What’s included
Software installed on the image and the ports it uses.
| Component | Version |
|---|---|
| Ubuntu | 24.04 LTS |
| Coolify | 4.x, the latest release, installed on first boot |
| Coolify proxy (Traefik) | Managed by Coolify |
| Docker Engine and Compose | From Docker's repository |
| Port | Protocol | Used for |
|---|---|---|
| 22 | TCP | SSH (Coolify also manages this server over SSH) |
| 80 | TCP | HTTP for the apps you deploy |
| 443 | TCP | HTTPS for the apps you deploy |
| 8000 | TCP | Coolify dashboard (until you give it a domain) |
| 6001–6002 | TCP | Coolify real-time updates and web terminal |
Who it’s for
- Developers and small teams who want push-to-deploy without a hosted PaaS bill
- Agencies hosting many small client apps on one server
- Anyone moving off Heroku, Render or Vercel to a server they control
Use cases
Git push deployments
Connect GitHub, GitLab or any Git repository; Coolify builds from a Dockerfile, Compose file or Nixpacks and redeploys on push.
Databases
Start PostgreSQL, MySQL, MariaDB, MongoDB or Redis from the dashboard, with scheduled backups to S3-compatible storage.
One-click services
Coolify's own catalogue of services, from analytics to wikis, each with its own domain and HTTPS.
Resources
Coolify needs at least 4 GB of RAM and a 40 GB disk. Every plan includes an NVMe disk and 20 TB of traffic.
Smallest plan
S2
- 2 vCPU (shared)
- 4 GB RAM
- 60 GB NVMe disk
The smallest plan that meets the minimum.
Recommended
S3
- 2 vCPU (shared)
- 8 GB RAM
- 80 GB NVMe disk
A comfortable size for regular use.
Coolify needs at least 4 GB of RAM on Odinex. Every app and database you deploy uses memory and disk on the same server, so S3 (8 GB) leaves room to build and run several apps. You can resize the server later. See current prices.
Getting started after deploy
Find your address and password
The address, user name and password are written to
/root/APP-INFO.txtand printed when you log in over SSH as root. If you created the server with a root password and it meets Coolify's policy (8 or more characters with upper-case, lower-case, a digit and a special character), the app uses that same password, so you can sign in with what the console showed you at creation. If you used an SSH key (or the password does not meet the policy), a strong password is generated for this server and written to/root/APP-INFO.txt.ssh [email protected] cat /root/APP-INFO.txtOpen the dashboard
Open
http://<server-ip>:8000and sign in with the emailadmin@<your-ip-with-dashes>.sslip.ioand your password. Change the email to your own in your profile.Give Coolify a domain
Point an A record (for example
coolify.example.com) at the server, then set it as the instance domain in Coolify under Settings. Coolify obtains the certificate and serves the dashboard over HTTPS.Deploy your first app
Create a project, add a resource from a Git repository or the service catalogue, and give it a domain whose A record points at the server. Coolify handles HTTPS for it on ports 80 and 443.
Close port 8000
Once the dashboard is on its HTTPS domain, remove port 8000 from your firewall so the login page is not served over plain HTTP.
Security notes
- Until you set a domain, the dashboard is served over plain HTTP on port 8000. Set a domain early and then block port 8000 with an Odinex firewall.
- A server without a firewall accepts all inbound traffic. Create an Odinex firewall that allows only SSH (22), HTTP (80), HTTPS (443) and, while you set Coolify up, 8000 and 6001–6002 and apply it to the server. Odinex firewalls filter traffic before it reaches the server, so Docker's own iptables rules cannot bypass them.
- Coolify connects to this server over SSH as root with its own key. Keep key-based root login enabled; turning it off breaks deployments.
- Check in Coolify's settings that registration is turned off, so nobody else can create an account, and invite team members from the dashboard instead.
- Take a snapshot before every upgrade, and turn on daily backups (20% of the server price) for anything you would not want to rebuild by hand.
Coolify questions
Clear answers about location, infrastructure and billing.
Why is the dashboard on HTTP at first?
Does the `nexoran-app-domain` helper work for Coolify?
Can Coolify deploy to other servers?
How do I update Coolify?
Documentation
More from the marketplace
Deploy Coolify in Frankfurt
Your own server with full root access, NVMe storage and 20 TB of traffic, billed by the hour.