n8n Self-Hosted
Automate integrations and business processes with a customer-hosted workflow editor and runtime.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Heroku
- Hetzner
10 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Docker Compose with persistent data; database and worker topology selected for workload
Runs in
Documented customer environment
Customer-operated workflow runtime, credentials store and persistent execution data
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- DigitalOcean: Customer cloud account
- Heroku: Customer platform workspace
- Hetzner: Customer cloud account
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Heroku
- Hetzner
Servers / containers
Operated by
Your team
Customer manages servers/containers, secrets, database, backup/restore, scaling and upgrades.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
n8n deployment on AWS ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
n8n deployment on Azure ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
n8n deployment on Google Cloud Run ↗ · Source checked 2026-11-12
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
n8n self-hosted deployment on DigitalOcean ↗ · Source checked 2026-11-12
- Heroku: Customer platform workspace · Customer-operated
Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.
n8n self-hosted deployment on Heroku ↗ · Source checked 2026-11-12
- Hetzner: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
n8n self-hosted deployment on Hetzner ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Docker Compose with persistent data; database and worker topology selected for workload |
|---|---|
| Infrastructure | Servers / containers Reviewed topology runs long-lived containers and persistent workflow/credential storage. Event triggers do not make the self-hosted control/runtime stack function-based serverless. |
| Licensing model | Source Available The core is under the Sustainable Use License with use restrictions, not an OSI open-source license. Enterprise-marked code requires a separate commercial Enterprise license. A free self-hosted option does not change the core license model. |
| License | Sustainable Use License for covered code; separate commercial Enterprise license for enterprise components |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
SAML or OIDC SSO is documented for self-hosted Business and Enterprise. Instance-owner or administrator privileges are required to configure it.
Self-hosted Business and Enterprise; not the unlicensed Community edition · Source ↗ · Reviewed 2026-11-14
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The vendor documents Linux Compose installation and links n8n-hosting configurations for different architectures. Configure persistent data, database, encryption key, domain and TLS; choose the production topology rather than treating the minimal single-server recipe as HA.
Official self-hosted Compose deployment · Source ↗ · Deployment artifact ↗ (Select and pin a compatible versioned application image) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The self-hosted memory guide ties RAM usage to execution concurrency, JSON/binary payload size and workflow behavior. It does not establish one safe server minimum. Size main processes, workers/task runners, PostgreSQL, queue-mode Redis, binary storage and HA after measuring representative workflows.
Self-hosted workflow-dependent sizing; complete production footprint unresolved · Source ↗ · Production topology and dependencies ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The Sustainable Use License permits internal business or non-commercial/personal use under its conditions. Enterprise files are separately licensed, and other branches have specific restrictions. Commercial redistribution or embedded use must be checked against vendor terms; self-hosting does not grant every Enterprise feature.
Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
n8n n8n@2.48.6 was published November 19, 2026. Official 2.x images use a patched Node 26.13.0 runtime carrying a V8 process-abort fix. Maintained 1.x users should use n8n@1.123.99 or later, which moves to Node 24.22.3.
Upstream n8n 2.x release; the 1.x maintenance line has a separate fixed build · Source ↗ · Prior reviewed release context ↗ · Maintained 1.x runtime fix ↗ · Patched V8 runtime integration ↗ · Reviewed 2026-11-19
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
This entry excludes n8n Cloud. The Sustainable Use License has use restrictions and should not be described as unrestricted open-source licensing. Enterprise components require the appropriate commercial license. External integrations, AI providers and optional assistant services require separate data-flow review. n8n@2.48.6 and the maintained n8n@1.123.99 line move official images to patched Node runtimes carrying a V8 process-abort fix. The 1.x image also moves to Node 24.22.3, while 2.x pins a patched Node 26.13.0. Update the selected line and verify custom images use the fixed runtime.
Category fit
- Workflow automation
- Visual integration/workflow automation with custom code and connectors; connected systems and AI providers may receive workflow data.
- AI tools & infrastructure
- Orchestrates AI providers, agents, tools and memory as workflows. Model inference and external service dependencies are configured separately.
Compare within Workflow automation
- Activepieces Self-HostedSelf-hosted workflow automation platform with integrations, triggers, actions and worker execution.
- AWS
- Google Cloud
- Railway
- Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
- AWS
- Azure
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
- AWS
- Azure
- CortezaLow-code platform for business records, workflows and configurable CRM applications.
- Hostinger
- Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
- AWS
- Azure
- Google Cloud
- Documenso Self-HostedSelf-hosted electronic-signature and document workflow application with a Railway deployment path.
- Railway
- DocuSeal Self-HostedSelf-hosted document forms and electronic-signature workflows with API and webhook integration.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Railway
- Render
- Heroku
- Linode
- Vultr
- Hostinger
- LumaDock
Showing 8 of 25 other listings in Workflow automation. These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow automation →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Current self-hosted Docker Compose guide ↗docs.n8n.io
- Official license boundaries ↗github.com
- Workflow automation project ↗github.com
- AI workflow components and integrations ↗docs.n8n.io
- n8n self-hosted deployment on DigitalOcean ↗docs.n8n.io
- n8n self-hosted deployment on Heroku ↗docs.n8n.io
- n8n self-hosted deployment on Hetzner ↗docs.n8n.io
- n8n@2.48.6 release ↗github.com
- n8n@1.123.99 release ↗github.com
- Patched V8 runtime integration ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- n8n deployment on AWS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Project instructions deploy n8n and PostgreSQL on customer-operated EKS. Review persistence, ingress and production scaling requirements.
- n8n deployment on Azure ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
Project instructions deploy n8n with PostgreSQL on Azure Kubernetes Service in the customer subscription.
- n8n deployment on Google Cloud Run ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project documents Cloud Run deployment. Its easy mode is not the production configuration; follow the durable-mode guidance for production and review execution and persistence constraints.
- n8n self-hosted deployment on DigitalOcean ↗ · DigitalOcean
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
- n8n self-hosted deployment on Heroku ↗ · Heroku
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
- n8n self-hosted deployment on Hetzner ↗ · Hetzner
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The project provides a provider-specific application deployment guide, including customer project/server creation, persistent application data and n8n configuration. DigitalOcean and Hetzner use customer-operated servers; Heroku uses a customer app and PostgreSQL service on platform-managed infrastructure. This is separate from n8n Cloud.
- n8n deployment on AWS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked