n8n hosting: your own automation server, in one click
Pick n8n from the app catalog, name it, deploy. It runs from the official image on a Starter plan with 1 GB, gets an https address that webhooks can reach, and keeps its workflows and credentials under /data with daily backups.
What you get
- The official n8n image with the editor at your address and webhooks that work from the first minute (WEBHOOK_URL is set for you).
- Workflows, credentials and the execution history under /data, so nothing is lost on a redeploy.
- Daily backups on paid tiers, restored in one click.
- A managed PostgreSQL, MySQL, MongoDB or Redis on your private network when SQLite is not enough.
- Redeploy pulls the latest n8n release.
Sizing
n8n needs about 400 MB at rest and more while workflows run, which is why it starts on Starter with 1 GB rather than the free tier. Workflows that process files or run AI steps in parallel are happier on Standard with 2 GB. The address comes with the tier and stays awake on a paid one, so a webhook is never kept waiting.
Environment
Every n8n setting is an environment variable, and the app's Environment page is where they go: timezone, SMTP for user invites, an encryption key of your own, community nodes. The panel keeps them encrypted and restarts n8n when you save.
Frequently asked questions
Is this n8n cloud?
No, it is n8n self-hosted on a machine we run for you: the open-source edition, your data, your address, a flat price instead of a per-execution one.
Do webhooks work?
Yes. The app has a public https address and n8n is told that address as its WEBHOOK_URL, so triggers from Stripe, GitHub, Telegram or anything else reach it.
Can I use PostgreSQL instead of SQLite?
Yes. Create a managed PostgreSQL from the Databases page and put its DB_* settings in the app's environment; n8n switches on the next restart.
How do I update n8n?
Press Redeploy on the app's page: the latest image is pulled and the app restarts on the same data.
What happens on a deploy?
The repository is cloned at your branch, dependencies install, the build runs when there is one, the app starts. With auto-deploy on, every push does the same. The live console shows each step; a failed one is explained in plain words.