CoolifyCoolify is the self-hosted platform you deploy your apps with. CubePath is the infrastructure it runs on. Pick a VPS, choose Coolify from our 1-click marketplace, and skip the manual install.
CubePath is a proud Coolify sponsor.
Coolify is an independent open-source project. CubePath sponsors it and provides infrastructure to run it on. coolify.io
What the stack looks like
One machine, root access, nothing hidden underneath.
Coolify handles how your applications get deployed. CubePath handles what they run on. Neither one locks you into the other.
Coolify is available directly in the CubePath marketplace, alongside every other 1-click app. You pick the server, we hand it over with Coolify running.
Installation details and configuration are documented by the Coolify project. Coolify documentation
A CubePath VPS is a plain Linux server with root access, not a locked-down runtime. That is the point: whatever you put on it, from a Coolify instance to a database you tune by hand, behaves the way it would on hardware you own.
Most of our developer customers run more than one thing per server. Coolify is usually the front door, and the rest follows naturally.
Full root access · Hourly billing
Coolify is one of the 1-click applications you can deploy from the CubePath marketplace. Here are a few that developers pair with it.
Running Coolify on your own VPS is a deliberate choice about where the boundary sits between your applications and the platform underneath them. Here is what actually changes.
On a managed platform, the deployment layer and the machine belong to the same vendor, and you interact with both through their console. Self-hosting Coolify splits those apart: the deployment layer is open-source software you run, and the server is infrastructure you rent with root access. If you want to read the logs on disk, change a kernel parameter or run something Coolify does not manage, nothing stops you.
Build pipelines and application runtimes have very different appetites. Sizing your own server means matching CPU, memory and disk to what your workloads actually do, rather than buying the next plan up because one dimension ran out. On CubePath you can start on a small General Purpose plan and move to a larger one, or to bare metal, as the load grows.
Latency and data location are architectural decisions. Choosing the region yourself lets you put the server close to your users or your other systems: Barcelona for Europe, Houston or Miami for the Americas. That choice stays yours as the project moves, and the price does not change between locations.
Projects rarely stay one container. A self-hosted setup grows by adding what you need next, a database, a worker, an object store, on infrastructure that already belongs to you. You are not waiting for a platform to support a service, and you are not rewriting your deployment model when you outgrow a plan.
When something breaks, it helps to have the whole picture: the container, the host, the network path. With Coolify on a CubePath VPS you can inspect all three yourself, and our support team can look at the infrastructure side with you rather than pointing at an abstraction boundary.
Self-hosting is not the right call for every team. It is the right call when control over the deployment layer is worth running it yourself, and Coolify makes that trade considerably lighter than it used to be.
The questions developers ask before moving Coolify onto their own server.
Coolify is an open-source, self-hostable platform for deploying and managing applications, databases and services. You run it on your own server, connect a Git provider, and it handles builds, deployments and service lifecycle from a web dashboard. It is developed independently by the Coolify project; CubePath is a sponsor and an infrastructure provider, not the maintainer.
Yes. Coolify is designed to be self-hosted on a server you control, and a VPS is the most common way to do that. On CubePath you deploy a Cloud VPS with root access and Coolify installs on it directly, either from our 1-click template or by following Coolify's own install instructions.
Choose a General Purpose VPS plan and a location, select Coolify from the 1-click marketplace instead of a plain OS image, and deploy. The server boots with Coolify installed and reachable on port 8000, where you create your admin account and connect your Git provider.
CubePath sponsors the Coolify project and maintains a 1-click Coolify template in our marketplace, so it installs without manual setup. Our support covers the infrastructure: the server, the network and the deployment. Questions about Coolify itself are best answered by the Coolify documentation and community.
That depends on what you deploy with it, since builds and running containers are what consume resources, not the dashboard. Our Coolify template recommends gp.starter (4 vCPU, 8 GB RAM, 100 GB NVMe) as a comfortable starting point for a real project, and you can move to a larger plan later. For the project's own requirements, check the Coolify documentation.
Yes. Coolify is one of the applications in our 1-click marketplace, which also includes Dokploy, EasyPanel, Portainer, Supabase, n8n, Grafana, MinIO, Nextcloud, GitLab and more. You can also install anything yourself, since every VPS comes with full root access.
A VPS gives you a dedicated Linux environment with root access at a predictable hourly price, which is exactly what Coolify expects to run on. You choose the resources, you choose the region, and the deployment layer stays software you control rather than a service you rent.
By the hour, with the monthly figure being the hourly rate multiplied by 730. A server is billed for as long as it exists, including while it is powered off, so destroying it is what stops the charges. A dedicated IPv4 address is a $1.50/month add-on. See the VPS pricing page for current plans.
Launch your infrastructure on CubePath and start building.
