Self-hosted n8n on a Frankfurt VPS
Updated
The n8n app gives you a cloud server in Frankfurt with n8n installed, so you can build and run your own workflow automations a few minutes after the server boots, with no per-execution pricing.
Your workflows, credentials and logs stay on a server you control in Germany.
What is installed
- n8n, the open-source workflow automation tool, set up to start with the server.
- A standard Linux system underneath, with full root access.
n8n has hundreds of built-in nodes for common apps, plus generic HTTP, webhook, code and database nodes. It also supports AI agent workflows that call language model APIs.
Which plan to start with
n8n is light when idle and busier while workflows run.
- Personal automations and small teams: the smallest Standard plan is a good start.
- Many workflows, large payloads or parallel runs: pick 2 to 4 GB of memory.
- Heavy data processing: a CPU-optimised (c) or memory-optimised (m) plan.
Standard
Shared vCPU for websites, apps, VPNs and development.
| Plan | vCPU | RAM | Disk | Traffic | Hourly | Monthly cap |
|---|---|---|---|---|---|---|
| S0 | 1 | 1 GB | 15 GB | Unmetered | €0.0056 | €3.49 |
| S1 | 1 | 2 GB | 30 GB | Unmetered | €0.0080 | €4.99 |
| S2 | 2 | 4 GB | 40 GB | Unmetered | €0.0144 | €8.99 |
| S3 | 2 | 8 GB | 50 GB | Unmetered | €0.0200 | €12.49 |
| S4 | 4 | 8 GB | 80 GB | Unmetered | €0.0288 | €17.99 |
| S5 | 4 | 16 GB | 100 GB | Unmetered | €0.0400 | €24.99 |
You pay by the hour from a prepaid balance, capped at the monthly price. Resize when executions start to queue.
Signing in after boot
- Create a server in the console and choose n8n as the app.
- When the server is running, give the installation a few minutes.
- Open the server's address in your browser. On first visit, n8n asks you to create the owner account.
- Sign in with that account and create your first workflow.
Create the owner account right away. Until you do, anyone who finds the address could claim it. For terminal access, connect with SSH as root, see connect with SSH.
First steps
Give n8n a domain and HTTPS
Webhooks and OAuth sign-ins for many services need a public HTTPS address. Create DNS records for the server's IPv4 and IPv6 addresses, then serve n8n behind a reverse proxy with a certificate. Our Caddy reverse proxy guide shows a simple setup. Set n8n's public URL to the new domain so webhook links are correct.
Restrict access
- Attach a free firewall that allows SSH and HTTPS only.
- Allow SSH from your own address only, if you have a fixed one.
- Use a strong password for the owner account and invite other users with their own accounts.
Back up your workflows
Workflows and stored credentials live on the server. Turn on daily backups for 20% of the server price, take a snapshot before upgrading n8n, and export important workflows now and then. The backup strategy guide has more ideas.
Connect to private systems
If n8n needs to reach databases or internal APIs, put them in the same private network. Those servers do not need public IPs at all. A NAT gateway gives them outbound internet access for updates.
Ideas for first workflows
If you are new to n8n, start with something small that saves time every week:
- Form to CRM: send new website form entries to your CRM or a spreadsheet and post a message to your team chat.
- Invoice handling: collect invoice emails, save the attachments to storage and log them in a table.
- Monitoring alerts: call a health endpoint on a schedule and notify you when it fails.
- Data sync: copy new records from one SaaS tool to another every few minutes.
- AI helpers: summarise incoming support emails or tag them before they reach a person.
Build one workflow, watch its executions for a few days, then add the next. The execution list in n8n shows where a run failed and with what data.
Why self-host n8n on Wolkra
- No per-execution fees. One server price, billed hourly and capped monthly, however many workflows run.
- Unmetered traffic. Moving files between APIs does not create a bandwidth bill. Ports go up to 10 Gbit/s, shared, with fair use. See unmetered bandwidth.
- Data in Germany. Useful when customer data must stay in the EU. See EU VPS and GDPR.
- Low latency across Europe from the centre of Europe, for webhooks from European services.
Planning a larger automation setup? Read n8n hosting for patterns such as separate database servers and staging copies.
Start your n8n server
Create an account, add balance by card or crypto, and choose the n8n app. Your automation server in Frankfurt is ready in minutes.
Frequently asked questions
What is n8n?
n8n is an open-source workflow automation tool. You connect apps and APIs with nodes on a visual canvas and run the workflows on your own server.
Is there a limit on workflows or executions?
Wolkra sets no limit. You are bound only by the server's CPU, memory and disk, and by the fair-use policy on traffic.
Which plan should I use for n8n?
A small Standard plan runs a handful of workflows. Choose 2 to 4 GB of memory if you process large files, run many executions in parallel or use AI nodes.
How do webhooks reach my n8n server?
Point a domain at the server and serve n8n over HTTPS. External services then call webhook URLs on that domain.
Does my automation data leave Germany?
Workflows, credentials and execution data stay on your server in Frankfurt. Data only leaves when a workflow sends it to an outside service.