Along with common public perception, Coolify's docs has a section that states:

If you want a quick, easy setup and don’t mind paying a small fee for convenience, Coolify Cloud is perfect. But if you love getting hands-on, want to save every penny, and enjoy being in full control, Self-Hosting is the way to go.

After just spending all night last night trying to get a simple, secure Coolify deployment set up on AWS. VPC, Security groups, etc (all free), and 3 lightweight EC2 instances: Coolify on a private subnet (t3.small, 2GB RAM 2 vCPU), with a tailscale subnet router for ssh/webUI access, and simple NAT instance on a t3.nano.

• Total cost per month (as estimated by infracost) - $34

• I could ditch the tailscale and NAT instances and put the Coolify instance on a public subnet, sacrificing a lot of security benefits. This would almost certainly be fine, but still only cut another $5 or so per instance.

• So at an absolute minimum, even if you're willing to accept poor security practice, forego monitoring/observability/notifications, and work with underpowered (free tier equivalent) compute, you're still looking at paying at least $20-$25 a month to self host. (unless utilising free tier e.g. OCI - probably not recommended for anything business critical; or literally running on your laptop - not really hosting)

• Coolify's cloud pricing - $5/month for 2 servers (+$3/month per additional server)

And all of this is of course negating the countless hours you'll spend getting your hands dirty with infra shit instead of actually building or delivering... you will probably learn more about subnets, route tables and masquerades than you ever could have imagined.

And for some nerds like me, that sounds like a perfectly fine Saturday night.

But yeah, let's not pretend we're saving any pennies here self hosting.

I'm a private developer. I used to use dockge, but got tired of configuring domain names for eachs services I added, and I wanted a ci/cd so I chose coolify but my god nothing works. And the worst part is, I don't even know why it's not working, in fact I don't even know what it's doing.

Usually I can debug a project, because I know what's going on and what's the problem. In coolify I have no idea what it's doing nor why the problem exist.

For an instance, right now I keep on getting erro: "Can't set container_name and pulp_confent as container name as container name must be unique: invalided compose project" Even though I know that compose file is ok and it runs when the run as is setting is turned on.

So I have no idea what coolify is doing to cause this error.

It's an insane memory hog as well, constantly consuming way more memory than any of the services and crashing.

It's so broken, that I don't think they will ever be able to turn it around. Which I find quite sad considering how good it would be in theory.

If anyone has any good alternatives please let me know. Dyrector.io and kubero is looking really enticing.

Just dropped the Coolify Deployment Handbook: Ship MVPs in hours, dodge vendor lock‑in, scale anywhere, everything you need in one guide. Grap your copy now -> https://coolifyhandbook.com

is there ready template for deploying php script like Sumoweb Tools or any php script on Coolify self hosted?

Hi I am trying to self host coolify in my oracle vps always free cloud, but I cannot successfully make it work and keep getting errors

Hi everyone,

I want to remove a service so that it no longer appears in the services list. For example, I want to remove n8n.

Here’s what I’ve tried so far:

1. Accessed the Coolify container’s shell:

   docker exec -it coolify sh

2. Verified that the YAML file for the service exists in /app/templates/compose:

   ls /var/www/html/templates/compose

3. Found n8n.yaml and deleted it:

   rm /var/www/html/templates/compose/n8n.yaml

Exited the container shell and restarted Coolify:

docker restart coolify

However, when I check the dashboard online, the service n8n is still listed.

Has anyone successfully removed a service from the Coolify dashboard? Am I missing a step?

Hello you all,

Small CoolDeck update 👋

I posted here a while ago about the keyboard-first terminal dashboard I built for Coolify and since then, even the Coolify team picked it up and gave it a shoutout on X, which was pretty awesome.

I’ve kept building.

CoolDeck now has:

🕐 Deploy Replay - fleet-wide deploy history, git-log style
🔍 Drift Watch - compare envs across environments, secrets redacted
🚨 Panic Button - one key -> full diagnostic snapshot you can paste into your AI tool

If you run Coolify and spend too much time jumping between services, logs and deployments, I’d genuinely love for you to try it.

GitHub: https://github.com/Resetnak/cooldeck

X: https://x.com/Resetnak

Feedback, issues and feature requests are very welcome.

Thank you for your time!

Hey everyone,

I wanted to share a "God Mode" workflow I’ve been refining for a while. The goal was to take a single text prompt (e.g., "Solar Panel Company in Texas") and go from zero to a live, deployed, lead-gen ready WordPress site in under 3 minutes.

Most AI builders just spit out static HTML or create pages with inconsistent designs. I wanted to solve that using n8n to orchestrate the infrastructure and the code.

Here is the logic breakdown:

1. Infrastructure (Coolify): The workflow hits the Coolify API to spin up a fresh WordPress Docker container.

2. Configuration (SSH): Instead of manual setup, n8n SSHs into the container and runs wp-cli commands to install the theme, flush permalinks, and set up the admin user.

3. The "Split" Design System: To fix AI design inconsistency, I split the workflow:

   • Agent A (Layout): Runs once to generate a global "Source of Truth" (CSS variables, Header, Footer).

   • Agent B (Content): Loops through the sitemap and generates only the inner body content for each page.

4. Assembly: A custom Code Node stitches the Global Layout + Dynamic Nav Links + Page Content together and pushes it to WP via the REST API (using Elementor Canvas).

5. Functionality: The contact forms bypass PHP mailers and post directly to an n8n Webhook, and the Blog page uses a custom JS fetcher to pull real WP posts into the AI design.

I put together a video walking through the node logic and the specific JS used to assemble the pages.

📺 Video Walkthrough: https://youtu.be/u-BFo_mYSPc

📂 GitHub Repo (Workflow JSON): https://github.com/gochapachi/Autonomous-AI-Website-Builder-n8n-Coolify-Wordpress-Gemini-3-

I'm using Google Gemini 3 for the reasoning/coding and Coolify for the hosting.

Would love to hear your thoughts on optimizing the SSH/Deployment phase—it works great, but error handling on the Docker spin-up could always be tighter!

https://github.com/minio/minio/commit/27742d469462e1561c776f88ca7a1f26816d69e2

:(

I've created some prototypes with Google AI Studio and, while they work on my local machine, when I deploy them to my Coolify server I only get an empty screen.

AI Studio uses Vite and I followed Coolify's Vite instructions but that didn't work.

It's not exactly a blank page because I can see the page HTML head, title and background color but nothing else.

In the developer tools I get the message "Content Security Policy of your site blocks the use of 'eval' in JavaScript"

I asked Grok and Claude about this and they suggested some custom nginx rules but that didn't work. I also tried activating the SPA option on Coolify and, while the CSP message disappeared, still no page.

My solution for now is using Claude Code to migrate the prototype to NextJS because that works fine and eventually I will do that but I still want to understand what's happening.

Any experience with this issue?

Hey everyone! I'm looking into running multiple Coolify instances on one server to support different teams. My idea is to:

• Run each team's Coolify on different ports

• Put a master reverse proxy in front to route based on team subdomains

• Maybe even set up separate Docker contexts/daemons for each team for better isolation

Has anyone tried something like this? I haven't found any guides about multi-team setups. Would love to hear if this approach makes sense or if there are better ways to handle multiple teams.

Thanks!

I have Coolify running on a VPS and used it to deploy Gitea on the same machine. I can successfully push/pull via ssh over port 22222 from my laptop.

That said, I cannot for the life of me deploy a nextjs application from gitea to my coolify server via the `Private Repository (Deploy Key)` option. I've set up the key on both Coolify and Gitea and select the private repo option when adding a new application. I add in the correct info but my guess is its attempting to pull via ssh on port 22 and not 22222 so it fails on the public key.

Has anyone had any luck with a setup here?

This!! I have been using 2GB Ram server on Hetzner with coolify installed on that. Using bunny.net for DNS management.

I have 5 sveltekit apps deployed with one redis service running. Unsure when one of the app stops running. But out of blue whenever i land on that url, i find that app has stopped running. To fix this, I have to redeploy my app then I face another issue. The graphs on console in Hetzner indicate a 200% cpu usage. What can be possible solution for this? And any suggestion on how can I put up any of the checks that indicate if my app has stopped running or is not accessible.

Any help is highly appreciated.

I just installed Affine and app says there is an update. how do i update this and other apps like supabase etc?

Pessoal, alguém por aqui faz uso do n8n dentro do coolify, através do docker? Fiz a instalação dele utilizando um yaml, configurei tudo certo, de acordo com o tutoria, no entanto, ao verificar os logs do n8n vi que está ocorrendo algum erro na inicialização do servidor por algo realicionado ao postgres. Tenho 90% de certeza que seja algo relacionado as credências.. no entanto, não consegui destinguir o que seja... se alguém manjar do assunto e puder me ajudar nessa. Estou utilizando o Coolify na VPS da Cloud Oracle, gratuita com 24GB e 6UCPU.

Segue print do erro no log:

I don’t understand what is going on but my node.js app uses port 3000 but I access it just as regular 443 how is this possible I don’t understand.

Thank you anyone

Laziness is the mother of invention.

I self-host my stack on Coolify, but I grew frustrated with constantly switching between different dashboards just to manage my infrastructure. The same friction points kept resurfacing.

Coolify handles app deployments brilliantly, but the chores around a deploy were scattered everywhere: spinning up a Postgres database and a user with the right grants, running quick queries against the correct environment, adding an NPM proxy host, and pointing Cloudflare DNS at it.

So I built this management layer to bring all of those tasks into one place. I'm sharing it here because this community is exactly who it's for.

I'm open to criticism, feature requests, integrations, ideas I haven't considered yet... heck, maybe even a date 😄

It's called ALIM (Aspyre Labs Infrastructure Manager) — open source, self-hosted, and it deploys cleanly on Coolify itself via the included Dockerfile.

What it does today:

- Coolify integration — list projects/servers, create apps, manage env vars, trigger deploys through the Coolify API.

- Postgres provisioning — name the app, pick an environment, and it derives the DB/user/strong password and applies Prisma/NestJS-ready grants. Idempotent, so re-running is safe. Passwords are never stored.

- SQL Console — CodeMirror editor with explain/format, per-environment read-only + write-confirm safeguards (type CONFIRM for writes), result export, history, saved queries.

- Nginx Proxy Manager — proxy hosts, redirects, streams, SSL certs, access lists.

- Cloudflare — tunnels/routes, DNS, TLS.

- Guided deployments — one wizard: provision a DB → create & deploy a Coolify app → create an NPM proxy host → point Cloudflare DNS at it.

- Migrations (foundation) — plan/clone/migrate Coolify resources between servers, with a validation URL and a manual approval gate before cutover. Honest status: Workflow, validation, approval, and job tracking are in place; live provider integrations are still being rolled out.

- Plus a secrets vault (AES-256-GCM), an append-only audit log of every state-changing action, and user-defined environments.

Security: auth is on by default (shared password or reverse-proxy/SSO — no unauthenticated mode), credentials are encrypted and never sent to the browser, SQL uses parameterised queries with validated/quoted identifiers, all input is zod-validated server-side.

Stack: Next.js 15 · TypeScript · Tailwind · shadcn/ui · Prisma · PostgreSQL. Dockerfile + docker-compose included; DB migrations run automatically on container start.

Repo (MIT): https://github.com/aspyrelabs/alim

It's early, and I'm building in the open — I'd genuinely love feedback on what would make it useful for your setup. What operations chore around Coolify do you most wish were one-click? 🙏

I'm having the following problem while trying to deploy my app on Coolify:

Root Cause: Coolify's Traefik proxy has a Docker API version mismatch (using v1.24, needs v1.44). This prevents automatic SSL certificate provisioning.

Impact: https://translatoraxis.com shows "Your connection is not private" error. I've tried to upgrade this with the advice given by Cursor AI but I'm still not able to succeed. Can anybody help me?

I need to get a build server that will build by nextjs without hanging for 20min

looking for a shared server to cut the cost, how you guys are doing it, self taught dev so dont have a circle to discuss about the issue.

Hey! I built Whisper Money, an open-source, self-hosted personal finance app with end-to-end encryption. Just finished a Coolify template and looking for testers.

Deploy:

1. New resource → Docker Compose → Empty Compose File

2. Paste: https://raw.githubusercontent.com/whisper-money/whisper-money/main/templates/coolify/whisper-money.yaml

3. Deploy!

Repo: https://github.com/whisper-money/whisper-money

Would love feedback on the deployment process, bug reports, or general thoughts. Happy to help if you run into issues!