You have seen what n8n can do. Now you just want it running so you can build your first automation. The problem is that most setup guides jump straight into Docker Compose, PostgreSQL, and reverse proxies, which is overkill if you are not a developer.
This guide keeps it simple. There are three ways to set up n8n, and the right one depends on how technical you want to get and how much you want to spend. We will walk through all three, then help you pick.
The three ways to set up n8n
| Method | Best for | Time | Cost |
|---|---|---|---|
| n8n Cloud | Anyone who wants it running today | About 2 minutes | From ~$20/month (14-day free trial) |
| Local trial | Testing on your own computer first | About 5 minutes | Free |
| Self-hosted on a VPS | High volume, full control, data privacy | 30 to 60 minutes | ~$6 to $20/month for the server |
Most people overthink this. If you are not sure, start with the Cloud trial or a local install, build a workflow, and decide later whether self-hosting is worth the effort.
Option 1: n8n Cloud (the fast path)
This is the simplest way to get started, and it is what we recommend for anyone who does not specifically need to self-host. n8n handles all the servers, updates, and security for you.
- Go to n8n.io and click Get started or Start free trial.
- Create your account with an email address.
- Pick a workspace name. This becomes part of your n8n web address.
- That is it. You land directly in the editor, ready to build.
The Starter plan runs around $20 per month and covers 2,500 workflow executions, which is plenty for a few automations. The Pro plan is roughly $50 per month for higher volume. The 14-day free trial does not ask for a card, so you can test properly before paying.
Choose Cloud if: you want zero maintenance, you run a handful of workflows, and you would rather pay a small monthly fee than manage a server.
Option 2: Try n8n free on your own computer
If you want to play with n8n before committing to anything, you can run it locally in a few minutes. You only need Node.js installed.
Open your terminal and run:
npx n8nWait for it to finish, then open http://localhost:5678 in your browser. n8n is now running on your machine.
This is great for learning and testing. Keep in mind that a local install only runs while your computer is on, so it is not meant for live automations that need to fire 24/7. Treat it as a sandbox.
Choose local if: you just want to learn the interface, follow a tutorial, or test a workflow before deciding where to host it for real.
Option 3: Self-host n8n on a VPS
Self-hosting gives you unlimited executions, full control, and keeps your data on your own server. It is the cheapest option at scale, but it takes the most setup and ongoing care. The most reliable method is Docker on a small Linux server.
What you need
- A VPS with at least 2 GB of RAM (providers like Hetzner, DigitalOcean, or Contabo run from about $6 to $12 per month)
- A domain name pointed at your server, so you can reach n8n over a real web address with HTTPS
- Docker and Docker Compose installed on the server
The setup, in plain steps
- Spin up the server. Create an Ubuntu 22.04 (or newer) VPS and log in over SSH.
- Install Docker and Docker Compose. These run n8n in an isolated container, which makes updates and backups far easier than a raw install.
- Point your domain at the server’s IP address with an A record.
- Create a Docker Compose file that defines the n8n container, your domain, and the environment settings (your timezone, the web address, and login details).
- Add HTTPS. A reverse proxy such as Nginx or Caddy with a free Let’s Encrypt certificate secures the connection. Caddy handles certificates automatically, which is friendlier for beginners.
- Start it with
docker compose up -d, then open your domain in a browser.
On the first screen, n8n asks you to create an owner account. Set a strong password, because this instance is now reachable from the internet.
For production use, connect a PostgreSQL database instead of the default file storage, and set up automated backups. This is the part where a lot of people get stuck, which is exactly why we offer a done-for-you setup if you would rather skip it.
Choose self-hosting if: you run high volumes, you want your data on infrastructure you control, and you are comfortable maintaining a server (or happy to have someone set it up for you).
Cloud vs self-hosted: which should you pick?
Here is the honest version.
- Low volume, no technical interest: n8n Cloud. The monthly fee buys you zero maintenance.
- High volume or strict data control: self-hosted. Once you pass a few thousand executions a month, a $10 server beats a $50+ cloud bill, and your data never leaves your machine.
- Somewhere in between: start on Cloud or local, prove the automation works, then move to self-hosted if the numbers make sense.
There is no wrong answer. The mistake is spending a week wrestling with Docker before you have even built a workflow that earns its keep.
Build your first workflow
Once n8n is open, click Create Workflow, then the + button to add your first step. Start with something tiny that proves the loop works, like a Schedule trigger that sends you a message every morning. Get one thing running end to end, and the rest clicks into place fast.
If you would rather not start from a blank canvas, you can import a ready-made workflow and have a real automation running in minutes. Our free and premium templates drop straight into any n8n instance, with a setup guide for each one.
Common setup problems (and quick fixes)
- The page will not load after self-hosting. Almost always DNS or the reverse proxy. Confirm your domain’s A record points at the server, and that ports 80 and 443 are open.
- Webhooks do not fire. n8n needs to know its public web address. Set the
WEBHOOK_URL(orN8N_HOST) environment variable to your real domain, not localhost. - Workflows reset after a restart. You are using temporary storage. Add a persistent Docker volume, or better, connect a PostgreSQL database.
- Credentials fail randomly. Check that your server’s clock is correct and your API keys have not expired. Time drift breaks a surprising number of integrations.
Frequently asked questions
Is n8n free?
n8n is open source and free to self-host. You only pay for the server you run it on. n8n Cloud is the paid, managed version, with plans from around $20 per month and a free trial.
How much does it cost to run n8n?
Self-hosted, expect about $6 to $20 per month for a small VPS, with unlimited executions. n8n Cloud starts near $20 per month for 2,500 executions. For low volume, Cloud is cheaper overall once you count your own time; at scale, self-hosting wins.
Do I need to know how to code to use n8n?
No. n8n is visual: you drag nodes onto a canvas and connect them. Some advanced steps use small expressions, but you can build most automations without writing code.
Should I use n8n Cloud or self-host it?
Use Cloud if you want zero maintenance and run a few workflows. Self-host if you need high volume, full control, or want your data on your own server. Many people start on Cloud and move later.
Can someone set up n8n for me?
Yes. If you would rather skip the server work entirely, our done-for-you setup service installs n8n, secures it, and hands it over running, with a walkthrough included.
Next steps
You now have n8n running, whichever path you chose. The fastest way to see real value is to import a workflow that solves an actual job instead of building from scratch.
- Browse ready-made n8n templates you can import in minutes.
- Read our step-by-step automation guides for specific workflows.
- Or, if setup is not how you want to spend your week, let us set it all up for you.