n8n Cloud is the managed version of n8n. Same platform, same nodes, same capabilities as self-hosted -- but n8n handles the server, updates, backups, and uptime for you. You can start for free and be building workflows in under 5 minutes.
Want full control instead? The self-hosted guide walks through running n8n on your own server with Docker. It's free and has no feature restrictions.
When to Use Cloud vs Self-Hosted
Honest tradeoffs:
| n8n Cloud | Self-Hosted | |
|---|---|---|
| Cost | Free to start, paid plans from $24/mo | Free forever |
| Setup time | 2 minutes | 15-30 minutes |
| Maintenance | None (managed updates, backups) | You handle updates, backups, uptime |
| Webhooks | Work immediately (public URL included) | Requires domain + reverse proxy + SSL |
| Data location | n8n's infrastructure (EU/US) | Your machine |
| Execution limits | Tier-dependent | Unlimited |
| Best for | Getting started fast, teams, no-infra setups | Homelab, full data control, high volume |
If you don't want to manage Docker and servers, Cloud is the right call. If you already have a server running and enjoy that kind of thing, self-host.
Quick Setup
1. Sign up
Go to n8n.io/cloud and create an account. You can start on the free plan with no credit card required.
2. Create your instance
After signup, n8n provisions a dedicated instance for you. Takes about a minute. You'll get a URL like your-name.app.n8n.cloud.
3. Build your first workflow
Click Add workflow and you're in the editor. The interface is identical to self-hosted. Drag nodes from the panel on the left, connect them, configure triggers.
A simple test to verify everything works:
- Add a Schedule Trigger (set to every minute)
- Add a Set node, output
{"message": "Cloud is working"} - Connect them
- Click Activate (toggle in the top right)
- Wait a minute, then check Executions -- you should see a successful run
4. Set up credentials
Go to Credentials in the left sidebar. Add API keys for any services you want to connect (Slack, OpenAI, Google Sheets, etc.). n8n stores these encrypted on their infrastructure.
That's it. You're running.
Configuration Notes
- Webhook URLs work immediately. Cloud instances have a public URL out of the box. No need to set up DNS, reverse proxies, or SSL certificates. This alone saves a lot of headaches if you're building webhook-triggered workflows.
- Execution limits depend on your plan. The Starter plan caps active workflows at 5. Pro is unlimited active workflows. Check n8n.io/pricing for current limits.
- Community nodes are supported. You can install community-built nodes from the n8n community node registry, same as self-hosted.
- Exporting workflows: Your workflows are yours. Go to any workflow, click the three dots menu, and Export to get a portable JSON file. You can import these into a self-hosted instance anytime. No lock-in.
- Version updates happen automatically. n8n Cloud stays on the latest stable release. If you're following a tutorial that references an older version, some node names or settings might look slightly different.
- Cron trigger note: Same as self-hosted -- if you activate a workflow via the API rather than the UI toggle, the cron scheduler might not register. Toggle the workflow off and back on in the UI to fix it.
Moving Between Cloud and Self-Hosted
n8n makes this straightforward. Export your workflows as JSON from one instance, import into the other. Credentials don't transfer (they're encrypted per-instance), so you'll need to re-add API keys after importing.
If you start on Cloud and later want to self-host (or vice versa), you won't lose your work.