Marketplace · Workflow

Deploy n8n in one click.

The self-hosted workflow automation platform. We review it, secure it and run it in production for you. Pick a region in Switzerland, France or Germany, or reach your own machines through a secure tunnel. We keep it patched, backed up and online. You just build workflows.

★ 187k stars · Sustainable Use · TypeScript · tested versions · shipped with a runbook

LicenseSustainable Use Stars187,035 LanguageTypeScript CategoryWorkflow Source github.com/n8n-io/n8n ↗ Website n8n.io ↗

What is n8n?

One of the most popular workflow automation tools anywhere, source-available and built for self-hosting.

n8n is a source-available workflow automation platform. You build workflows on a visual canvas: nodes for 400+ integrations, wired together with branching, error handling and scheduling. When a prebuilt node isn’t enough, you drop into code. Webhooks trigger workflows from anywhere, and its AI nodes let you build LLM-backed automations on the same canvas.

A workflow tool ends up holding the keys to everything else: API tokens for your CRM, database passwords, OAuth grants for your email and your files, plus every record that flows through a workflow. Self-hosting n8n keeps those credentials and payloads on infrastructure you control instead of a third-party automation vendor’s cloud.

The catch: self-hosting means someone has to run it. Reverse proxy, TLS, a public webhook endpoint to secure, upgrades that ship frequently, security patches, backups of every workflow and credential your team depends on. That someone is usually you, at the worst possible time.

n8n, without the ops.

Everything below is what you’d otherwise build and babysit yourself.

Residency

Your credentials stay where you put them.

Deploy to ch-zh1 (Zurich), fr-pa1 (Paris) or de-fr1 (Frankfurt). Workflows, stored credentials and execution data stay in the region you choose, under Swiss or EU law and in line with GDPR.

Secured

Reviewed before it ships.

Our n8n package is reviewed, secured and locked to versions we have tested, and it ships with a runbook. We track CVEs upstream and patch them fast.

Your tools

Reach systems behind your firewall.

Workflows often need your internal databases and services. We drop in a secure tunnel so n8n reaches them without you exposing anything to the internet. Your systems stay inside your own network.

Managed

TLS, upgrades, scaling: handled.

Certificates issued and renewed, rolling zero-downtime updates, instant rollback, health checks. n8n ships new releases fast; we keep you current without breaking your team’s workflows.

Backups

Backups you can actually restore.

Offsite backups of your workflows, credentials and execution history. We run restore drills, not just snapshots.

No lock-in

Leave whenever you want.

n8n is source-available and your exit is real: workflows export as JSON and your data leaves with you, in usable form. Pilae runs it for you. It never owns it.

Self-hosting n8n: DIY vs Pilae.

Both paths end with n8n in production. Only one of them ends there this afternoon.

Self-hosted DIY On Pilae
Initial setup Docker, reverse proxy, DNS, auth. An afternoon if nothing fights back One click, live in minutes
TLS certificates Issue, wire up, remember to renew Issued and renewed automatically
Upgrades Frequent releases to track, test and apply yourself Tested versions, rolled out with instant rollback
Security patching You watch the CVE feed Upstream tracked, CVEs prioritized
Backups cron + object storage + hope Offsite, verified with restore drills
Data residency Wherever your VPS happens to be You pick: Zurich, Paris, Frankfurt, or your own racks
3 a.m. failures Yours Ours
Webhook endpoints Expose a public URL and secure it yourself TLS-terminated endpoint from the first minute
Reaching internal systems VPN gymnastics or holes in the firewall Secure tunnel; your systems stay inside your own network

From catalog to production in three steps.

No servers to set up, no configuration to write. The platform work is already done.

01

Pick n8n.

Find it in the catalog: reviewed, secured, locked to tested versions, runbook included.

02

Choose where it runs.

A Pilae region in Switzerland, France or Germany, or your own machine connected through a secure tunnel. Same console either way.

03

Deploy and connect your tools.

One click to production with TLS and backups from day one. Wire up your first integrations, set your webhooks, invite your team, done.

Your workflows hold the keys to everything. Keep them close.

Every n8n deployment is pinned to the region you choose. Encryption, dedicated VLANs, and the option to hold your own encryption keys for regulated workloads. Or reach your own machines through a secure tunnel.

ch-zh1 ready
fr-pa1 ready
de-fr1 ready

Deploying n8n: the questions we get.

If yours isn’t here, reach out and we’ll answer it, usually the same day.

What’s the easiest way to self-host n8n?

Deploying it through a managed platform. On Pilae you pick n8n from the catalog, choose a region, and click deploy. TLS, backups, patching and upgrades are handled for you from the first minute. You get self-hosting’s control without its ops.

Is n8n open source?

Not strictly. n8n is source-available under its Sustainable Use License. The code is public and you can self-host it, but it isn’t an OSI-approved open-source license. What matters for your exit: workflows export as JSON and your data leaves with you, in usable form.

Can n8n run AI and LLM workflows?

Yes. n8n ships AI nodes for building LLM-backed workflows and agents on the same visual canvas as the rest of your automations. Pair it with Open WebUI from the same catalog to keep the whole AI stack on infrastructure you control.

Where do my n8n credentials and workflow data live?

In the region you choose: Zurich, Paris or Frankfurt. Workflows, stored credentials and execution data stay there, encrypted. For regulated workloads you can hold your own encryption keys.

How do n8n updates and security patches work on Pilae?

We track upstream, prioritize CVEs, and ship updates locked to versions we have tested, rolled out with zero downtime and instant rollback. You stay current without watching the release feed.

Can I move my n8n deployment off Pilae later?

Yes, and that’s by design. Your workflows export as JSON, and your credentials and execution data exit with you in usable form. No proprietary formats, no lock-in.

Runs well next to.

Build your stack from the same catalog. One console, one click each.

n8n, without the ops.

Deploy it in minutes, keep your data in the country you choose, and leave whenever you want. Your data goes with you.

Explore the catalog →