Setup Strategy

n8n Community Edition: Features, Limits, and Free Unlocks

Published on Mar 25, 2026 · By Anshul Namdev

What Is the Community Edition?

When you self-host n8n without purchasing a paid plan, you are running the Community Edition. It is free, open-weight, and includes the vast majority of n8n's feature set. For most individual developers, freelancers, and small teams building internal automations, the Community Edition is everything you need.

Understanding exactly where the Community Edition ends and the paid plans begin is critical before you architect a production system. Discovering a necessary feature is locked after you have built can force a disruptive and expensive migration.

Edition Feature Comparison

Feature Community Registered Enterprise
Core workflow execution Yes Yes Yes
Queue mode Yes Yes Yes
Logging Yes Yes Yes
Workflow folders No Yes Yes
Debug in editor No Yes Yes
Custom execution data No Yes Yes
Custom Variables No No Yes
Environments No No Yes
External secrets No No Yes
Git version control No No Yes
SSO (SAML / LDAP) No No Yes
Projects No No Yes
Log streaming No No Yes

What the Community Edition Does Not Include

The community edition has a very specific set of omissions. These are not missing due to instability or incompleteness — they are deliberately gated behind paid plans to sustain n8n's development. Knowing them upfront is essential before committing to a self-hosted deployment.

  • Custom Variables: Instance-wide variables you can define once and reference across all workflows. Without this, each workflow must redeclare its own constants or pull them from environment variables manually.
  • Environments: The ability to maintain separate staging and production configurations from a single n8n admin panel. Without this, environment separation requires running entirely separate n8n instances.
  • External Secrets: Native integration with secret managers like HashiCorp Vault or AWS Secrets Manager. On the community edition, credentials are stored directly in n8n's own encrypted database.
  • External Storage for Binary Data: By default, binary files (images, PDFs, attachments) are stored in the local filesystem. Enterprise plans support routing binary data to S3 or similar object storage, which is critical for high-volume workflows.
  • Log Streaming: Pushing execution logs to external observability platforms (Datadog, Splunk, etc.) in real time. Basic logging to local files is included in the community edition, but forwarding is not.
  • Multi-Main Mode: Running multiple n8n main process instances simultaneously for high-availability failover. Queue mode (a single worker pool) is included, but true active-active redundancy is Enterprise-only.
  • Projects: A workspace-level organization layer above individual workflows, allowing teams to partition access by project scope. Missing on Community; only the instance owner and the workflow creator can access workflows.
  • SSO (SAML / LDAP): Single Sign-On integration with enterprise identity providers. Users on Community must authenticate with local n8n accounts only.
  • Workflow and Credential Sharing: On Community, only the instance owner and the user who created a workflow or credential set can access it. There is no fine-grained permission system between team members.
  • Version Control Using Git: The built-in Git integration for pushing workflow exports to a repository and switching between branches is Enterprise-only. Manual JSON exports remain available on Community as a workaround.

The Registered Community Edition

n8n offers a genuinely compelling middle ground: by registering your self-hosted instance with your email address, you unlock three additional features completely free of charge. The license does not expire once activated.

The three features unlocked by registration are:

  • Folders: Organize all your workflows into a hierarchical folder structure directly inside the n8n editor. This feature alone becomes essential once an instance grows beyond 20 to 30 workflows.
  • Debug in Editor: Copy and pin execution data from a previous run into an active workflow session. This allows you to replay a specific problematic execution payload directly in the editor without needing to manually trigger the workflow again.
  • Custom Execution Data: Attach, search, and annotate custom metadata to any workflow execution. This is particularly powerful for building audit trails, tagging executions with customer IDs, or flagging specific runs for review.

How to Register a New Instance

If you are setting up n8n for the first time, the registration option is presented during the initial account creation flow. Simply enter your email address when prompted and a license key will be sent immediately.

How to Register an Existing Instance

If your instance is already running without registration, activating the free features takes under two minutes:

  1. Select the three-dot icon in the lower-left corner of the n8n editor.
  2. Select Settings, then navigate to Usage and plan.
  3. Select Unlock, enter your email address, and select Send me a free license key.
  4. Check your inbox for the license email.
  5. Activate by clicking the button in the email, or by returning to Settings > Usage and plan and selecting Enter activation key.

Once activated, the license is permanent. n8n may adjust the set of features included in the registered unlock tier in the future, but previously unlocked features will not be revoked from existing activations.

When You Need to Upgrade Beyond Community

The community edition handles the overwhelming majority of real-world automation use cases. The decision to upgrade typically comes down to one of three specific requirements:

  • Multi-user team access with permissions: If more than one person needs to own, edit, or share specific workflows independently, you need at least the Starter Cloud plan or Business self-hosted plan for the Sharing feature.
  • Enterprise Identity and Compliance: If your organization mandates SSO, LDAP integration, external secret management, or audit log streaming to a SIEM, the Enterprise plan addresses all of these together.
  • Environment promotion pipelines: If your team operates a formal staging-to-production workflow promotion cycle and requires Git-based version control of n8n workflow definitions, the Enterprise Git integration is the only native solution.

For everything else, a registered Community Edition instance is a fully capable foundation for serious production automation infrastructure.


Feature availability may change across n8n releases. Always verify against the Usage and plan panel in your running instance and the official n8n pricing page for the most current plan breakdown.