Research report · verified 22 Sep 2026
n8n license-boundary audit.
n8n is a workflow-automation product that can connect systems and run optional AI steps. This report adds it as a source-available comparison to Activepieces CE, not as an OSI-style open-source substitute.
Finding
Classification: source-available/fair-code; not OSI-style open source. This is a code-license taxonomy, not legal advice. n8n’s LICENSE.md names the Sustainable Use License v1.0 for covered code and excludes non-master branches, .ee. files/directories and third-party components. The official FAQ says n8n does not call itself open source because OSI licenses cannot limit use; it identifies paid customer access and white-labeling as examples that need a separate commercial agreement.
Public source, self-hosting and a free Community edition do not change this classification. The Community/Registered Community/Business/Enterprise split is a product-edition distinction; see the edition comparison. Check a material deployment with n8n or qualified counsel.
Operational boundary
n8n uses workflows made of triggers, processing nodes and actions. Official documentation includes selected nodes for HubSpot, Jotform, Gmail, SendGrid, X, Facebook Graph API and Google Analytics, plus HTTP/API tooling. This supports documented connector availability, not universal connector coverage or production suitability. Every chosen flow still needs a check of operations, OAuth scopes, API versions, target-service terms and data paths.
n8n is an orchestration layer. It is not the system of record for contacts, consent, suppression, campaigns, deliverability or marketing strategy. Do not treat an AI Agent node or Agent Builder as an autonomous marketing operator. Agent Builder and some self-hosted agent capabilities are Preview; self-hosted agents currently do not support queue mode.
n8n and Activepieces CE
| Topic | n8n | Activepieces CE |
|---|---|---|
| License category | Sustainable Use License for covered code; source-available/fair-code, not OSI-style. Enterprise and third-party scope require separate checks. | MIT for CE/outside named EE paths in the prior verified report; OSI-style for that named CE/code scope, not every repository path. |
| Layer | Visual workflow and optional AI/agent orchestration. | Visual workflow orchestration across systems a team already owns. |
| Deployment | Local Docker uses persistent data; default storage is SQLite, with PostgreSQL supported. Queue mode adds main instance, Redis, workers and database. | Prior report documented Docker Compose with app, worker, PostgreSQL and Redis. |
| Operator duties | Own hosting, access, credentials, encryption key, backups, retries, retention, target scopes and review/rollback. | Own deployment, encryption key/database backup, public webhook route, connector scopes, worker sizing, retries and review/rollback. |
The Activepieces statements above are carried from the earlier verified report, not newly re-researched in this run. See its original report and the Activepieces CE dossier.
Draft-only test plan
- Run a disposable local Docker instance with fictional data and no public URL or webhook.
- Use a Manual Trigger and a fixed content-calendar transformation; use an LLM only with an approved, separately scoped low-spend test key.
- Stop before an action node and label the local output
REVIEW REQUIRED. - Cause one harmless failure, inspect the execution and retry controls, then remove the workflow, credentials, container and test data.
No hands-on test occurred. This plan does not establish license fitness, connector behavior, reliability, deliverability, security, scale, model quality or production readiness.
Maintenance and uncertainty
The research-date release page showed n8n@2.40.5 on 21 September 2026 and a 2.41.0 pre-release on 22 September. n8n documents regular minor releases and provides a security reporting route and a self-hosted security audit. These are maintenance and process signals, not reliability or security guarantees.
- No n8n installation, node, integration, license key or workflow was tested.
- License scope is not uniform across the repository; check the package/component and intended distribution or service model.
- Connector documentation does not establish every API version, rate limit, pricing term, privacy condition, maintenance state or approval behavior.
- Reverify Activepieces CE when an edition, license or deployment decision is material.