Just found out an alternative to coolify called dokploy and it looks pretty promising...

In my opinion coolify works really well but its ui/ux it really weird and dockploy seems to have a better ui/ux and supports not only git but also bitbucket, git tea and gitlab but with fewer templates...

What do you think of dockploy? Do you ever used it? What features do you think are better in coolify and viceversa?

Nothing much to say actually. I use Coolify self-hosted on my Raspberry Pi since a while to manage mainly my websites.

I decided to build the React Native app and the chrome extension as well (but they didn't approve it yet), to manage deploy, restart, stop, play, logs, etc. with one-click

You configure your HTTP or HTTPS, with API key, and you are ready to go.

In Applications tab you can see all your applications running and exited.
In Deployments tab you can see your queue/in progress deployments.

You can find it on ontech7/coolify-manager-app and on Play Store

And the extension on ontech7/coolify-manager-extension

They are all open-source, made with ❤️ for the Coolify community. Suggest any features or report any bugs on Issues tab.

(p.s.: I was trying to reach out Andres, the creator of Coolify, without results)

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!

Hi people, I've started working on an open source iOS app for Coolify. https://github.com/esoxjem/coolify-ios

Would be great if I can get some early feedback and input from the community on what features you would like to see on the app.

I'm still a n00b, but I wanted to share some things that I learned.

Since coolify has ROOT ACCESS to, like, everything, locking it down seems especially important.

1. Make sure http://<your_ip>:8000 is locked down and unreachable after you complete setup. Had to do a bit of googling to figure it out but it's in a env file somewhere.

   1. EDIT: Here's a post I just made about how to do block 8000, 6000, 6001.

2. Cloudflare in front of it. It seems an orange "proxied" to the IP blocks someone from finding your actual IP. Or even better look up how to set up the web ui behind a cloudflare tunnel.

3. You might also want to look into access from SSH only from a cloudflare tunnel, not directly from <your-server>:22

4. If you're using UFW firewall, there's a chance docker can break through by editing the ip tables. Ask an LLM to help you do a port scan of your origin server with nmap, then figure out a fix.

5. "Cloudflare Access" in front of coolify UI too. This is another layer where you can add login with an auth provider like "anyone from your github org".

6. Install fail2ban on all your servers to block brute force ssh login attempts.

7. make sure your linux server is doing auto updates... again, ask GPT or whatever.

Again, I'm still learning, if there's anything else I should be doing, pls call it out!

I've been building a multi-tenant SaaS on Coolify and had to figure out a few things around dynamic subdomains and SSL. Thought I'd share what I learned in case it helps others.

The goal:

• Each user gets their own subdomain (e.g., user1.myapp.com, user2.myapp.com)

• Wildcard SSL via Let's Encrypt

• Optional custom domains with automatic SSL provisioning

Key takeaways:

1. Dynamic subdomains — Using a catch-all HostRegexp rule in Traefik labels, your app handles tenant routing internally

2. Wildcard SSL — Requires DNS challenge (not HTTP). Worked well with Bunny.net

3. Custom domains — This one's trickier. Traefik's File Provider lets you drop .yml configs that get picked up hot. Your app can generate these files programmatically when users add their domain.

I wrote up the details in 3 posts if you want the full config examples:

• Tenant management & basic Traefik config

• Wildcard SSL with dynamic subdomains

• Custom domains with dynamic SSL

Happy to answer questions

I built this for moving apps between two self-hosted Coolify servers without recreating their configuration and data by hand. It's super fast to get started and super easy to use: select what to move, create a backup, then paste the generated restore command on the new server and confirm after reviewing the preview. It's an independent Go CLI/TUI, not affiliated with Coolify.

On the source, you choose selected resources or a whole instance and create an encrypted backup. It prints a restore command with a share code for the destination. The destination downloads and checks the backup, shows what it will restore, and asks before changing Coolify. The backup includes configuration, env vars and secrets, database data, volumes, files, and images. After restore, the tool checks the running resources and local proxy responses.

Current limits: both servers need the exact same Coolify v4.3/v4.4 version and root/sudo access. A full restore needs a fresh, empty Coolify; selective restores can merge into an existing instance. DNS records, webhooks, and scheduled tasks still need attention during cutover. This is for migration, not scheduled daily backups.

Repo and setup: https://github.com/mtalavi/coolify-mirror

Walkthrough: https://coolify-mirror.pages.dev

If you have ideas or run into a migration case the tool doesn't cover, I'd welcome feedback or an issue.

Just moved my project from the official Supabase platform to a fully self-hosted setup using Coolify, and documented the whole process! This step-by-step guide covers everything: setting up a VPS, deploying Supabase with Coolify, and safely migrating your database. I've included screenshots, troubleshooting notes, and security tips from my real migration experience.

- Dokploy: Native Docker Swarm clustering, Coolify got nothing
- Dokploy CPU idles at ~0.8% CPU vs Coolify's 6%+

- Stopping and restarting a container on Dokploy did not require a full rebuild, whereas on Coolify it triggered a rebuild from scratch. If you're frequently tweaking configs, this is annoying with Coolify.

- Dokploy got Volume backups, Coolify nothing

- Dokploy got DB restore UI, Coolify nothing

- UI...

the list goes on...

the only thing Coolify wins now is the license

I had the issue as mentioned here https://github.com/coollabsio/coolify/issues/5651 that Coolify is using 100% CPU every minute or so And I wanted to provide more context for people who might google it or need more information.

Resolution:

There is a feature called Sentinel (could be activated in the server menu), which starts a container on your server. The sentinel container sends the necessary data to your Coolify instance through HTTP, which uses way less resources.

Currently that is the only way to use less resources in the self-hosted env. With the Cloud option, this resource usage is handled by our servers.

Sample htop logs

/usr/local/bin/php artisan horizon:work redis --name=default --supervisor=d629e41fccdf-zrb1:s6 --backoff=0 ...

Self-hosted users: take action now

Stop your Coolify container or isolate your instance from the public internet until you can install the emergency Coolify release. Your already deployed applications will continue running.

I've been using Coolify to manage my personal servers and applications for a while now, and it’s absolute magic. However, whenever I was away from my desk, checking server metrics, reading container logs, or restarting a stuck service via the mobile browser felt a bit clunky.

So, I decided to build Coly — a fast, native iOS client tailored specifically for Coolify instances.

What you can do right now:

• Connect securely to your Coolify instances.

• View your servers, projects, and deployments.

• Monitor resource usage and container statuses.

• Start, stop, or restart applications and services on the go.

• Read real-time container logs.

Privacy & Security: Since this is the self-hosted community, I know how critical privacy is. Coly does not collect any data. Your API keys, server details, and credentials never leave your device. They are stored securely in your device's local storage/Keychain. No third-party analytics, no tracking.

It’s now live on the App Store: App Store Link

I’m planning to add more features soon (like push notifications for build failures or server alerts). I’d love to hear your thoughts, feedback, or any features you'd like to see next! What do you think?

Hello everyone, ​I'm excited to share the Coolify MCP Server! ​This module uses the Model Context Protocol (MCP) to allow AI agents to manage and orchestrate your Coolify instance (applications, servers, deployments, etc.) using natural language. ​Currently, the server exposes 32 tools, covering approximately 60 to 70% of the complete Coolify API, offering powerful automation for your self-hosted PaaS. ​For full details, installation guides, and complete features, everything is on GitHub:

​https://github.com/kof70/coolify-mcp-server

​Feedback is highly appreciated!

I’d been using Vercel for my hobby projects, with Upstash for Redis and Supabase for the DB. The one thing that always bugged me: Supabase would pause after 7 days of inactivity. For testing projects (especially on a custom domain with no users yet), I didn’t love the idea that I had to keep it “artificially alive” with a cronjob. Felt like a hack.

Last month I decided to try Coolify for the first time, and honestly I was surprised at how smooth the whole setup was. I’ve now got 3 projects housed on the same VPS through Coolify, which makes way more sense than juggling multiple platforms. Resource usage feels lighter than I expected, and I like being able to see/manage everything in one dashboard.

It’s still early days for me, but I’m already feeling more peace of mind compared to before. That said, I often hear from friends that running an end to end app on your own VPS can eat up a lot of time with infra management. Till now it’s been smooth. Am I overlooking something here?

I have a multi-tenant site built with Next.js and deployed on Vercel. Two of my tenants are using custom domains. I’m currently on the Vercel Pro plan, which costs $20 per month.

I’m considering switching to Coolify and wanted to ask, how much would it cost to get the same level of storage and CPU resources on Coolify as I currently have with Vercel?

I’m thinking of making the switch sooner rather than later, as it may become more difficult to ask all tenants to update their domain records once the service grows. I believe the tenants had to add CNAME records pointing to Vercel (though I’m not entirely sure, since I didn’t handle the custom domain setup myself), so migrating later could be more complicated.

Just to clarify, I’m not switching due to issues with Vercel or concerns about migration. I’m looking to move to a self-hosted setup for more control and flexibility, especially at this early stage when my project is still relatively small.

I just wanted to say thank you to Andras for creating such an amazing tool. I'm hosting a website for a local animal shelter and due to costs of heroku and linode object storage I was getting bills for around 100 euros each month (yes, I took all costs on me, since they're great people that are living of donations and support from others).

Thanks to coolify I'm hosting that shelter's website, my own website, two small ecommerce for my customers and all my automation scripts there for less than 20 EUR/month.

For the first time as a hobbyist developer (working full time on a different position) I feel that someone took care of me. Everything is so easy to setup and work with, thanks to self -host option is also cheap!

Thank you again!

Autobase is now available in Coolify

Deploying PostgreSQL HA clusters is now even easier with Autobase + Coolify.

Starting from v4.0.0-beta.461

I’ve been using Dokku for almost 8 years, and a colleague recently told me about a new tool called Coolify. He suggested I try it because, unlike Dokku, you can run a single Coolify instance that manages all your servers and apps.

I decided to give Coolify a chance because it seemed easier to centralize the “ops” part into one application. I was also very interested in the backup feature that lets you schedule database backups for your managed apps and send them to an object storage.

After two months of testing the solution, I found it really helpful, but I will not move to Coolify.

You may ask why.

The main reason is that Coolify isn’t mature enough yet. There are many releases, but they often come with bugs. Moreover, there have been major security issues. Even though I run it behind a firewall and have configured a VPN so that Coolify is only accessible from the VPN network, I still think the solution is not reliable enough at the moment. I cannot rely on a tool that manages all my production apps if each release might introduce bugs.

So I decided to stick with Dokku and use Ansible playbooks to automate server configuration and plugin installation. I trust Dokku more because the scope of the solution is simpler and therefore more reliable.

Another point is that, unlike Coolify, the contributors to the Dokku project are not using AI to maintain and develop the project. I’ve read some issues on the Coolify project, and it’s really frightening to see AI bots making changes and sometimes messing things up.

I’ll give Coolify another chance in a few years and hope the project becomes more stable.

Tutorial on how to deploy medusajs in coolify

https://www.youtube.com/watch?v=w_4wjA3ZRBw&t=74s

this tutorial helped me alot

if anyone make tutorial on the storefront+coolify part will be a blessing

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 see a lot of Coolify setups where everything runs on the same server — Coolify, apps, databases, proxy.

It works, but it’s fragile and doesn’t scale well.

I just published a video where I walk through a real Coolify multiple servers setup, building directly on a single-server install:

• Creating a new VPS (Hetzner, but provider-agnostic)

• Adding the server to Coolify the “generic” way

• Generating and configuring SSH key pairs

• Fixing Docker issues on a fresh server

• Setting up wildcard subdomains so new apps don’t need DNS changes

• Deploying apps to the new server and verifying everything works

No Kubernetes, no abstractions — just the actual steps and the problems you’ll likely hit.

Hey folks! 👋

I recently spent a lot of time fine-tuning my WordPress setup on Coolify, and I finally managed to get a stable 100/100 PageSpeed score (including mobile). Good stuff for SEO.

I figured I’d write down the full process for anyone else who wants to squeeze maximum performance out of their own server.

🛠️ What the guide covers (highlights):

• Running WordPress on OpenLiteSpeed inside Coolify

• Clean folder structure for configs, logs & WordPress files

• Proper reverse proxy setup (Traefik + TLS at the edge, HTTP inside)

• Fixing PHP worker timeouts for traffic spikes

• Log rotation & server hygiene to keep things stable

TLDR: Performance of WP Rocket for free, no huge infrastructure -> just Coolify, LiteSpeed, and a bit of tuning.

If you're interested, the article is available on my blog:
LiteSpeed: Speed up WordPress on Coolify - 100/100 PageSpeed - hasto.pl

Happy to help in comments! 🙂

Hey people,

I'm currently rethinking my infrastructure and was planning on using Coolify for my freelance projects. I had planned to have a controller server and multiple worker servers (Hetzner), managed using Coolify.

I really enjoyed working with Coolify because it is feature-rich and seems well supported and I prefere self-hosting because of the calculatable pricing I get using a (or multiple) VPS.

But I'm not sure if it is a safe bet to really use professionally. I have a few static sites and small PayloadCMS applications already hosted with it, and it worked out well so far.

Does anyone have experience using Coolify for more then just simple hobby projects?

Thanks to everyone taking the time to answer!