Automation and integrations decision

n8n Cloud

A narrow, self-hosted workflow runner (webhooks, HTTP nodes, code steps, and logging) is realistic for a small team to build and maintain, but reproducing n8n Cloud's breadth (UI polish, 400+ nodes, templates, hosted scaling, AI credits, and enterprise features) is substantial and better justified when those needs are critical.

Visit website
Subscription$20/month ✓ verified
Initial build80 hours
Monthly upkeep8 hours + $40
Evidence2/3 runs agree

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need — the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship.

Code n8n Cloud publishes itself

Not a way out of the subscription — these are the vendor’s own repositories. Worth a look for how they build, and for anything you would have to integrate with.

What a replacement has to do

  • Receive trigger (webhook/schedule) → run node graph (HTTP/code/AI) → store/stream execution results → retry/alert on failure

What it still won’t have

  • Hosted UI, templates and pre-built node catalogue
  • Managed scaling, observability and audit/log streaming
  • Built-in AI credits and assistant preview
  • Enterprise features (SSO, extended retention, dedicated SLA)
  • Broad community & vendor support channels

What remains hard

  • Brand trustTop 50 Github. Our 199.3k stars place us among the most popular projects.
  • Brand trust4.7/5 stars on G2.
  • Infrastructure at scalen8n handles up to 220 workflow executions per second on a single instance.
Read the build prompt

First-year cost

Keep paying

Paying ischeaper in year one.

On cash alone, building overtakes the subscription at 3 seats.

Paid seatsseats

Money you would actually spend

Keep paying

Subscription price × seats × 12

Build it

AI build APIs + hosting

Time you would spend

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal hosted workflow runner in Node.js (Express) + Postgres + Redis + worker pool. Scope in: REST API to create/update JSON workflow graphs, webhook and cron triggers, an execution worker that runs HTTP request nodes and executes user JS/Python code safely (use a sandbox like vm2 or spawn isolated subprocesses), execution queue with Redis and BullMQ, store execution logs in Postgres, basic web UI to list workflows and recent executions, and simple retry/error notification via email. Out of scope: full visual drag-and-drop editor, 400+ built-in integrations, enterprise SSO, paid billing. Include input validation, authentication (JWT), rate limiting, CI tests for worker and API, and sane error handling and retries.
How we checked5 sources · 2/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 5 cited sources+3
  • Price verified on pricing page+3
  • Hard moats found in the evidence-3
  • Evidence score60

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time — so the same evidence always produces the same number.

How scoring works →

Cited sources · 5

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 3 moats quoted from the page