n8n Community Edition

When you self-host n8n without purchasing a paid plan, you are running the Community Edition. It is free, source-available under the Sustainable Use License, 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. You get unlimited workflows, unlimited executions, all 400+ integrations, full webhook support, queue mode, and the complete workflow editor.

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.

The Community Edition omissions are deliberate. These features are gated behind paid plans to sustain n8n's development. Here is what each one means in practice:

• Custom Variables: Instance-wide constants you define once and reference across all workflows. Without this, each workflow must redeclare its own values or pull them from environment variables manually.
• Environments: Separate staging and production configurations from a single admin panel. Without this, environment separation requires running entirely separate n8n instances.
• External Secrets: Native integration with HashiCorp Vault, AWS Secrets Manager, or Azure Key Vault. On Community, credentials are stored in n8n's own encrypted database only.
• External Binary Storage: Route binary files (images, PDFs, attachments) to S3 or compatible object storage. On Community, binaries are stored on the local filesystem, which becomes a scaling bottleneck at high volume.
• Log Streaming: Push execution logs to Datadog, Splunk, or similar observability platforms in real time. Basic file-based logging is included, but forwarding is not.
• Multi-Main Mode: Run multiple n8n main processes simultaneously for high-availability failover. Queue mode (single main, multiple workers) is included. Active-active redundancy is Enterprise-only.
• Projects and Sharing: Workspace-level organization with fine-grained access control. On Community, only the instance owner and the workflow creator can access a given workflow.
• SSO (SAML / LDAP): Single Sign-On with enterprise identity providers. Community users must authenticate with local n8n accounts only.
• Git Version Control: Built-in Git integration for pushing workflows to a repository and switching branches. Manual JSON exports remain available as a workaround.

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.

Registration requires only a valid email address. n8n uses it to send you the license key and occasional product updates. No credit card, no phone number, no company information required.

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

New instance: The registration option is presented during the initial account creation flow. Enter your email when prompted and a license key is sent immediately.

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

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

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 a paid plan for the Projects and Sharing features. On Community, only the owner and creator have access.
• Enterprise identity and compliance. If your organization mandates SSO, LDAP, external secret management, or audit log streaming to a SIEM, the Enterprise plan addresses all of these. These are hard requirements you cannot work around.
• Environment promotion pipelines. If your team operates a formal staging-to-production workflow promotion cycle and requires Git-based version control of 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. Many teams run hundreds of workflows on Community without hitting any functional limits.

Running Community Edition in production is entirely viable. Here are the practical recommendations that matter most:

• Use PostgreSQL, not SQLite. The default SQLite backend works for testing but will corrupt or lock under concurrent writes. Switch to PostgreSQL with DB_TYPE=postgresdb before you go live. See our VPS self-hosting guide for the full Docker Compose setup.
• Set the encryption key once, back it up. N8N_ENCRYPTION_KEY encrypts all saved credentials. Generate it with openssl rand -hex 16, store it somewhere safe, and never change it. If you lose this key, all credentials become unrecoverable.
• Prune execution data. n8n stores every execution by default. On a busy instance, the database grows quickly. Set EXECUTIONS_DATA_MAX_AGE (in hours) to auto-prune old executions. 720 hours (30 days) is a reasonable default.
• Enable queue mode for heavy workloads. If you process thousands of executions daily, enable queue mode with Redis to separate the main process from worker processes. This prevents a long-running workflow from blocking the editor or webhook triggers.
• Automate backups. A daily PostgreSQL dump and n8n data volume backup is the minimum. Use cron and store backups offsite. Losing a production n8n instance with months of workflow development is painful and entirely preventable.
• Pin the Docker image version. Using n8nio/n8n:latest in production means any restart could pull a new version with breaking changes. Pin to a specific version like n8nio/n8n:1.52.0 and upgrade deliberately.