n8n is freemium. Check the official pricing page for current tiers and limits.

What is n8n best for?

Developers and ops teams who want a workflow tool without vendor lock-in AI-heavy automations where you want to mix LLM agents and traditional integrations Internal tools where data residency or self-hosting is a hard requirement

What are the main downsides of n8n?

License is "Sustainable Use" (fair-code), not OSI-approved open source — read the fine print before commercial redistribution UI/UX still trails Make.com on polish for non-developers Self-hosting is "free" in license cost only; ops, upgrades, and SSO add real bills

Source-available workflow automation with native AI agent nodes — self-host or use n8n Cloud. See our review for the full pros and cons.

n8n review — Workflow Automation

What it is

n8n is a workflow automation platform that sits in the same ring as Zapier and Make.com but plays a different game: source-available, self-hostable, and built for people who are comfortable seeing — and writing — code when needed. Workflows are visual graphs of nodes; each node is a typed integration, a control structure, or a code block. Released under the fair-code “Sustainable Use License”, it can be self-hosted free for internal use, run in n8n Cloud, or embedded by ISVs under a separate commercial license.

n8n includes AI Agent nodes, LangChain integrations, vector-store nodes, and tool-calling primitives alongside its conventional automation nodes.

Who it’s for

n8n is a strong candidate for developers, indie builders, and small ops teams that want visual automation with the option to self-host. It’s especially relevant for anyone building AI agents that also need conventional integrations — query a Postgres database, post to Slack, write to S3 — because it treats LLMs as another node type rather than the center of the product.

It’s a poor fit for non-technical solo operators who genuinely need zero-config and don’t have anyone to run a server. Those people belong on Zapier or Make.

Strengths

Documented self-hosting. n8n documents Docker and npm deployment paths; production readiness still depends on the operator’s database, queue, backup, upgrade, and security choices.
AI-native without being AI-only. Agent and tool-calling nodes coexist with HTTP, database, and SaaS integrations. The same workflow can call Claude, hit a Postgres, send a Telegram message, and update Airtable.
Code escape hatch. Function nodes accept arbitrary JS or Python. When no-code runs out, you don’t have to migrate.
Execution-based cloud billing. n8n Cloud counts workflow executions rather than each step as a separate task; whether that costs less depends on the workflow and current plans being compared.
Real affiliate economics. 30% recurring × 12 months on cloud signups is one of the better deals in the category.

Weaknesses / Watch out

“Open-source” is a marketing word here. The Sustainable Use License restricts what counts as “internal business” use and forbids competing as a multi-tenant service. If you’re a consultancy reselling n8n-as-a-service, talk to a lawyer first.
Self-hosting drift. The free tier of self-hosting omits SSO, audit logs, and external secrets — you’ll either upgrade to the Enterprise license or end up writing duct tape.
UX gaps. Branching, error handling, and sub-workflow re-use are functional but visibly less polished than Make.com.
Lock-in vector. Workflows are JSON-portable but the node ecosystem is n8n-specific. Migration to Activepieces or Windmill means rewriting.

Best paired with

Anthropic Claude or OpenAI as the LLM backend behind the AI Agent node — keep the model choice swappable rather than hard-coded.
Supabase or Postgres for state, vector storage, and audit logs your workflows can write to.
Activepieces as a comparison candidate when evaluating fully OSI-licensed alternatives.

Lock-in score

Medium. Workflow JSON exports cleanly and the integrations follow predictable patterns, but every n8n-specific node (the AI Agent node, the LangChain wrappers, custom community nodes) has to be rewritten when you migrate. If lock-in worries you, the practical mitigation is: keep complex business logic in code nodes (portable) rather than chains of n8n-specific nodes (not portable), and document your workflows alongside the code that calls them.

Compare n8n head-to-head

Still deciding? See how n8n stacks up against the tools it’s most often weighed against:

n8n vs Zapier — self-host engine vs the polished category leader
n8n vs Make — AI-native self-host vs the slick visual canvas
Activepieces vs n8n — MIT-licensed challenger vs the mature default

Verdict

Lean n8n when self-hosting and visual automation must coexist. It fits teams that want code escape hatches and AI nodes without giving up a visual workflow surface. Teams that prioritize a fully managed, non-technical experience should also evaluate Zapier or Make. The affiliate relationship does not determine this recommendation.

Sources