This article covers the questions that come up before you subscribe. For troubleshooting while using it, see the n8n FAQ.
Q: How is this different from the official n8n Cloud?
The main differences are the billing model and where your data lives. n8n Cloud caps executions by plan, while hosting on your own instance is billed per instance, with executions not counted separately.
As for data, everything your workflows process stays inside your own instance. For teams handling customer personal data that is a practical concern, not just a matter of feeling better about it. The full comparison is in self-hosted vs. Cloud.
Q: Is there a cap on executions?
There is no per-execution billing. What you need to watch is resources, not counts: high-frequency, high-volume workflows consume CPU and memory.
There is also something many people only discover later: by default n8n stores the complete record of every execution, which eats storage over time and slows the editor down. You need to set a retention period. See execution data growth.
Q: Can I install community nodes?
Yes. This is one of the main benefits of hosting on your own instance, since community nodes are restricted on the official cloud plans.
Q: Is the webhook URL fixed?
Every instance gets its own subdomain and automatic SSL, so webhook URLs work out of the box with no domain or certificate work on your side.
That matters when you are connecting services like LINE, Stripe, or GitHub that need a fixed callback URL. With the free tier of a tunneling tool, the URL changes on every restart and the other side can no longer reach you. Related reading: where to host a LINE bot.
Q: I use Zapier today. Is migrating a hassle?
The workflows themselves cannot be imported directly, so you rebuild them. But the real point is not the rebuilding effort, it is not copying them one to one: what you designed on Zapier was shaped by per-step billing, and once you move, all the compromises you made to save money can be undone.
The recommended migration order is in migrating from Zapier to n8n.
Q: Where are my API keys stored? Is that secure?
Credentials for each service are stored inside your own instance. Every instance is a separate Docker container on its own network, and API keys are stored with AES-256 encryption.
Q: Do I need to know how to code?
Basic workflows can be assembled by dragging and dropping, with no coding required.
But honestly: when the service you want to connect has no ready-made node, you will need to read its API docs and assemble the call yourself with an HTTP Request node. That is not really programming, but it does take some technical patience. If you would rather not touch anything like that, n8n may not be the right tool for you.
Q: How many workflows can one plan run?
There is no limit on the number of workflows. What is limited is the compute resources of the instance. Dozens of low-frequency workflows are usually fine, while a single workflow that runs every minute and processes large volumes of data is the one that actually strains resources.
Sources and further links
n8n's nodes and pricing change often. These are the primary sources for checking:
- n8n official documentation
- n8n official pricing — cloud plans and quotas
- n8n source code and release notes — the authoritative source for license terms
Resources and cost
Q: Is the plan's memory enough?
It is more than enough for typical API integrations, form notifications, and data sync workflows, and several hundred executions a day is no problem. What to watch for is "moving a large volume of data in one pass", such as a loop that processes tens of thousands of records at once. Just split that kind of job into smaller batches.
Q: How does this compare to renting a VPS and setting it up myself?
The server rent alone is roughly the same. The difference is operations: updates, backups, SSL, and monitoring are all on us. Once you count the time you would spend handling those yourself, managed hosting almost always comes out ahead. The full breakdown is in self-hosted vs. managed cost analysis.
Q: Can I try it first?
Yes. Request a free trial on the Free Trial page and our team will set it up for you. No credit card is needed and nothing is charged automatically when the trial ends, so the cost of finding out is low.
Q: How do I pay?
Recurring credit card billing; the yearly plan is charged once a year. Managing your subscription and canceling renewal are self-service in the dashboard, with no email request needed. After you cancel, service continues until the end of the current period and you are not charged again. There is no cancellation fee; the period you have already paid for is not refunded or prorated.
Further reading
- n8n FAQ: resource limits, webhook URLs, and community nodes
- Is self-hosting n8n cheaper? A cost table that counts your time
- n8n vs. Zapier vs. Make: monthly cost and data residency for Taiwan teams
- RoamerHost n8n hosting plans
Want someone to build it for you?
If you would rather not assemble these workflows yourself, or the project is large enough that you want someone planning it with you, Roamer Tech (the company behind RoamerHost) takes on contract work for business process automation and AI agents:
