Deploy to Coolify
Open-source self-hosted PaaS. Similar shape to Dokploy, larger ecosystem.
Self-hosting with a big library of one-click services alongside your app, and multi-server support once one box is not enough.
Minimal setups — it carries more moving parts than a plain Docker Compose file.
Setup
- 1
Install
Same shape as Dokploy: one script on a clean VPS, then everything else through the panel.
curl -fsSL https://cdn.coollabs.io/coolify/install.sh | bash - 2
Add the application
Choose the Dockerfile build pack and set the base directory to the API. Coolify reads the Dockerfile as-is, so the image Grit generates needs no changes.
Build pack: DockerfileBase directory: /apps/apiPorts exposed: 8080 - 3
Attach databases and set the health check
Add Postgres and Redis as resources in the same project, then copy their internal connection strings into the app. Set the health check path to `/api/health` so a failed boot is caught rather than served.
What catches people out
Internal connection strings use the container name, not localhost. Using localhost is the single most common Coolify support question.
Coolify keeps every build image by default and will fill the disk. Set a cleanup schedule on day one.
Platform dashboards and CLI flags change faster than these docs. For anything that looks different from what is written here, Coolify's own documentation is the authority: coolify.io/docs/