n8n is a workflow runner, so it has to be running for anything to happen: scheduled triggers fire on its clock and webhooks arrive on its URL. Self-hosting it means a persistent process, a database, and for anything serious a queue mode with separate workers. A platform that sleeps idle applications will silently stop the automations it was installed for.
3 providers document support for n8n, listed alphabetically. Mostly platform as a service, shared hosting and containers as a service, of 5 categories in all. 116 records do not record this field, and cannot appear here either way.
E
- Elestio
Elestio is managed hosting for open-source software on dedicated virtual machines, provisioned into a third-party cloud or into the customer's own account.
O
- Opalstack
Developer-owned US host running PHP-FPM, Node, Python and Ruby stacks with full SSH on every plan, plus VPS and bare-metal tiers.
S
- Sliplane
German Docker hosting that bills for the server rather than the container, so unlimited services can share one machine, with managed Postgres and S3 storage.
Do I need special hosting for n8n?
In most cases, no. n8n runs on any host that supports its runtime. This list is shorter than that: it holds the providers that document n8n themselves, with an installer, a guide or a maintained image. Other hosts may run it without mentioning it.
What should I check before hosting n8n?
The runtime versions on offer, how deploys work, whether there is a shell for command-line tools, where cron jobs run, and which databases come managed. Check backups too, and how to move away later.
Who is the best n8n hosting provider?
We can't tell from here. A host that suits a small agency site can be wrong for an API with users in Asia and Europe. The list is alphabetical and nobody paid for a place on it. The guide covers what to compare.