> ## Documentation Index > Fetch the complete documentation index at: https://repocloud.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Coolify > Install Coolify, the self-hosted alternative to Heroku and Netlify, on your own VPS with the DevOps AI Agent: Git deploys and one-click templates ## Coolify on RepoCloud Coolify is an open-source, self-hostable alternative to Heroku, Vercel, Netlify and Railway. On RepoCloud you install it on your own VPS with [AI Deploy](https://repocloud.io/docs/deployment/ai-deploy.md): a plain Ubuntu 24.04 server is created and the [DevOps AI Agent](https://repocloud.io/docs/ai-agents/devops-ai-agent.md) installs Coolify on it while you follow the chat. The server has root access, SSH, a browser-based serial console, and all the management tools in the RepoCloud dashboard. > **Git Deploys** > > Deploy from GitHub, GitLab, Bitbucket, or Gitea. Once the repository's webhook or a Git App is connected, a push starts a deployment. Builds use Nixpacks, Railpack, a Dockerfile, static files, or Docker Compose > **Hundreds of Templates** > > Hundreds of one-click templates, such as WordPress, n8n, Grafana, Plausible, MinIO, and Ghost > **Databases** > > Create PostgreSQL, MySQL, MariaDB, MongoDB, Redis, and more as resources, with scheduled backups for every engine listed here except Redis > **Certificates and Previews** > > Coolify's reverse proxy requests Let's Encrypt certificates for the domains you add, pull requests can get their own preview deployments, and a wildcard domain can be set for generated addresses > **Full Root Access** > > SSH into your server, use the browser-based serial console, and manage everything at the OS level > **S3 Backups** > > Scheduled database backups can be copied to S3-compatible storage and restored from the dashboard with Import Backup (not for ClickHouse or Redis) ## Installing Coolify with AI Deploy RepoCloud has no ready-made Coolify template. Coolify is installed on a blank Ubuntu server by the DevOps AI Agent, from Coolify's public repository. ### Prerequisites - A RepoCloud account with a balance above $3 - A server of Tier 3 or larger. Coolify's documentation gives 2 CPU cores, 2 GB of RAM and 10 GB of disk space as its minimum; Tier 3 has 2 vCPU, 2 GB of RAM and a 40 GB SSD, while Tier 2 has one vCPU. Heavier workloads on the same server need a larger tier ### Steps **1. Open AI Deploy** Go to [repocloud.io/ai-deploy](https://repocloud.io/ai-deploy). **2. Paste the Repository** Enter Coolify's repository, `https://github.com/coollabsio/coolify`, and a project name for your own reference. **3. Choose a Tier** Select Tier 3 or a larger tier. A server can later move to a tier whose disk is the same size or larger, and a resize can be refused. **4. Add Instructions (Optional)** [Custom instructions](https://repocloud.io/docs/ai-agents/custom-instructions.md) tell the agent what you expect. Examples: "Install Coolify with its official install script and create the administrator account during the installation." or "When you are done, tell me the address of the dashboard and the ports Coolify needs open." **5. Deploy and Follow the Chat** Click **Deploy**. A dedicated IPv4 address is included with every VPS at no extra charge. The chat opens once the server is ready, and AI-assisted deployment typically takes 5–15 minutes. The agent reports the dashboard's address and any logins it created. > [!NOTE] > > The agent is an AI and can make mistakes: read what it reports, steer it in the chat when something is off, and take a snapshot before a risky change. [Safety and Control](https://repocloud.io/docs/ai-agents/safety-and-control.md) explains how. ## First-Time Setup **1. Open the Dashboard** Open the address the agent reported. Coolify's documentation lists the ports of a Coolify server: 8000 for the dashboard by IP address (`http://:8000`), 6001 for real-time updates and 6002 for the web terminal when you use the IP address, 22 for SSH, and 80 and 443 for HTTP and HTTPS traffic through Coolify's proxy. **2. Sign In** Use the login the agent reported. Coolify's documentation describes pre-creating the root account during the installation so that the registration page is never exposed, which you can ask the agent to do. **3. Check Your Server** A standard Coolify installation has a server named `localhost`, the server Coolify runs on. It cannot be removed. **4. Create Your First Project** Coolify organizes work into projects. Create one (e.g., "My First Project") to group your applications, databases, and services. > [!TIP] > > To open the dashboard on your own domain, set the **URL** under **Settings > General** in Coolify, as Coolify's documentation describes, and point the domain's DNS record at the server. ## Deploying Applications ### From a Git Repository **1. Create a New Resource** Open a project and its environment, select **+ New**, then choose Application. **2. Choose a Source** Choose a public repository, a deploy key, or a Git App (GitHub App or GitLab App). **3. Select Repository and Branch** Pick the repository and branch you want to deploy. The **Deploy on push (webhooks)** setting under Advanced > Deployment redeploys on every push; it works once the repository's webhook or a Git App is connected. **4. Configure the Build** Choose the build method: **Nixpacks**, **Railpack**, **Static**, **Dockerfile**, or **Docker Compose**. Set environment variables, build arguments, and resource limits as needed. **5. Add a Domain** Open the application's **Domains** settings, add the domain with `https://` in front, and point its DNS record at the server. With no wildcard domain set, Coolify generates an `sslip.io` address from the server's IP. **6. Deploy** Click **Deploy**. Watch the **Deployment Logs**. Once the build completes and the domain's DNS record points at the server, your app answers on the domain. ### From a Template Coolify ships with hundreds of one-click service templates: **1. Browse Templates** Open a project and environment, select **Create New Resource**, then choose a one-click Service. **2. Select a Template** Choose a template (e.g., WordPress, Plausible Analytics, n8n, Uptime Kuma). Each template starts from its own default configuration with generated initial values. **3. Configure and Deploy** Review **Configuration > General**, **Environment Variables**, and **Persistent Storages**, fill every required variable, and press **Deploy**. Popular templates include: - **CMS**: WordPress, Ghost, Strapi, Directus - **Analytics**: Plausible, Umami, GoatCounter - **Automation**: n8n, Activepieces - **Monitoring**: Uptime Kuma, Grafana, Beszel - **Storage**: MinIO, Nextcloud, Seafile - **Development**: Gitea, Code Server, Coder ## Managing Databases Coolify can create, configure, back up, and restore databases as resources: - **PostgreSQL** — connection strings from the database page; pgAdmin is a separate template you deploy next to it - **MySQL / MariaDB** — standalone or as part of a service stack - **MongoDB** — a standalone container - **Redis** — caches, queues, streams, and key-value data Depending on the engine, Coolify provides: - Connection strings and credentials - Scheduled backups for PostgreSQL, MySQL, MariaDB, MongoDB, ClickHouse, and SQLite, optionally copied to S3-compatible storage added under **S3 Storage** - Restore with **Import Backup** (not for ClickHouse or Redis) - CPU and memory metrics, once metrics are enabled on the server ## Custom Domains and SSL Coolify's own proxy requests certificates for the domains you add inside Coolify. This is separate from the RepoCloud Custom Domain section. **For the Coolify dashboard itself:** set the **URL** under **Settings > General** in Coolify, which is Coolify's own feature for the dashboard's domain. **For applications deployed inside Coolify:** 1. Open the application's **Domains** settings in the Coolify dashboard 2. Add your domain with `https://` in front (e.g., `https://app.yourdomain.com`) 3. Create a DNS **A record** pointing to your VPS IPv4 address 4. Coolify's proxy then requests a Let's Encrypt certificate. This needs the DNS record in place and port 80 reachable > [!WARNING] > > The **Custom Domain** section of the RepoCloud manage page, on a server that has one (see [Custom Domains](https://repocloud.io/docs/manage/custom-domains.md)), puts a domain on the server's default web address. It does not send a domain to an application inside Coolify: use Coolify's own Domains settings for that. ## Managing the Server Your server has its own manage page in the RepoCloud dashboard: its address and SSH command, power controls, the browser console, SSH keys, resizing, snapshots, usage charts and the option to delete it. [Managing VPS Apps](https://repocloud.io/docs/manage/vps-apps.md) describes each part, and **Resume Chat** on the same page reopens the chat with the DevOps AI Agent. Take a snapshot before you upgrade Coolify or make other risky changes, so you can roll back. ## Upgrading Coolify Coolify manages its own updates. When a new version is available, an **Update available** badge appears beside the version number at the top left of the Coolify sidebar. **1. Check for Updates** Look for the **Update available** badge beside the version number, or open **Settings > Updates** and press **Check now**. **2. Create a Snapshot** Before upgrading, create a snapshot from the RepoCloud manage page so you can roll back if something goes wrong. Coolify also advises backing up its own instance first. **3. Run the Upgrade** Press **Upgrade Now** with no deployment running. The dashboard is unavailable briefly (usually under a minute) while Coolify restarts. The update changes Coolify only, not the applications, databases, and services it manages. **4. Verify** The version number at the top left of the sidebar shows the new version. Check that your applications are still running. > [!TIP] > > To upgrade over SSH, run Coolify's `upgrade.sh` with the version you want, without a leading `v`: `curl -fsSL https://cdn.coollabs.io/coolify/upgrade.sh | bash -s ` (for example `4.3.23`). Never omit the version, and never run `install.sh` to update: on an existing instance it resets ownership and permissions under `/data/coolify`, including managed service data. ## Troubleshooting > **Dashboard not loading after the agent finished** > > Start with [Troubleshooting the Chat](https://repocloud.io/docs/ai-agents/troubleshooting.md), which covers an address that does not open, and tell the agent what you see after **Resume Chat** on the manage page. You can also check the server yourself: open the browser console from the RepoCloud manage page or connect over SSH, and look at `docker ps` for the running Coolify containers. If that does not fix it, open a [support ticket](https://repocloud.io/docs/manage/support.md). > **The deployment failed or the agent seems stuck** > > [Troubleshooting the Chat](https://repocloud.io/docs/ai-agents/troubleshooting.md) covers a deployment that failed, an agent that seems stuck or asks for something, a server that does not answer, and a missing **Resume Chat** button. > **Let's Encrypt certificate not issuing** > > Ensure your DNS A record points to the correct IPv4 address (shown in the manage page Access section). The certificate request uses port 80, so the proxy container must be running and port 80 must not be blocked. Check the proxy's logs: in the Coolify sidebar open **Servers**, your server, **Proxy**, then **Logs**. > **Cannot SSH into the server** > > Verify you are using the correct IP address and that your SSH key file has `chmod 600` permissions. If SSH hangs or is refused, use the browser console from the RepoCloud manage page to check that the SSH service is running and that no firewall is blocking port 22. > **Applications fail to build** > > Read the **Deployment Logs** in the Coolify dashboard for specific errors. Common causes: missing Dockerfile or unsupported Node.js/Python version for Nixpacks. Ensure your repository has a supported build configuration. You can switch the build method under **General > Build pipeline** (Build strategy): Nixpacks, Railpack, Static, Dockerfile, or Docker Compose. ## Use Cases Coolify is ideal for: - **Indie developers and startups** who want Heroku-like convenience without vendor lock-in or per-app pricing - **Agencies** deploying multiple client sites from Git with certificates for the domains they add in Coolify and preview environments - **Teams** that need databases next to their applications, with scheduled backups and CPU and memory metrics - **Self-hosters** migrating from other PaaS providers who want to keep their deployment workflow ## Next Steps > **[Install Coolify](https://repocloud.io/docs/deployment/ai-deploy.md)** > > Start an AI Deploy with Coolify's repository > **[Coolify Documentation](https://coolify.io/docs)** > > Read the official Coolify documentation for advanced features > **[Dokploy](https://repocloud.io/docs/deployment/dokploy.md)** > > Explore Dokploy as an alternative Docker-focused deployment platform > **[VPS Apps Overview](https://repocloud.io/docs/deployment/vps-apps.md)** > > Learn about VPS Apps and the RepoCloud manage page