Self-hosted n8n works until something breaks at two in the morning.

Who carries what

We do not sell n8n building or hosting, and our systems are Python agents. If you searched for n8n help, the useful thing we can offer is a view of where the cost lands before you pick a route.

Self-hosting suits a team that already administers servers and enjoys the work. It suits a team badly when "someone" means the one developer who is also your support desk.

The cloud prices on October 2, 2026

n8n's pricing page lists cloud plans in euros, shown as billed annually: Starter at EUR 20 a month for 2,500 workflow executions, Pro at EUR 50 for 10,000, and Business at EUR 667 for 40,000. The page says annual billing saves 17%.^[1] It also lists self-hosted options, where you run and secure the server yourself.^[1] An execution is not the same unit as another tool's task or credit, so check the definitions carefully before you compare numbers across different vendors.

Four questions before you rely on a self-hosted flow

1. Who gets notified when it stops running, and how quickly would they respond?
2. Where are the backups kept, and has anyone ever restored one?
3. Does the workflow reply to customers? If so, where is it written down that a STOP ends the conversation?
4. If the person who built it leaves the company, can the next person read and understand it?

With good answers, keep running it. Our advice for a workflow that is working is to leave it alone.

When the flow starts speaking for you

The case for code begins when the flow talks to customers on your behalf and picks up duties: consent, an AI disclosure, WhatsApp's window and templates, caps, a log, and a kill switch. We write those as Python agents and test them, though the testing so far is a sandbox with simulated customers and no paying client. No-code or Python agents sets out the choice, and build it yourself, or buy it done compares the prices.