n8n and open-source automation: a business guide

In short: if you want open-source workflow automation for your business, n8n is the reference tool. You can self-host it or use n8n Cloud, connect your store, CRM and ERP, and you pay per workflow execution rather than per step. It pays off when someone owns it; for simple flows without in-house IT, Make or Zapier are faster.

Key takeaways

n8n's code is public and its license allows free use for internal business processes, not reselling it as a service.
Self-hosting gives you control over data, but updates, backups and security become your job.
Cost depends on the billing unit: n8n counts executions, Make counts operations, Zapier counts tasks.
Self-hosting doesn't make you GDPR-compliant by default: the external apps your workflows send data to matter too.
Start with the process, not the tool: one frequent, measurable workflow.

An online store growing from a hundred to a thousand orders a month, or a B2B company with a sales team, soon hits the same wall: data retyped between the store, the ERP and the CRM, quotes rebuilt from scratch, reports assembled by hand every Monday. If you still need to work out what to automate, start with the guide to business process automation.

What is open-source automation, and what does n8n do?

Open-source automation means using platforms with public code, which you can install on your own servers, to connect business software without manual steps. The best-known project in this space is n8n.

n8n is a workflow automation platform with a visual editor. A workflow is a sequence that starts with a trigger, such as a new order, and continues with actions like updating the ERP, alerting the warehouse and emailing the customer. Each step is a node: an app, a database, an API or an AI model; where the editor falls short, you add code. It's also the tool I use for this blog's publishing workflow.

Is n8n actually open source? What the license says

Technically, no: n8n is source-available. The Community edition uses the Sustainable Use License, which allows free use and modification for internal business purposes but restricts commercial use towards third parties.

According to n8n's official license FAQ, you can use it for free if workflows are created or edited only by people in your organization. You can also build automations for clients on your own instance and run n8n behind the scenes of your own product. You can't offer it as a service where clients build their own workflows. SSO, environments, projects, external secrets and Git-based version control need a paid plan, even when self-hosted (n8n documentation).

Does open source mean no vendor lock-in?

It reduces lock-in; it doesn't remove it. Vendor lock-in is a dependency on one supplier that makes switching tools expensive. In n8n, workflows are JSON files you can export and import into another instance (n8n documentation). A self-hosted install without a license key runs as the free Community edition; adding a Business or Enterprise key unlocks those editions' features on the same install (n8n hosting guide).

Two practical points. Exported files include credential names and IDs, and HTTP Request nodes imported from cURL may contain authentication headers: clean them up before sharing them with a supplier. And in my view the costliest lock-in isn't the tool, it's business logic buried in workflows nobody documented: for every flow, write down what it does, who owns it and which systems it touches.

What are the alternatives to n8n, open source and otherwise?

Alternatives fall into self-hostable projects, such as Activepieces and Node-RED, and proprietary cloud services, such as Make and Zapier.

Tool	Model	Where it runs	How you pay	Best for
n8n	Public code, Sustainable Use License; paid enterprise features	Your servers or n8n Cloud	Community edition is free; cloud is billed per workflow execution	Complex flows, APIs, AI agents, sensitive data
Activepieces	MIT license for the core; enterprise folders under a separate license	Your servers	Infrastructure and maintenance	Teams that want a strictly open-source license
Node-RED	OpenJS Foundation project, born at IBM	Servers, cloud or low-cost hardware like a Raspberry Pi	Infrastructure and maintenance	Event-driven flows, machine and sensor data
Make	Proprietary subscription	Vendor cloud	Operations, converted into credits: every module run counts	Marketing and ops teams, visual flows
Zapier	Proprietary subscription	Vendor cloud	Tasks: every completed action counts, triggers don't	Short flows between popular SaaS apps

Sources: Activepieces license, Node-RED, Make, Zapier. In my view, for connecting a store, a CRM and marketing tools, n8n is still the most practical starting point.

Open-source AI frameworks or automation platforms: what does a business actually need?

They are two different categories, and mixing them up leads to the wrong tool. Search for "open-source frameworks to automate work" and you'll often find machine learning libraries such as TF-Agents, Gym or ReAgent. They're built for developers and data scientists who train models with reinforcement learning, where a system learns by trial and error which decisions maximize a goal. They don't connect an online store to an ERP.

Tool	What it is	Project status	Who it's for
TF-Agents	TensorFlow library for reinforcement learning and contextual bandits	Public code on GitHub	Data science teams training models
Gym / Gymnasium	Standard set of simulation environments for reinforcement learning	Gymnasium is the maintained fork of OpenAI's Gym, run by the Farama Foundation	Model research and development
ReAgent (Meta)	Platform for reinforcement-learning-based decision systems	Archived and no longer maintained	No new projects
n8n, Activepieces, Node-RED	Workflow platforms that connect apps, data and AI models	See the table above	Teams automating business processes

Sources: TF-Agents, Gymnasium, ReAgent.

A machine learning framework only makes sense if you need to build your own model, for example to optimize pricing or recommendations, and you have a team that can train and maintain it. For processes you need a workflow platform, which can still use AI: n8n lets you add models from several providers, such as OpenAI, Anthropic and Google, with tools and memory, and connect an AI agent to MCP servers (n8n AI documentation). MCP (Model Context Protocol) is a standard protocol that lets an AI agent reach external tools and data; I cover it in the guide to orchestrating AI agents. Either way the software is free, but adaptation and maintenance remain the real costs.

Self-hosted or cloud: which is right for your business?

Self-hosting means running the software on servers you control; managed cloud is the same platform hosted and maintained by the vendor. Go cloud if you lack dedicated technical skills, and self-host if you have them and need control and customization, as n8n's own decision guide suggests.

Aspect	n8n Cloud	Self-hosted n8n
Getting started	Instant	Server, Docker, domain and certificate to set up
Updates and patches	Handled by the vendor	Handled by you or your partner
Backups	Handled by the vendor	Yours to design: database, credentials, workflows
Control over data and network	Limited to the service's options	Full
Cost	Subscription based on executions	Free Community edition, plus servers and maintenance hours

A practical rule: if nobody can say who will update n8n next month, start in the cloud.

What do you need to self-host n8n?

You need sysadmin skills, not just user skills. n8n's documentation recommends self-hosting for expert users and warns that mistakes can lead to data loss, security issues and downtime (Docker installation guide). The pieces to own:

Servers and containers: n8n installs with Docker or Docker Compose; the npm install is meant for development and testing. Someone has to configure the domain, HTTPS and server resources.
Database: by default n8n stores credentials, executions and workflows in SQLite; you can configure PostgreSQL instead (database documentation).
Growing volumes: in queue mode, a main instance receives triggers and webhooks and hands executions, through Redis, to multiple workers; you scale by adding or removing workers (queue mode documentation).
Error handling: each workflow can have an error workflow that starts with the Error Trigger node when an execution fails and, for example, sends an email or Slack alert (n8n error handling documentation).
Updates and backups: the part most often neglected; see the security section.

The cloud has technical limits too: each plan has a memory cap (640 MiB of RAM on Starter), and workflows that process a lot of data can exceed it and crash the instance (n8n Cloud documentation). If you expect large files or big catalog exports, check this before picking a plan.

How much does automation with n8n, Make or Zapier really cost?

The billing unit matters more than the entry price. n8n counts executions: one workflow run is one execution, regardless of the number of steps (n8n pricing). Make counts operations, which it converts into billing credits: every module run, including the trigger check (Make Help Center). Zapier counts tasks: every completed action, while triggers are free.

An example scenario: an online store with 1,500 orders a month and an eight-step flow per order.

n8n: 1,500 executions a month.
Make: about 10,500 operations for the 7 action modules (7 × 1,500), plus one per trigger check.
Zapier: about 10,500 tasks (7 actions × 1,500, trigger excluded).

As of November 2026, n8n Cloud Starter starts at €20 a month for 2,500 executions and Pro at €50 for 10,000 (billed annually); Zapier Professional starts at $19.99 a month for 750 tasks. Pricing changes often, so always check. When self-hosting, the license is free, but budget the time spent installing, updating and fixing errors as a fixed line item.

Security: what changes when you run n8n yourself?

When you self-host, security becomes your operational responsibility. The platform holds the credentials for your store, CRM and email: if it's compromised, an attacker can reach all of them.

A concrete case: CVE-2026-21858, published in January 2026 with a CVSS score of 10.0, let even an unauthenticated attacker read files on the server through certain form-based workflows, in versions from 1.65.0 up to, but not including, 1.121.0. It's a textbook case for proactive cybersecurity. The baseline controls:

scheduled updates and a named owner who follows security advisories;
editor available only over HTTPS and, where possible, only from the company network or a VPN;
few users allowed to create or edit workflows;
backups of the database and credentials, with a tested restore.

Are n8n, Make and Zapier GDPR-compliant? Where your data goes

No tool is GDPR-compliant on its own: compliance depends on how you use it. What changes is who processes the data and where it's stored.

Tool	Where the data lives	What the vendor says	What to check
Self-hosted n8n	On your servers	n8n is neither controller nor processor of your workflow data	Usage telemetry is on by default and is switched off with environment variables
n8n Cloud	Vendor infrastructure	n8n is both controller and processor; the DPA with Standard Contractual Clauses is part of the terms of service	The list of sub-processors
Make	US or EU data center, chosen per organization	The location can't be changed after the organization is created	Some AI features send requests to the US even in an EU zone
Zapier	AWS servers in the United States	EU-only storage isn't available	Transfers rely on the EU-US Data Privacy Framework

Sources: n8n privacy and security, Make organizations, Make AI data zones, Zapier data privacy.

Two practical consequences. First, even with n8n on your own servers, a workflow that sends personal data to a cloud service outside the EU creates a transfer you need to assess; self-hosting covers the platform, not the apps it connects. Second, before the pilot, map every flow that touches customer or employee data (which data, to which services, on what legal basis) and bring in your DPO or privacy advisor, as with any compliance automation project.

When should you choose Make or Zapier over n8n?

Make or Zapier are the better choice when fast setup and a non-technical team's autonomy matter more than cost at volume and control over data.

Zapier: short flows between popular apps, low volumes, no technical staff.
Make: richer visual logic with filters and routers, run by marketing or operations.
n8n: growing volumes, long flows, custom API calls, AI agents or strict rules on data.

A mixed path often works: validate a process on Make, then move it to n8n once volume makes operation-based billing too expensive.

Practical examples for e-commerce and B2B companies

Typical scenarios, not client cases:

E-commerce: a Shopify or WooCommerce order creates the ERP document and invoice and alerts the warehouse.
E-commerce: a review request a few days after delivery, with negative replies routed to customer service.
B2B: a website lead is enriched, added to the CRM and assigned to the right sales rep, with a reminder if it goes unanswered.
B2B: price lists and stock synced between the ERP and a customer portal, with n8n as the hidden engine, a use the license allows.

You can plug AI agents into these flows to classify requests or draft a first reply, leaving the decision to a person.

Will n8n connect to your ERP or online store?

Almost always, if the software has an API, the interface it uses to expose data and functions to other programs. n8n's catalog lists more than 2,000 integrations with apps, services and APIs (integrations catalog); when there's no ready-made integration, the HTTP Request node can query any app with a REST API (HTTP Request node documentation).

Before you start, ask your ERP vendor three things: whether there's an API, whether it's included in your license or paid, and which data it exposes (orders, customers, price lists, stock). If there's no API, the options are scheduled file exports, database access agreed with the vendor or, as a last resort, AI agents that use the browser on portals with no integrations.

How to apply it in your company: first steps

Map three repetitive processes with monthly volume, minutes per item and common errors.
Pick one with clear rules and data that's already digital: orders, leads or quotes.
Decide where it runs: who updates the platform, what personal data flows through it, how many executions a month.
Build a pilot with an error workflow that alerts you when an execution fails, and a named owner who acts on it.
Measure after 30 days: hours saved, errors avoided and cost per execution, using the right KPIs, then decide whether to extend it.

See how I approach these projects in the solutions section, and find more articles in the automation archive.

Mistakes to avoid

Installing n8n and forgetting it: without updates and backups, license savings are paid back in risk.
Estimating costs after the fact: work out executions, operations or tasks before you pick a plan.
Starting without a baseline: without hours and errors measured upfront, you can't tell if the pilot worked.
Confusing frameworks with platforms: a machine learning library won't connect your store, CRM and ERP.

Frequently asked questions (FAQ)

Is n8n free for businesses?

The self-hosted Community edition is free as long as only people in your organization create and edit the workflows. n8n Cloud is paid, and so are features such as SSO, environments and external secrets.

Should I self-host n8n or use n8n Cloud?

Cloud makes sense if nobody on your team can look after servers, updates and backups. Self-hosting makes sense if you have in-house skills or a partner, high volumes or strict rules on where data lives.

When is Make a better choice than n8n?

When the people building the flows are marketing or operations staff without developers, volumes are moderate and you don't want to run infrastructure. The catch is cost, which grows with operations because every module run counts.

Zapier or n8n for an online store?

Zapier works for short flows between popular SaaS apps and low order volumes. With long flows and high volumes, task-based billing climbs fast because every completed action counts. n8n counts one execution per workflow run and, at the same volume, often costs less.

Is self-hosting more secure than the cloud?

Only if you run it well: you get more control over data, but updates, access and backups are on you. CVE-2026-21858, rated CVSS 10.0, affected n8n instances that hadn't been updated. Without a patching process, self-hosting is less secure, not more.

Can I use n8n to deliver automations to my B2B clients?

Yes, as long as clients don't create or edit the workflows: the license lets you build automations for them on your own instance and run n8n as the hidden engine of a portal. Letting clients build flows or reselling n8n as a service requires a commercial license.

Is n8n GDPR-compliant?

It depends on how you use it. When self-hosted, n8n doesn't process your workflow data, which stays on your servers: compliance is on you, including the external apps you send data to. On n8n Cloud the vendor is both controller and processor, and the DPA with Standard Contractual Clauses is included in the terms of service.

Sources

If you want to find out which automation stack fits your business, book a free diagnosis.