About n8n
n8n is a free and open fair-code licensed workflow automation tool. Easily automate tasks across different services with a visual workflow editor.
What you get
- 200+ Integrations — Connect to popular services and APIs
- Custom Functions — Write custom JavaScript functions
- Error Handling — Built-in error handling and retry logic
- Scheduling — Run workflows on schedule or triggers
- Self-Hosted — Run on your own infrastructure
- Visual Editor — Drag-and-drop workflow builder
Storage that survives a restart
n8n is deployed with a persistent volume. They keep their contents across restarts, redeploys and resource changes, and can be resized later.
- n8n_data — 2 GB — Settings, encryption key file and binary data
How deployment works
- Click Deploy n8n and sign in to your Nexent Cloud workspace (or create one - it takes a minute).
- Name the app and adjust CPU, memory and storage if the defaults don't fit; the price updates as you go.
- Nexent provisions the containers, their persistent volumes and a
*.nexentcloud.comaddress with TLS. Add your own domain afterwards from the app's settings.
Questions about n8n hosting
How much does hosting n8n cost?
$4.02 a month, or $40.24 a year. That covers 1 vCPU, 1 GB of memory, 5 GB of persistent storage and 50 GB of bandwidth, with TLS and an address included. Resources can be changed afterwards and the price follows them.
How long does it take to deploy n8n?
About 8 min. Nexent Cloud pulls the image, attaches the storage it needs and issues a certificate for its address; you do not configure a server, a reverse proxy or a certificate renewal.
Can I use my own domain?
Yes. Every app gets an address on nexentcloud.com with TLS immediately, and you can point your own domain at it afterwards from the app’s settings - the certificate is issued and renewed for you.
Is my n8n data kept when it restarts?
Yes. n8n is deployed with a persistent volume (n8n_data 2 GB), which survive restarts, redeploys and resource changes.
Can I move away later?
It is standard n8n, running in a container from the upstream image - not a fork and not a managed variant. Your data is on a volume you can back up and take with you.