Decision
n8n Cloud vs self-hosted
Prices checked . n8n's pricing page and docs re-read . This page is the decision. The dated cost tables stay on what n8n costs at 2,500, 10,000, and 50,000 executions a month.
Should I use n8n Cloud or self-host n8n?
Cloud means n8n hosts it. n8n applies security and stability updates, and you still choose the version, release track, cadence, and maintenance window. You pay for a production-execution allowance. Starter on n8n Cloud is $20/mo first term and $20/mo renewal (annual), checked Oct 19, 2026. 2,500 executions/mo, 5 concurrent (allowance checked Oct 17, 2026). Pro is $50/mo first term and $50/mo renewal (annual), checked Oct 19, 2026. 10,000 executions/mo, up to 50 concurrent (allowance checked Oct 17, 2026). Currency basis: USD in the dataset. Dataset note: Starter $20 /mo, billed annually (US locale; EU visitors see 20€). Dataset note: Pro $50 /mo, billed annually (US locale; EU visitors see 50€). A euro figure on the pricing page is not converted and is not mixed into this dollar price. Self-hosted Community edition is free under the Sustainable Use License (fair-code, source-available, and not open source as the Open Source Initiative defines it). You pay for the server at renewal, and you do the updates, backups, and security work yourself. Neither side wins for every reader. The decision turns on execution volume, how much operations work you will take on, how you need to scale, and where the data has to live.
A production execution is one automatic run of a workflow, started by a trigger, a schedule, or polling. An allowance is how many of those a Cloud plan includes. Renewal (steady state) is the price after the first term. Queue mode is a main instance plus workers, Redis, and Postgres. The Community edition is the free self-hosted edition you get with no license key. Run your own numbers in the plan calculator or the renewal-aware calculator. How big a server to start with is on how much RAM and CPU n8n needs.
Start with who runs it, not a host shortlist
n8n splits the choice into two decisions (choose how to use n8n). First, Cloud or self-hosted: who runs the infrastructure. Second, the plan or edition inside that choice. The same guide says both options support production use. A self-hosted instance can be a production system. A Cloud workspace can be a production system.
Cloud is for starting with no installation, for readers who do not want to manage infrastructure, and for readers who want n8n to handle hosting, updates, and scaling. Self-hosting is for full control over the deployment, for custom setups, and for teams that already have the infrastructure and the technical resources. The free path on that page is the self-hosted Community edition. After this decision, best n8n hosting is the page for which kind of host.
What does each side cost at a given volume?
The verified Cloud allowances are the two dataset rows. n8n Cloud Starter (annual): $20/mo first term and $20/mo renewal (annual), checked Oct 19, 2026. 2,500 executions/mo, 5 concurrent (allowance checked Oct 17, 2026). The 2,500 row is priced on the 2,500 table. Pro (annual): $50/mo first term and $50/mo renewal (annual), checked Oct 19, 2026. 10,000 executions/mo, up to 50 concurrent (allowance checked Oct 17, 2026). The 10,000 row is priced on the 10,000 table. Currency basis: USD in the dataset. Dataset note: Starter $20 /mo, billed annually (US locale; EU visitors see 20€). Dataset note: Pro $50 /mo, billed annually (US locale; EU visitors see 50€). A euro figure on the pricing page is not converted and is not mixed into this dollar price. All plans on the pricing page include unlimited users and workflows (n8n pricing).
n8n Cloud at 50,000 executions a month is — / not yet verified. No plan in the dataset lists 50,000 executions a month. The pricing page's Business plan is labeled self-hosted only and is not in the dataset, so it is not priced here and is not used as a substitute. Enterprise is listed as custom on that page and is not in the dataset either. The 50,000 column, including that blank, is on the 50,000 table. Self-hosting at that volume is a queue-mode question first, then a server you test. It is not answered by picking a larger VPS price.
Self-hosted server examples, at renewal
These are examples, in two size classes. They are not a ranking, and affiliate relationships do not decide which ones appear. Each one is a heuristic to test on the sizing guide and its self-test, not a claim that the plan handles a given number of executions. All current prices, dated, are on the monthly price snapshots (this month: October 2026).
1 GB class
- Vultr Cloud Compute 1 GB (Regular): $5/mo first term and $5/mo renewal (hourly), checked Oct 19, 2026. 1 vCPU, 1 GB RAM, 25 GB SSD, 1024 GB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim.
- Linode (Akamai) Nanode 1GB: $5/mo first term and $5/mo renewal (hourly), checked Oct 19, 2026. 1 vCPU, 1 GB RAM, 25 GB disk, 1000 GB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim.
4 GB class
- Hostinger KVM 1: $6.49/mo first term and $11.99/mo renewal (+85%), 24-month renewal term in the dataset (prepaid term), checked Oct 19, 2026. 1 vCPU, 4 GB RAM, 50 GB NVMe, 4 TB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim.
A server price is not the whole cost. Your admin time is your hours per month times your rate. This site does not claim a rate or a number of hours. Put yours in the renewal-aware calculator. The hidden-cost lines stay on the cost-by-executions page. This page does not reprint those tables. A paid self-hosted licence, if you need Business or Enterprise features, is a separate line. It is not in the dataset. Verify it at n8n pricing. It is not folded into these server prices.
What do I have to maintain if I self-host n8n?
Updates
The update guide says to try to update at least once a month, to check the release notes for breaking changes, and to test in a separate environment first (update n8n). The backup guide says to take a full backup before that update (back up and restore). The procedure depends on how you installed n8n. The sequence, and who patches what on each host, is on how to update n8n safely.
On Cloud, n8n always applies security and stability updates automatically. You still choose the version, the release track (Beta or Stable; Stable is what n8n recommends for mission-critical workloads), the cadence, and the maintenance window. Changing the version restarts the workspace for 1 to 2 minutes (update your Cloud version). The same patch guide has the Cloud row.
Backups
A complete self-hosted backup is the .n8n folder, which holds the encryption key, plus a PostgreSQL backup when you use Postgres, plus external storage or custom paths when you use them (back up and restore).
Without the encryption key, restored credentials cannot be decrypted.
The CLI export covers workflows and credentials only. It is not a full backup: users, execution history, variables, and the encryption key stay behind.
Stop n8n before copying .n8n when the database is SQLite.
A host snapshot is not that backup.
The per-host table, with its filled, partial, and not-verified cells, is on n8n backups.
Cloud backup schedule, retention, and restore: — / not yet verified. The Starter and Pro cards and the Cloud update guide do not state one, so this page does not promise that n8n backs the workspace up.
Security and the setup surface
Self-hosting puts the install, the domain and HTTPS, the proxy and webhook URL, and patching on you. Install methods in the docs are one-line setup, Docker Compose, Docker, npm, and cloud providers (host n8n). That page says npm is deprecated from n8n 3.0. Fixes for the usual first-install breakage, and the per-host setup surface, are on n8n setup problems and the patch guide.
SSO, external secret stores, and log streaming are paid-edition features (compare editions). Needing them changes the edition, on Cloud or self-hosted. It does not by itself pick who runs the server. n8n publishes no universal minimum RAM or CPU. Sizing stays a heuristic to test on the sizing guide. The control you gain by self-hosting is control of the deployment. It is not a measured security score.
How does each side scale?
On Cloud, concurrency is the plan limit in the dataset. Starter is 5 concurrent. Pro is up to 50 concurrent. Executions past that limit queue and then run first in, first out, in regular mode (understand Cloud concurrency). Scaling means moving to a different allowance. A 50,000-execution Cloud price is — / not yet verified, for the reason in the cost section. Queue mode on Cloud is documented for Enterprise plans. Enterprise is not priced in this dataset.
Self-hosted, start with one instance. Queue mode is a main instance that receives triggers, Redis as the broker, workers that execute, and a shared database (enable queue mode). You scale by adding or removing workers. Running queue mode with SQLite is not recommended. Postgres is the documented database. Binary data in queue mode cannot use filesystem storage. S3 external storage is the documented path, and external binary storage is a paid-edition feature. No workers-per-GB figure and no executions-per-worker figure are published, so this page prints none. Architecture comes before size. The size check is the sizing guide and the self-test.
Where is my data on n8n Cloud vs self-hosted?
For hosted plans, n8n says data is stored in the EU, on servers in Frankfurt, Germany (n8n pricing). Dataset: Starter: EU (Frankfurt), no choice, specs checked Oct 17, 2026. Pro: EU (Frankfurt), no choice, specs checked Oct 17, 2026. For self-hosted plans, data is wherever you decide to host n8n, on infrastructure you provide and manage, and you keep the backup and the encryption key. External secret stores and external binary storage are paid-plan features. The pricing page is the list of which tier includes them. Certifications, a data-processing agreement, sub-processors, and any region other than Frankfurt are not verified here.
When Cloud wins
- You do not want to manage infrastructure, or you want to start with no installation (n8n's deployment guide). Next: the plan calculator.
- Your production executions fit a verified allowance: 2,500 a month on Starter, or 10,000 a month on Pro, at the renewal prices above. Next: the 2,500 table or the 10,000 table, and the n8n Cloud host page.
- You would rather n8n handle hosting, security and stability updates, and scaling, and the server-price gap is not the question you are trying to answer. Next: the renewal-aware calculator, where your own hours and rate go in.
When self-hosting wins
- You want full control of the deployment, or the use case needs a custom setup (n8n's deployment guide). Next: the setup guide.
- You already have the infrastructure and someone who will do the work. Next: updates and patching and backups.
- The data has to live in a place you choose, not only Frankfurt. Next: the data section above, then a host page for the server you actually pick.
- The allowance is the binding constraint, and you accept the operations work in the section above. The gate is the renewal price of a server you have self-tested, not a promised saving. Next: the self-test, then the cost tables, then the calculator.
There is no ranked winner and no volume at which one side becomes the cheaper one on this page. Once you know Cloud or self-hosted, best n8n hosting is the host-kind shortlist and the cheapest way to host n8n is the renewal-priced shortlist. If you are leaving a host on a deadline, the Zeabur shutdown guide is a separate page. Migration steps stay there.
Weighing Zapier or Make against self-hosted n8n instead? Zapier and Make vs self-hosted n8n prices one workflow at 2,500, 10,000, and 50,000 runs a month.
What's the difference between n8n Cloud and self-hosted n8n?
| Aspect | n8n Cloud (Starter/Pro as listed) | Self-hosted (Community unless stated) |
|---|---|---|
| Who runs it | Fully hosted by n8n. No installation (choose how to use n8n). | You provide and manage the infrastructure. Install options in the docs: one-line setup, Docker Compose, Docker, npm, and cloud providers. The host docs say npm is deprecated from n8n 3.0 (host n8n). Without a license key it runs as the free Community edition. |
| Price basis | Per production-execution allowance. Starter (annual) on /hosts/n8n-cloud/ is $20/mo first term and $20/mo renewal (annual), checked Oct 19, 2026. 2,500 executions/mo, 5 concurrent (allowance checked Oct 17, 2026). Pro (annual) on /hosts/n8n-cloud/ is $50/mo first term and $50/mo renewal (annual), checked Oct 19, 2026. 10,000 executions/mo, up to 50 concurrent (allowance checked Oct 17, 2026). Currency basis: USD in the dataset. Dataset note: Starter $20 /mo, billed annually (US locale; EU visitors see 20€). Dataset note: Pro $50 /mo, billed annually (US locale; EU visitors see 50€). A euro figure on the pricing page is not converted and is not mixed into this dollar price. | The Community edition is free under the Sustainable Use License (community license). You pay for the server. Renewal-priced examples only, not capacity claims: Vultr Cloud Compute 1 GB (Regular) (1 GB class) on /hosts/vultr/: $5/mo first term and $5/mo renewal (hourly), checked Oct 19, 2026. 1 vCPU, 1 GB RAM, 25 GB SSD, 1024 GB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. Linode (Akamai) Nanode 1GB (1 GB class) on /hosts/linode/: $5/mo first term and $5/mo renewal (hourly), checked Oct 19, 2026. 1 vCPU, 1 GB RAM, 25 GB disk, 1000 GB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. Hostinger KVM 1 (4 GB class) on /hosts/hostinger/: $6.49/mo first term and $11.99/mo renewal (+85%), 24-month renewal term in the dataset (prepaid term), checked Oct 19, 2026. 1 vCPU, 4 GB RAM, 50 GB NVMe, 4 TB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. |
| Price at 50,000 exec/mo | — / not yet verified. No plan in the dataset lists 50,000 executions a month. The pricing page's Business plan is labeled self-hosted only and is not in the dataset, so it is not priced here and is not used as a substitute. Enterprise is listed as custom on that page and is not in the dataset either. | Queue mode comes before a bigger server (enable queue mode). Renewal-priced examples only, with no claim that a plan handles 50,000 executions a month. The sizing self-test is on /n8n-vps-requirements/#self-test. |
| What counts toward the bill or quota | Production executions only: runs started by a trigger, a schedule, or polling (understand executions). A schedule counts every firing. A poll counts only when it finds new data. A webhook counts each inbound request that starts the workflow, including an empty body. Manual runs, sub-workflow runs, error-workflow runs, empty polls, and malformed requests that fail before the workflow starts do not count. | The same counting rules apply on a licensed paid plan (understand executions). The Community edition has no n8n execution bill. The server is the cost. |
| Updates | n8n always applies security and stability updates automatically. The owner chooses the version, the release track (Beta or Stable; Stable is recommended for mission-critical workloads), the update cadence, and the maintenance window. A version change restarts the workspace for 1 to 2 minutes (update your Cloud version). Who patches what, by host, is on /n8n-hosting-patch-security/. | Your job. Try to update at least once a month, check the release notes for breaking changes, and test in a separate environment first (update n8n). Take a full backup before updating (back up and restore). The steps depend on the install method. The sequence and the per-host patch row are on /n8n-hosting-patch-security/. |
| Backups | — / not yet verified. The Starter and Pro cards and the Cloud update guide do not state a backup schedule or a restore guarantee, so none is promised here. | Your job. A complete backup is the .n8n folder, including the encryption key, plus a PostgreSQL backup when you use Postgres, plus external storage or custom paths when you use them. Without the encryption key, restored credentials cannot be decrypted. The CLI export of workflows and credentials is not a full backup. Stop n8n before copying .n8n when the database is SQLite (back up and restore). A host snapshot is not a backup. The per-host table is on /n8n-hosting-backups/. |
| Scaling | Plan concurrency, as stored in the dataset: Starter 5 concurrent; Pro up to 50 concurrent. Executions past the limit queue and then run first in, first out, in regular mode (Cloud concurrency). Moving up means a different allowance. — / not yet verified. No plan in the dataset lists 50,000 executions a month. The pricing page's Business plan is labeled self-hosted only and is not in the dataset, so it is not priced here and is not used as a substitute. Enterprise is listed as custom on that page and is not in the dataset either. Queue mode on Cloud is documented for Enterprise plans, which are not priced in this dataset. | One instance first. Queue mode is a main instance, workers, Redis, and Postgres. Add or remove workers to scale. Queue mode with SQLite is not recommended. Filesystem storage for binary data is not supported in queue mode; S3 external storage is the documented path (enable queue mode), and external binary storage is a paid-edition feature (compare editions). No workers-per-GB or executions-per-worker figure is published, so none is given. Size is a heuristic to test on /n8n-vps-requirements/. |
| Data location | For hosted plans, data is stored in the EU, on servers in Frankfurt, Germany (n8n pricing). Dataset: Starter: EU (Frankfurt), no choice, specs checked Oct 17, 2026. Pro: EU (Frankfurt), no choice, specs checked Oct 17, 2026. | Wherever you decide to host n8n (n8n pricing), on infrastructure you provide and manage (choose how to use n8n). You keep the backup and the encryption key (back up and restore). |
| Features needing a paid tier | SSO, LDAP, multiple environments, and Git version control are not on the Starter or Pro cards. They appear on the Business card, which the pricing page labels self-hosted only. Business is not in the dataset, so it is not priced here. Enterprise lists an external secret store and log streaming. The pricing page is the definitive list (n8n pricing). | The Community edition excludes custom variables, environments, external secrets, external storage for binary data, log streaming, multi-main mode (queue mode itself is included), projects, SSO (SAML, LDAP), workflow and credential sharing, and version control using Git. Paid Business and Enterprise plans unlock those (compare editions). A paid self-hosted licence price is not in the dataset. Verify it at n8n pricing if you need it. It is not added to a server total here. |
| License | Paid subscription with its own terms. The Sustainable Use License FAQ does not apply to n8n Cloud (license FAQ). | Free Community edition under the Sustainable Use License. Fair-code and source-available. n8n does not call itself open source, because OSI open source licenses cannot limit use the way this license does (community license). You may use or modify it for your own internal business purposes, or for non-commercial or personal use. You may build client automations those clients cannot create or edit, and charge for that work. You may not host n8n as a service that lets clients build workflows, or let external end users build or configure their own workflows through your product (license FAQ). If a case is unclear, the docs say to write to license@n8n.io. |
| Support | Forum support is listed on the Starter card, and the Pro card includes everything in Starter (n8n pricing). Dedicated support with an SLA is listed on the Enterprise card, not on Starter or Pro. No support-response time is published for Starter or Pro, so none is stated here. | — / not yet verified. The pricing page does not state a separate support channel for the Community edition. |
Other Cloud limit rows — active workflows, saved executions, storage, log retention, and max execution duration — stay off this table. The dataset and the live pricing page do not yet agree on those fields, so they are left as — / not yet verified instead of being guessed. Uptime, an SLA, and a backup promise for Starter or Pro are in the same state: absent here until an official page states them.
Compare two plans, first term then renewal
Pick a self-hosted plan and an n8n Cloud plan. The result uses the dataset: the first-term price, then the renewal price after the first term. A missing renewal stays an em dash. It is not treated as zero. This does not estimate executions. Your own volume goes in the form under it, and the dated tables stay on the cost page.
True cost calculator
First-term price, then the renewal price after the first term ends.
Run your own numbers
The form below is the renewal-aware calculator. Blank hidden costs stay blank. An unknown renewal stays an em dash. The suggested server class is a heuristic to test, not a benchmark.
Execution-tier true cost
The handoff from the cost-by-executions tables. Blank hidden costs stay excluded. An unknown renewal stays an em dash and is never treated as zero. The suggested class is a heuristic to test.
Enter a production-execution count, or open this calculator from a tier table. Totals appear here.
FAQ
- Should I use n8n Cloud or self-host n8n?
- Neither side wins for every reader. n8n's deployment guide says to choose Cloud when you want to start with no installation, you do not want to manage infrastructure, or you want n8n to handle hosting, updates, and scaling, and to choose self-hosting when you want full control, a custom setup, or you already have the infrastructure and the technical resources. Both support production use. Cloud fits when your volume sits inside a verified allowance (Starter (annual) is $20/mo first term and $20/mo renewal (annual), checked Oct 19, 2026. 2,500 executions/mo, 5 concurrent (allowance checked Oct 17, 2026). Pro (annual) is $50/mo first term and $50/mo renewal (annual), checked Oct 19, 2026. 10,000 executions/mo, up to 50 concurrent (allowance checked Oct 17, 2026). Currency basis: USD in the dataset. Dataset note: Starter $20 /mo, billed annually (US locale; EU visitors see 20€). Dataset note: Pro $50 /mo, billed annually (US locale; EU visitors see 50€). A euro figure on the pricing page is not converted and is not mixed into this dollar price.) and you would rather pay n8n to run it. Self-hosting fits when the data has to live where you choose, or the allowance is the binding constraint and you take on the update, backup, and setup work. n8n Cloud at 50,000 executions a month is — / not yet verified. No plan in the dataset lists 50,000 executions a month. The pricing page's Business plan is labeled self-hosted only and is not in the dataset, so it is not priced here and is not used as a substitute. Enterprise is listed as custom on that page and is not in the dataset either. Run your own numbers in the calculator on /n8n-cloud-vs-self-hosted/#execution-cost.
- Is self-hosting n8n worth it?
- There is no universal yes or no. The Community edition is free under the Sustainable Use License (fair-code, source-available, and not open source as the Open Source Initiative defines it). You pay the server at renewal, and you pay with your own time. 1 GB class examples: Vultr Cloud Compute 1 GB (Regular) on /hosts/vultr/ is $5/mo first term and $5/mo renewal (hourly), checked Oct 19, 2026. 1 vCPU, 1 GB RAM, 25 GB SSD, 1024 GB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. Linode (Akamai) Nanode 1GB on /hosts/linode/ is $5/mo first term and $5/mo renewal (hourly), checked Oct 19, 2026. 1 vCPU, 1 GB RAM, 25 GB disk, 1000 GB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. 4 GB class example: Hostinger KVM 1 on /hosts/hostinger/ is $6.49/mo first term and $11.99/mo renewal (+85%), 24-month renewal term in the dataset (prepaid term), checked Oct 19, 2026. 1 vCPU, 4 GB RAM, 50 GB NVMe, 4 TB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. Those figures are examples to test, not a promised saving. Your admin time is your hours per month times your rate. This site claims neither number. The work is updates, backups including the encryption key, and the setup surface, spelled out on /n8n-hosting-patch-security/, /n8n-hosting-backups/, and /n8n-hosting-setup/.
- How much does n8n Cloud cost vs a VPS?
- Starter (annual) is $20/mo first term and $20/mo renewal (annual), checked Oct 19, 2026. 2,500 executions/mo, 5 concurrent (allowance checked Oct 17, 2026). Pro (annual) is $50/mo first term and $50/mo renewal (annual), checked Oct 19, 2026. 10,000 executions/mo, up to 50 concurrent (allowance checked Oct 17, 2026). Currency basis: USD in the dataset. Dataset note: Starter $20 /mo, billed annually (US locale; EU visitors see 20€). Dataset note: Pro $50 /mo, billed annually (US locale; EU visitors see 50€). A euro figure on the pricing page is not converted and is not mixed into this dollar price. VPS examples at renewal, 1 GB class: Vultr Cloud Compute 1 GB (Regular) on /hosts/vultr/ is $5/mo first term and $5/mo renewal (hourly), checked Oct 19, 2026. 1 vCPU, 1 GB RAM, 25 GB SSD, 1024 GB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. Linode (Akamai) Nanode 1GB on /hosts/linode/ is $5/mo first term and $5/mo renewal (hourly), checked Oct 19, 2026. 1 vCPU, 1 GB RAM, 25 GB disk, 1000 GB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. 4 GB class: Hostinger KVM 1 on /hosts/hostinger/ is $6.49/mo first term and $11.99/mo renewal (+85%), 24-month renewal term in the dataset (prepaid term), checked Oct 19, 2026. 1 vCPU, 4 GB RAM, 50 GB NVMe, 4 TB bandwidth. Example only. Whether it is enough is a heuristic to test on /n8n-vps-requirements/, not a capacity claim. The dated volume tables stay on /n8n-cost-by-executions/#cost-2500, /n8n-cost-by-executions/#cost-10000, and /n8n-cost-by-executions/#cost-50000. They are not repeated here. n8n Cloud at 50,000 executions a month is — / not yet verified. No plan in the dataset lists 50,000 executions a month. The pricing page's Business plan is labeled self-hosted only and is not in the dataset, so it is not priced here and is not used as a substitute. Enterprise is listed as custom on that page and is not in the dataset either.
- What do I have to maintain if I self-host n8n?
- You update it, you back it up, and you run the setup. The update guide says to try at least once a month, read the release notes for breaking changes, and test in a separate environment first. The backup guide says to take a full backup before updating. A complete backup is the .n8n folder, including the encryption key, plus Postgres or external storage when you use them. A CLI export of workflows and credentials is not a full backup. Install, the domain and HTTPS, the proxy and webhook URL, and patching are yours. The guides are /n8n-hosting-patch-security/, /n8n-hosting-backups/, and /n8n-hosting-setup/. On Cloud, n8n applies security and stability updates automatically, and you still choose the version, release track, cadence, and maintenance window. A version change restarts the workspace for 1 to 2 minutes.
- Where is my data on n8n Cloud vs self-hosted?
- For hosted plans, n8n says data is stored in the EU, on servers in Frankfurt, Germany. Dataset: Starter: EU (Frankfurt), no choice, specs checked Oct 17, 2026. Pro: EU (Frankfurt), no choice, specs checked Oct 17, 2026. For self-hosted plans, data is wherever you decide to host n8n, on infrastructure you manage, and you keep the encryption key. Certifications, a data-processing agreement, sub-processors, and any region other than Frankfurt are not verified on this page.
- Is n8n open source, and can I host it for my clients?
- n8n does not call itself open source. The Community edition is free under the Sustainable Use License, which is fair-code and source-available. OSI open source licenses cannot limit use the way this license does. You may use it for your own internal business purposes or for non-commercial or personal use, build automations for clients who cannot create or edit them, and charge for that work. You may not host n8n as a service that lets clients build workflows, or let external end users build or configure their own workflows through your product. The license FAQ does not apply to n8n Cloud, which is a paid subscription with its own terms. If a case is unclear, the docs say to write to license@n8n.io.
Prices: /data/prices.json (last checked ). How checks work: /methodology/. Price history: /changelog/. Prices this month: October 2026.
Docs and the pricing page re-read .
Affiliate disclosure: Some links on this site are affiliate links. If you buy through them, we may earn a commission at no extra cost to you. This never affects the prices we show or how hosts are ranked.