What is n8n?
n8n is a powerful workflow automation workspace. It allows you to build custom automated flows to handle your daily, monthly, or routine tasks seamlessly.
How n8n Works
n8n is an open-source platform. It is completely free if you self-host it on your own machine, or you can choose their paid, cloud-hosted web version.
My Journey
I absolutely loved the idea of transforming my repetitive tasks into automated workflows. I chose n8n at first glance because it integrates with so many tools (Telegram, Meta apps, Google apps, Microsoft apps, AI chatbots, etc.).
Initially, to keep costs at zero, I hosted n8n right on my laptop. It was easy to download, configure, run, and build on. However, when I tried to build real-world automation, I quickly ran into a few major limitations:
- Dependency on Laptop Status: Every time I wanted to use n8n or let a workflow run, my laptop had to be turned on with the server actively running.
- Public Access Hurdles: To integrate a local workflow with external apps/webhooks, you have to expose your private local network to the public internet. I ended up using a Cloudflare Tunnel for this, but only after days and days of trial and error.
- The Inconvenience Factor: Relying on a local machine for routine automation isn't a long-term solution. Every time I needed to check a process, I had to open my laptop, boot up the n8n server, launch the Cloudflare Tunnel, and then open the public link. I even wrote a Windows script to automate this startup process on a click, but it still felt like too much friction.
Some Commands
Make the n8n localhost http://localhost:5678 work as a public host (URL), by following commands below:
<aside>
-
Run local n8n server
PS <N8N-PACKAGE-PATH> n8n
-
Set n8n link to Cloudflared Tunnel
cloudflared tunnel <Tunnel-Name> --url <http://localhost:5678>
-
Run Cloudflared Tunnel
<N8N-PACKAGE-PATH> cloudflared tunnel run <Tunnel-Name>
Now I’ve got the a public link form Cloudflared Tunnel, for example a1b2-3c4d.cfargotunnel.com
-
For better readable URL, added a subdomain record to that I already have to indicates the tunnel’s public URL
<aside>
<img src="/icons/search_gray.svg" alt="/icons/search_gray.svg" width="40px" />
https://n8n.sajjad.design
</aside>
</aside>
Exploring Better Hosting Options
Realizing local hosting wasn't enough, I started exploring cloud alternatives. I spent December 2025 and January 2026 working intensively on this migration project to get everything running smoothly in the cloud.
First, I tried hosting n8n on Render using their free tier combined with a Supabase database. Eventually, I moved to a Hostinger VPS. At first, trying to host multiple apps and websites on a single VPS without Docker containers became a messy network confusion that frequently crashed.
The turning point was discovering Coolify. Coolify became the key to managing everything on that VPS; it automatically handles network routing and spins up an isolated Docker container every time I deploy a new app. While Coolify is a fantastic option for my current setup, it still comes with its own set of challenges—mainly optimizing memory, processing power, and network configurations across all the running containers.
One of my workflow
For Next
<aside>
💡
The Best Budget Tip: If you want to use n8n right now without breaking the bank, a low-cost VPS combined with Coolify is the absolute sweetest spot. It gives you production-level automation features without the heavy price tag of official cloud hosting.
</aside>