When should you choose self-hosted n8n or n8n Cloud?
Compare responsibilities before looking at the monthly bill. You can self-host n8n on your own infrastructure or in the cloud.
| Option | When it makes sense | What your company handles |
|---|---|---|
| Features in your current tool | Available rules and connections already solve the problem. | Configure permissions, review results, and handle errors. |
| n8n Cloud | You want to use n8n without managing a server. | Design and maintain workflows, credentials, and integrations. |
| Self-hosted n8n | You need control over the installation and can operate it. | Maintain infrastructure, backups, security, and workflows. |
| Custom software | The process needs controls or features a platform doesn't handle well. | Fund development, support, and maintenance. |
A VPS is a rented virtual server. Even though it runs in the cloud, installing n8n on one is still self-hosting.
How much does self-hosted n8n cost compared with Cloud?
The license is one part of the budget. Compare setup and operating costs for each option.
The self-hosted Community edition is free, but it doesn't include single sign-on, projects, environments, or Git-based version control. Paid self-hosted editions are also available.
The official n8n pricing page lists Cloud Starter at €20 per month when billed annually. It includes 2,500 workflow executions and up to five concurrent executions. The page also says hosted plan data is stored in Frankfurt, Germany.
An execution is one complete workflow run, regardless of how many steps it has. The listed price isn't a quote in Colombian pesos and doesn't necessarily cover connected services.
For self-hosting, add server, storage, backup, and administration costs. Include the work needed to secure the installation and handle incidents. For both options, budget for building and changing workflows, plus any external service charges.
A WhatsApp workflow, for example, may incur charges from a messaging provider and the services it calls. The timeline depends on available connections, permissions, and testing. We can't estimate it from the tool names alone.
Also check your plan's capacity. According to the n8n help center, executions over the limit fail and aren't queued on the Cloud plans described there. Decide who receives the alert and how they'll recover the pending work.
Where is your workflow data processed?
The location of n8n is only part of the picture. A workflow can receive data in Colombia and then send it to a service in another country.
Map the data from entry to destination. Identify what arrives, which service receives it, where it's stored, and who can access it. Include execution logs and backups, as well as systems that request or receive information.
For example, a company could host n8n in Colombia and connect a spreadsheet or messaging provider with infrastructure elsewhere. The n8n server's location doesn't determine where those integrations process data.
For personal data, review contracts, roles, and locations with your legal team. Colombia's SIC External Circular 003 of 2025 explains the international transfer rules in article 26 of Colombia's Law 1581 of 2012. How those rules apply depends on the operation. This article isn't legal advice.
Before connecting a service, ask its provider how it stores and processes data and who can access it. The map should reflect your agreement, not just the location in your server settings.
How do you test operations before choosing?
Use a representative workflow and document who's responsible for each part. With self-hosting, the server provider and workflow maintainer may be different parties.
- Assign owners. Identify who manages the server, updates n8n, and receives alerts. Specify who reviews the data when an integration fails. Get the support scope in writing. Installing the application doesn't necessarily include fixing your workflow.
- Secure the installation. Review access, credentials, and how the instance is exposed. The n8n security documentation describes measures such as SSL, node restrictions, and hiding execution data.
- Test recovery. Create a backup and restore it in a test environment. Confirm you can recover workflows, necessary data, and access to credentials. Record how long recovery takes, what's lost, and who performs it.
- Measure the result. Track successful executions, errors, and time to resolution. Check a sample of results against expected cases. A completed workflow doesn't guarantee that it recorded the right information.
What could this look like at a Colombian company?
This example is illustrative; it doesn't describe a client.
A small company receives quote requests through WhatsApp. A workflow takes each message, records available details in a spreadsheet, and notifies the sales team. If information is missing, it leaves the request for human review.
The input is a message with product and contact details. The expected result is an accurate row and a notification to the team. Before going live, test incomplete messages, duplicates, and unexpected data.
With Cloud, the company manages the workflow and its connections without maintaining the n8n server. On a VPS, someone must also handle updates, backups, and recovery. In both cases, review messaging costs and where connected services process data.
To assess the result, compare incoming requests with the rows created. Check that each detail landed in the right field. If a request isn't recorded, the team needs an alert and a way to recover it without creating a duplicate.
If you use Cloud and are considering a migration, confirm the available migration options with n8n. Check credentials, connections, and triggers before switching. Keep the old workflow until you've verified the new installation and tested recovery from a failure.
To compare other automation platforms, see n8n vs. Zapier vs. Make. If WhatsApp is your main channel, see which messages you can automate in WhatsApp Business.
