n8n Cloud vs self-hosted for Pipedream migrations

n8n Cloud vs self-hosted is the first decision after picking n8n as your Pipedream replacement, and for Pipedream users the deciding factor is usually code. n8n Cloud runs your workflows with no servers to manage, but its Code node can load only crypto and moment, and Python can't import anything. Self-hosted n8n lets you install packages, at the cost of running and updating it yourself.

The short answer

• Mostly webhooks, schedules, app nodes and plain JavaScript: n8n Cloud.
• Code steps that import npm packages or Python libraries: self-hosted, or rewrite those steps.
• Need Git, multiple environments or SSO: check the plan table below; some features are Business or Enterprise only.

Comparison

	n8n Cloud	Self-hosted Community Edition
Price	Paid plans by monthly executions	Free (you pay for the server)
Setup	Sign up	Docker or npm; you handle updates, backups, TLS
npm in Code node	crypto, moment only	Packages you install and allow-list
Python imports	None	Allow-listed packages via task runners
Execution time	Plan maximum	Your server
Custom nodes, unverified community nodes	Self-hosted only (verified community nodes work on Cloud)	Yes
Variables ($vars)	Pro, Enterprise	Not in Community Edition (Business, Enterprise)
Git source control	Enterprise	Not in Community Edition (Business, Enterprise)
Public API	Yes (not during trial)	Yes
License	Service terms	Sustainable Use License (fair-code)

Sources: n8n pricing, Code node, Community Edition features, Variables, source control, API authentication.

n8n Cloud plans

As listed on n8n.io/pricing on October 21, 2026 (EUR, billed annually): Starter €20/month for 2.5K executions, Pro €50/month for 10K executions, Enterprise on request. Business (€667/month, 40K executions) is self-hosted only. Pricing is per workflow execution regardless of the number of steps. Monthly billing costs more; check the page for current numbers.

Compared with Pipedream's credits (one per 30 seconds of compute at 256 MB), per-execution pricing mainly helps long-running workflows: a run costs one execution however long it takes. Very frequent short runs cost one unit per run on both.

Self-hosting

The Community Edition is free and includes almost all features (docs); it lacks things like Variables, environments, external secrets, SSO, credential sharing and Git. Registering it with an email unlocks a few extras (folders, debug in editor, custom execution data).

Quick start from the Docker docs:

docker volume create n8n_data
docker run -it --rm --name n8n -p 5678:5678 \
  -e GENERIC_TIMEZONE="Europe/Berlin" -e TZ="Europe/Berlin" \
  -e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true \
  -v n8n_data:/home/node/.n8n n8nio/n8n

That's a test setup. For production, add a database, TLS, backups of the volume and of N8N_ENCRYPTION_KEY, and, if you need npm or Python packages, the n8nio/runners sidecar (npm guide). n8n recommends self-hosting for expert users. Its Docker page also points to Docker Compose for a fuller setup.

Licensing

Self-hosted n8n uses the Sustainable Use License, a fair-code license. Use is limited to your own internal business purposes or non-commercial and personal use; consulting is explicitly allowed. Offering n8n to others as a product, for example letting your customers connect their accounts and build workflows in it, is not. For most teams migrating their own workflows this changes nothing.

Deciding from your Pipedream export

Count the code steps that import packages. Our free report lists them per workflow and marks what works on n8n Cloud and what needs self-hosted n8n. Next: migrate Pipedream to n8n, or compare platforms in Pipedream vs n8n.

Not affiliated with n8n or Pipedream.