Self-hosted n8n features that change how teams operate it, most of them restricted to paid plans. n8n is source-available under the Sustainable Use License, not OSI open source.
Keeping n8n credentials in HashiCorp Vault, AWS, Azure, GCP, Infisical or 1Password instead of the n8n database, what the Enterprise plan requirement means, and the credential-field-only limit.
Running separate development, staging and production n8n instances backed by Git branches, who can push and pull, and the Business plan requirement.
Sending n8n audit, workflow and AI node events to syslog, a webhook or Sentry on the Enterprise plan so security teams can monitor credential changes and executions.
Installing verified and unverified community nodes from npm on self-hosted n8n, reviewing them before use, and keeping them working in queue mode and across upgrades.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.