Can you help me understand when businesses choose to self-host n8n versus using the cloud version? I believe self-hosting for anything beyond personal use requires being an Enterprise client—is that generally true? And how should I work through this with clients?

Honestly, nobody really knows for sure, and there hasn’t been any backlash yet. Many people using n8n to make money are on the self‑hosted version, but they usually just run the executions through their own endpoint rather than setting it up for the client, which adds nuance. If you want to play it safe, I’d recommend the cloud‑hosted offering: it’s easier, faster, you don’t have to mess with webhooks, and the platform handles reliable updates and server uptime for you. Yes, it costs more—around $50 a month for five workflows and 5‑10k executions—but when you’re delivering $5k‑$15k of value per client, that fee is negligible. So my recommendation is to go with cloud hosting.

self-hostcloudn8nautomation

Related answers

youtube ↗Agency Operations

What client projects do you work on and how do you decide between using the cloud version versus self‑hosting for your customers?

I only ever use the cloud version for Nadn because it’s a multifaceted platform. While self‑hosting can be cheaper and handle higher volume, it requires you to manage dev‑ops and deployments, which I don’t want to deal with. I focus on delivering enough ROI that the $60‑a‑month cloud plan is negligible compared to the value I generate for a client—often $5,000‑plus per month. Most of my clients stay on the Pro plan, which gives 10,000 workflow executions, unlimited steps, and up to 15 active workflows, and that’s sufficient for now. If they scale further I may move them to an Enterprise plan, but the goal is always to let the cloud handle the heavy lifting so the client can concentrate on business logic.

cloudself-hostingpricing

youtube ↗Agency Operations

Is it better to self‑host or use a cloud‑hosted solution (pay pro) for agency use, and what do you personally do?

I definitely go cloud‑hosted. It's just so much easier. With self‑hosting you run into DevOps and deployment concerns that are way above most people's pay grades. I often hit self‑hosted errors that can take hours to fix, and you also have to deal with Oauth setup—getting client IDs, client secrets, and configuring Google accounts, which is a massive pain. Cloud‑hosted avoids most of that and saves a lot of time.

self-hostingcloudagency

youtube ↗Agency Operations

I'm a little bit late to the NAN hosting game. Are the self-hosting videos on platforms like Hostinger bottlenecks for providing NADN as a service?

Yes, the best option is to pay the default fee for a carefree experience with all the hassles. I'd love to see a video on this, as I was almost tempted to go self-hosting and learn the platform. I've tons of experience breakinging down barriers and obstacles of self-hosting and common apps affected by it, and how much more effort and time is needed to manage and maintain. Suffice to say, the reason I typically recommend cloud hosting everything is that you don't have to deal with deployment, DevOps, or additional environment variables and similar self-hosting concerns. As an automation specialist, believe it or not, your main point of value is not in your technical knowledge; it's in knowing just enough of the technicals to apply them to real business processes. Then you spend the rest of your time becoming a business person, a business expert. That's where the leverage lies with the alpha people who get really into self-hosting—they often lose the cart for the horse, spending so much time figuring out every little technical detail, spinning up Docker containers, getting environment variables right, and doing EngineX pass-through for webhook URLs. It's incredible how much time that takes. My recommendation is to focus on the things you actually get paid for—delivering value to your clients—not on designing the most optimal, technically and academically perfect solution.

self hostingcloud hostingautomation

youtube ↗Agency Operations

How do you deliver n8n workflows to clients who aren't familiar with them? Do they self-host their own account or pay a monthly subscription for cloud hosting? How do you get their credentials/API keys — do you get access on the call and set it up on their n8n account yourself, or do you guide them through it?

They pay for cloud hosting on a monthly subscription and sign up themselves — I get them to create the account, guide them through it, and then they hand me the account access, since it's tied to their card. That's the 80/20 approach: guide them to create it, get access, but they own and pay for it.

client deliveryn8nhostingcredentials