Source-available comparison · verified 22 Sep 2026
n8n: workflow automation with a license boundary.
n8n can connect systems and run workflow or AI steps. It is a source-available/fair-code product, not an OSI-style open-source alternative to Activepieces CE.
License and product scope
License classification. The repository’s Sustainable Use License covers code except stated exclusions, including .ee. files/directories and third-party components. n8n’s license FAQ describes this as fair-code/source-available and says n8n is not open source because its license limits use. This is a taxonomy label, not legal advice.
Use restriction. The license and FAQ restrict commercial provision/hosting and give paid customer access and white-labeling as examples that need a separate agreement. Check the exact intended use with n8n or qualified counsel; this page does not decide whether a deployment is permitted.
Self-hosting and the free Community edition are product/deployment choices, not an OSI license classification. The edition comparison lists Community features and omissions; feature and plan boundaries can change.
Execution boundary
n8n is a visual workflow and optional AI/agent orchestration layer. Its documentation covers triggers, processing nodes and actions, plus nodes for selected CRM, form, email, social and analytics services. Connector fit depends on the node, operation, API version, credential, OAuth scope and target-service terms. These entries do not prove production suitability for every integration.
It is not a CRM, contact-consent record, suppression list, campaign system, deliverability service or marketing strategy system. Do not use it for unrestricted autonomous sending, posting, CRM changes or paid-media actions.
What an operator must own
- Hosting, patching, network exposure, identity/access controls, credentials and encryption-key custody.
- Database/volume backups and restore drills; the backup guide says a full recovery needs the relevant data, custom nodes/external storage when used, and the encryption key.
- Per-flow retry, error, retention and rollback ownership; execution visibility and retry controls do not provide an alert policy by themselves.
- Consent, suppression, deliverability, target API/OAuth scope and any model-provider terms, costs and data path.
The documented Agent Builder and self-hosted knowledge-base capabilities are Preview; self-hosted agents require the agents module and do not support queue mode yet. Sensitive tools can require approval. Treat this as a human-review control, not proof of agent safety.
Safe first test
Do not connect real CRM, email, social, analytics, advertising, webhook or production credentials. Create one harmless failed branch, inspect the local execution and retry controls, then remove the workflow, credentials, container and test data. This test can show whether a team can inspect a local draft workflow. It does not prove licensing fitness, reliability, security, connector behavior, scale or production readiness.
Decision
Use n8n only when a source-available/fair-code workflow layer fits the intended license and an operator can own its deployment and controls. Keep Activepieces CE as the OSI-style orchestrator example, subject to its named EE-path caveat. Read the full n8n license-boundary audit for sources, comparison details and exclusions.