What does n8n cost to self-host once licenses and staff are counted?
The n8n cost of ownership starts with the license choice. The Community edition is free to self-host under the Sustainable Use License for your own internal business purposes. Features such as SSO and LDAP, environments with Git, and log streaming are included only in the Business and Enterprise plans, and multi-main high availability is restricted to Enterprise self-hosted deployments. Your first decision is therefore whether any of those features are required on day one or can wait until the workflows prove their value. On n8n's pricing page, the Business plan is listed at 667 euros per month billed annually and is currently self-hosted only, while Enterprise is quoted on request. Confirm current figures with n8n before you budget, because list prices change.
Licensing is only one line in the total. Plan for the hosting compute for the main instance, and for workers and webhook processors if you run queue mode. Add PostgreSQL, which holds workflow and execution data, and Redis where queue mode uses it as the broker. Backups of the database and encryption key, monitoring and alerting, log retention, and TLS certificate management all recur every month. Some of these costs are one-time, such as the initial build, credential migration and first workflow rebuilds. Others recur, including patching, upgrades, storage growth from execution history and the on-call time needed when a webhook fails at night. Ask for each of these as a separate line item so you can see what changes when volume grows.
Staff time is usually the largest and least visible cost. An internal platform or automation team must learn the deployment model, configure queue mode correctly, handle the shared encryption key that every worker needs, and keep up with releases that ship often. Teams usually scope this in-house when they already run PostgreSQL, Redis and container platforms and have someone who owns them. They often bring in a partner for the first build, the security configuration and the handover, then keep a smaller internal rota for routine work. Either way, estimate hours per month for upgrades, incident response and workflow changes, and compare that with the cost of a fixed-scope implementation and an optional support retainer.
Check the license scope before you assume the cheapest path is compliant. The Sustainable Use License does not cover files with .ee in their name or directory, which need a valid n8n Enterprise License. Distribution is allowed only free of charge for non-commercial purposes, so embedding n8n in a product you sell is outside the Community terms. Whether an outside firm operating the instance for you counts as internal use is a question for your legal team and for n8n, so confirm it in writing before the deployment starts. Also confirm whether your Enterprise terms or Business terms match the features your design depends on.
When you request a quote, ask for the scope in writing: the number of instances and workers, the database and Redis sizing assumptions, the backup and restore test, the monitoring stack, the features that need Business or Enterprise, and what is excluded, such as licenses, cloud accounts and ongoing support. A useful comparison sets the one-time implementation cost against a recurring monthly estimate for hosting, licensing and internal time. That view shows whether a Community deployment with a small internal team is sound, or whether the features your teams need make a paid edition the cheaper option.
What a n8n cost of ownership review includes
A cost of ownership review turns n8n edition choice into a written record your leadership, finance and security teams can check. Each deliverable below answers one question, and together they show what self-hosting costs over time and which features need a license.
License position per use case
Each planned use of n8n is compared against the Sustainable Use License, which permits use for your own internal business purposes and non-commercial or personal use. Internal automation, customer-facing products built on n8n, and distribution to third parties are treated separately, because the terms differ for each. The output states the position for every use case and flags the ones your counsel should review before go-live.
Edition recommendation tied to features
The recommendation names the features your team needs, such as SAML single sign-on, environments with Git, log streaming and multi-main high availability, and maps each one to the edition that includes it. Community, Business and Enterprise are compared against that feature list, not against general marketing claims. Confirm current plan contents on the pricing page on the day you sign, since editions change.
Infrastructure model
The infrastructure model sets out the compute, PostgreSQL, Redis and storage needed for each environment, including whether queue mode and separate webhook processors are required. It states which parts run in your cloud account, data center or air-gapped network and which, if any, depend on external services. Each component is listed with its owner, so the running cost has a clear basis.
Recurring cost list
The recurring cost list separates one-time work from costs that continue every month or year, such as hosting, database backups, monitoring, license fees for Business or Enterprise, upgrade effort and staff time. Each line names who pays for it, whether that is your organization, a vendor or a partner, and what drives it up or down. Ask for the list to show the assumptions behind each line rather than a single total.
Assumptions register
The assumptions register records every input that shapes the figures, including expected execution volume, number of editors, number of environments, retention periods and the plan vendor pricing is based on. Each assumption has an owner and a date, so a change in workflow volume or team size can be traced to a specific line. This register is the part of the review that most often changes after go-live.
Exclusions and limits of the review
The review is not an audit, a legal opinion on license terms or a certification, and it does not replace advice from your counsel on how n8n may be used in your products. It also does not issue a quote for vendor licenses or predict future n8n pricing. Ask for these exclusions to be written into the scope, and ask who will handle any license question the review raises.
What the Sustainable Use License allows inside a company
The Sustainable Use License that covers n8n permits you to use or modify the software for your own internal business purposes, or for non-commercial or personal use. Distribution is allowed only free of charge and only for non-commercial purposes. For most organizations evaluating self-hosting, the practical starting point is simple: running n8n on your own servers to automate your internal processes is within the scope of internal business use. That covers the Community edition running your finance, HR, IT and operations automations, and it is the reason a company can start with a free install before deciding whether a paid edition is needed for features such as SSO or Git environments.
Several questions fall outside that simple case and should be settled before rollout. The first is whether you intend to offer n8n itself to customers, for example by running separate instances for each client or by letting external users build workflows in your environment. Hosting n8n as a service for others is a different question from using it internally, and the license treatment of that model should be reviewed rather than assumed. The second is whether internal automations will ever be shipped to customers as part of a product. Embedding n8n, or distributing a modified copy of it, moves the work out of the internal-use category. Write down the intended use cases, including any partner or customer access, and have them reviewed against the license text.
Some files in the repository carry .ee in their file name or directory path. The license states that these files are not covered by the Sustainable Use License and require a valid n8n Enterprise License. Your team should know this before it modifies source code, copies directories into a fork, or builds a custom image. Check which features your deployment touches, because enabling or building on enterprise functionality without the right license creates a compliance gap even when the rest of the install is licensed correctly. Ask the vendor which components sit under the enterprise terms and keep a record of the license decision for each environment, including staging and disaster recovery copies.
Confirm your interpretation with your legal team before committing budget or architecture. The questions to put to them are specific: Is our intended use internal business use? Will any customer, partner or contractor access n8n in a way that changes the analysis? Do we plan to modify or redistribute the code? Do we need an Enterprise License for any of the components we will run? DeployOpen does not give legal advice on license terms. We can document how your environment is built and which components it uses, so your counsel has accurate facts to review, but the interpretation of the license belongs with your lawyers and, where relevant, with n8n directly.
Which n8n edition covers which feature set
This table compares the three self-hosted n8n editions on the features that usually drive the purchase decision: identity, environments, log streaming, high availability and support. Read each row as a question to answer for your own environment, then confirm current terms on n8n's pricing page before you commit, because plan contents and prices can change.
| Feature or term | Community (self-hosted) | Business (self-hosted) | Enterprise (self-hosted) |
|---|---|---|---|
| Users, workflows and integrations | Unlimited users, workflows and integrations | Unlimited users, workflows and integrations | Unlimited users, workflows and integrations |
| Execution counting | One execution is one run of a whole workflow, regardless of step count | One execution is one run of a whole workflow, regardless of step count | One execution is one run of a whole workflow, regardless of step count |
| SSO (SAML) and LDAP | No | Yes | Yes |
| Git-based environments | No | Yes | Yes |
| Log streaming | No | Yes | Yes |
| Multi-main high availability | No | No | Yes |
| Dedicated support with an SLA | No | No | Yes |
| Published price (per n8n pricing page) | Free to self-host | 667 euros per month billed annually, currently self-hosted only | Custom pricing, requested through n8n |
Which costs recur after go-live and who pays them
Once a self-hosted n8n instance is live, most of the bill keeps arriving every month or every year, and it lands with different owners. Some lines go to your cloud provider, some to n8n as a licensor, and some to your own staff or a partner retainer. Read each category below against your own hosting model and ask for the recurring items to be named separately in any quote.
n8n license or subscription
The Community edition carries no license fee, but SSO and LDAP, Git environments and log streaming are included only on the Business and Enterprise plans, and multi-main high availability is restricted to Enterprise self-hosted deployments. Under the Sustainable Use License, the terms also limit use to internal business or non-commercial purposes, and any .ee files need a valid Enterprise License. Ask whether the license is annual, which edition covers each feature you need, and what renewal terms apply.
Compute and storage for main and workers
Your cloud provider bills for the main instance, any worker or webhook processor nodes, and the disk they use. In queue mode, workers scale with execution volume, so this line moves with workflow load rather than user count. Ask the partner to show how many nodes the quote assumes, how scaling is triggered, and whether the estimate covers reserved or on-demand capacity.
PostgreSQL and Redis hosting
PostgreSQL stores workflow definitions, credentials and execution data, and Redis brokers executions in queue mode. Whether you run these as managed services or self-managed VMs changes who handles patching, failover and storage growth. Ask who pays for each managed service, what storage and backup tiers are included, and whether the quote covers replicas if you need redundancy.
Backups and execution data retention
Backup storage and retention periods are recurring costs that grow with execution history. Pruning execution data reduces database size but also reduces the audit trail available to your team. Decide how long execution data and encrypted credential backups must be kept, where they are stored, and who restores them. Ask the partner to state the retention policy and the restore test cadence in writing.
Monitoring and log tooling
Metrics, alerting and log storage are often billed by a separate observability vendor or by your cloud provider, and they recur with data volume. Log streaming to an external destination is a Business and Enterprise feature, so the choice of plan can shape this line. Ask which tools are included in the quote, who receives alerts out of hours, and how much log retention is assumed.
Patching and upgrade testing
n8n ships minor releases roughly weekly under semantic versioning, and breaking changes arrive in major releases. Each upgrade needs a staging run of critical workflows, a database backup and a rollback plan. Whether this work is done in-house or under a partner retainer determines who carries the cost of each cycle. Ask what is covered per release, how many upgrades per year are included, and who tests credential-dependent workflows.
Internal staff time
Your own engineers and workflow owners spend time on access reviews, incident response, reviewing new community nodes, and answering requests from business teams. This cost is rarely shown on an invoice but often exceeds the infrastructure bill. Estimate the hours per month for each role and agree with the partner which of these tasks sit in a retainer and which stay with your team.
What drives n8n cost of ownership up or down
This table lists the main factors that change what self-hosting n8n costs and how much effort it takes, with how each one pushes cost up and how to keep it down. Read it before asking for a quote, since most drivers are set by your own choices about edition, environments and skills. The main takeaway is that the edition and the number of environments are the two decisions that most often change the license line, while queue mode and compliance evidence mostly change effort.
| Driver | How it raises cost or effort | How to keep it down |
|---|---|---|
| Edition choice driven by named features | SSO and LDAP, environments with Git, log streaming and multi-main setup are included only in the Business and Enterprise plans on the pricing page. Needing any of them moves you off the free Community edition. | List the features you truly need before choosing. If you only need Community features, stay on Community and confirm the license terms against your use case. |
| Number of environments (development, staging, production) | Each environment adds a server, a database, credentials to configure and a workflow promotion path. Environments with Git are a paid feature, so promoting workflows across them can require a Business or Enterprise license. | Limit environments to what your release process needs. Confirm with n8n whether your planned environments need licensed features before you commit to a design. |
| Expected execution volume | Higher volume increases compute, database growth and the need for a larger PostgreSQL instance. Because n8n counts one execution per whole workflow run, a workflow with many steps does not multiply the count, but heavy runs still consume resources. | Batch small triggers where it is safe, schedule heavy jobs off-peak, and prune execution data on a set schedule. Ask the implementer to size from measured run volume, not estimates. |
| Number of workflows and credentials to protect | More workflows raise testing, documentation and upgrade regression effort. More credentials raise secret management, rotation and access-review work, and each credential is a potential exposure. | Retire unused workflows, group related ones into sub-workflows, and keep a credential inventory with owners. Restrict who can view shared credentials. |
| Need for queue mode or multi-main | Queue mode adds a Redis broker, worker instances and a shared encryption key across processes, which adds infrastructure and operations work. Multi-main requires an Enterprise self-hosted license, so high availability has a direct license cost. | Start with a single main instance if throughput allows, and add queue mode only when measured load requires it. Decide on multi-main only if your uptime requirement justifies the Enterprise license. |
| Compliance evidence requirements | Assessors often ask for access reviews, change records, encryption key handling, backup restore tests and audit logs. Producing this evidence is ongoing work, and the license tier may determine which logging and access features exist. | Agree the evidence list before build, use the features your edition provides, and automate exports where possible. DeployOpen prepares controls and evidence, but independent auditors issue any assessment result. |
| Internal skills available | Teams without Node.js, PostgreSQL, Redis or container operations experience need more outside help for setup, troubleshooting and upgrades. Each skill gap usually shifts cost from internal time to external services. | Map existing skills against the stack before scoping. Plan a handover with runbooks, and ask any partner to quote training and support after go-live as separate line items. |
| Enterprise support and SLA | Dedicated support with an SLA is part of the Enterprise plan on the pricing page. Choosing it adds a recurring license cost, while relying on community channels shifts response risk to your team. | Decide support needs by system criticality. Compare the Enterprise support terms with a retainer for implementation support, and confirm exactly what each covers in writing. |
How a cost of ownership assessment runs step by step
The sequence turns a loose question about n8n into a written assessment that names the edition, the deployment shape, the recurring costs and the assumptions behind each number. Each step produces an artifact that the next step depends on, so the final document can be checked and challenged by the people who own the budget.
Inventory intended use and internal status
Start by listing what n8n will do, which teams will build and run workflows, and whether every use is for your own internal business purposes. The Sustainable Use License permits internal business use and non-commercial or personal use, so anything that serves external customers, resells the product or embeds it in a distributed product needs a legal review before the edition decision is made. The output is a use register with one line per use case, an internal or external flag, and a named owner who confirms the reading with counsel. The step is done when legal has signed off on each external-facing item or those items are removed from scope.
List the features the business requires
Turn the requirements into a short feature list and mark which items are included in the Community edition and which depend on a paid plan. Typical items that need checking are SSO and LDAP, Git-based environments, log streaming, multi-main high availability and any Enterprise-only support terms. Confirm each item against the current pricing page and the vendor documentation, since plan contents change. The output is a feature matrix with a column for the plan that includes each feature and a column for the requirement's owner. The step is done when every requirement is either covered by a named plan or accepted as a gap with a stated workaround.
Choose the edition and deployment shape
Using the feature matrix, select the edition, then decide the topology: a single instance, a main instance with separate workers in queue mode, or several main instances for high availability. Queue mode requires shared Redis and PostgreSQL and a shared encryption key across processes, so the shape determines how many services your team operates. The output is a one-page architecture note naming the edition, the process layout and the data stores. Ask the vendor or a partner to confirm that the chosen shape is supported on the chosen edition before the note is accepted.
Model recurring infrastructure costs
List each component of the chosen shape and identify who pays for it: your cloud account or data center, a managed database provider, or the vendor's license fee. Separate one-time costs such as initial setup and migration from recurring costs such as compute, storage, backups, Redis, PostgreSQL, monitoring and network egress. For each recurring line, record the driver that moves it, such as execution volume, workflow data retention or number of workers. The output is a cost model with a unit basis for each line and a statement of the prices used with their source and date. Mark any figure you could not obtain as an open item rather than estimating it.
Model people roles and time
Name the roles that will own the platform, including the administrator who runs upgrades, the person who maintains credentials and encryption keys, workflow builders in each business unit and the on-call contact for failed executions. For each role, record the share of time you expect it to need and whether that time is provided internally, by a partner under a retainer or by a fixed-scope engagement. The output is a responsibility table that maps each recurring task to a role and a delivery route. The step is done when every recurring task in the cost model has a named owner.
Set the upgrade and support cadence
n8n uses semantic versioning and ships minor releases roughly weekly, so a patch-and-minor schedule cannot be left to chance. Decide how many hours per month are budgeted for reviewing release notes, applying minor releases to a staging copy, running regression checks on critical workflows and rolling production forward. Set a separate budget for occasional major releases, which may carry breaking changes. Also decide what support is needed after go-live and whether it comes from internal staff, a retainer or the vendor's enterprise support terms. The output is an upgrade and support calendar with a stated budget for each release class, and the step is done when the owner of the budget signs off on the figure.
Write the assessment with assumptions
Assemble the outputs from the previous steps into one written document: the use register, feature matrix, architecture note, cost model, responsibility table and upgrade calendar. Each number must link to an assumption, and each assumption must name its source or the person who confirmed it. Include a sensitivity section that shows which assumptions change the total most, such as execution volume or upgrade effort. Ask for a written quote against the same architecture note before comparing options. The assessment is complete when a reviewer who did not write it can trace every line to its source.
Where n8n cost estimates usually go wrong
The most common error is treating the free Community edition as zero cost. The software may be free to download, but someone still installs it, configures PostgreSQL, applies upgrades, takes and tests backups, and watches execution failures. Check this by listing every recurring task by role (platform engineer, security reviewer, workflow owner) and estimating the hours each month. Ask your partner or internal team to show those hours in the figure. A quote that lists only infrastructure and license lines has left out the largest recurring cost.
Second, do not assume that single sign-on, environments with Git, or log streaming are available on the Community edition. According to n8n's pricing page, SSO and LDAP, Git environments, and log streaming are included only in the Business and Enterprise plans. Multi-main setup, which runs several main instances for high availability, is restricted to Enterprise self-hosted deployments. Confirm each feature you plan to use against the current pricing page and the license terms before the design relies on it. If a feature requires a paid plan, add that cost to the estimate, and record which plan the figure assumes.
Third, queue mode multiplies the infrastructure line. The main instance hands executions through Redis to a pool of workers that read and write PostgreSQL, and the encryption key must be shared with every worker and webhook processor. Estimates often count one server and forget the extra worker hosts, the Redis service, its monitoring, and the storage that grows with execution history. Ask for a process count, a concurrency setting for each worker, a Redis sizing and failover approach, and an execution data retention period. Each of these changes the monthly cost.
Fourth, upgrade and testing effort is usually underestimated. n8n ships minor releases roughly weekly and occasionally publishes breaking major versions, so testing is a recurring activity, not a one-off project. Estimates that assume a single upgrade a year leave out regression testing of critical workflows, credential checks, and rollback rehearsals. Ask for the number of upgrade cycles per year in the scope, who signs off each one, and whether post-go-live support includes upgrades or only incident response.
Finally, the license question is easy to skip when workflows serve people outside your organization. The Sustainable Use License permits use for your own internal business purposes or for non-commercial or personal use, and it does not cover files with .ee in their name or directory, which need a valid n8n Enterprise License. If a workflow sends data to customers, runs a customer-facing product, or is resold as a service, the standard license may not fit. Inventory how each workflow is used, check whether any .ee features are enabled, and obtain a written license review from your legal or compliance team before the figure is signed off.
Questions buyers ask about n8n editions and running costs
Is the n8n Community edition free to self-host for internal use?
Yes, for internal business use, the Community edition is free to self-host. n8n is licensed under the Sustainable Use License, which allows use or modification only for your own internal business purposes or for non-commercial or personal use. The n8n pricing page lists a free self-hosted Community edition. The license does not allow distribution for commercial purposes, so offering n8n as a hosted service to outside parties is a different question. Files with .ee in their name or directory are not covered by the Sustainable Use License and need a valid n8n Enterprise License, so confirm that your deployment does not depend on them. Ask your legal counsel to confirm how the license applies to your affiliates, contractors and customers.
Which n8n features force a paid edition?
SSO and LDAP, Git-based environments and log streaming are listed as included only in the Business and Enterprise plans. According to the n8n pricing page, the Business plan is priced at 667 euros per month billed annually and is currently self-hosted only. Enterprise uses custom pricing for self-hosted or cloud. Multi-main setup, which runs several main instances for high availability, is restricted to Enterprise self-hosted deployments. Enterprise also adds dedicated support with an SLA. Queue mode itself is a scaling design, so check the current pricing page and license terms for the exact feature split before you commit, because plan contents can change.
Do we need a partner to choose an n8n edition?
No, your own team can choose an edition, but the decision depends on mapping requirements to plan features. Start with the list of features you must have, such as SSO through SAML, Git-based promotion between environments, log streaming or high availability, and compare that list against the current pricing page and license terms. A partner adds value when the mapping needs to be documented for an audit or procurement file, or when the answer depends on architecture choices such as queue mode and multi-main. Ask any partner to show the written license position, the feature list they relied on and the date they checked it, so the decision stays traceable.
How long does an n8n edition and deployment assessment take?
The duration depends on the scope, and no fixed figure applies to every organization. The main drivers are the number of workflows and credentials to review, the number of integrations in use, whether you need queue mode, multi-main, SSO or Git environments, and how many environments and approval stages exist. Regulatory review, identity provider access and the speed of decisions from your security and compliance teams also affect the timeline. Ask for a written, fixed-scope plan that lists the assessment steps, the client inputs each step needs and the points where your sign-off is required, rather than relying on a general estimate.
What does the client need to provide for an n8n assessment?
The client provides access, information and decisions. Expect to supply an inventory of existing workflows with their owners, triggers and target systems, and a list of the integrations and credentials they depend on. You will need a named technical contact for the hosting environment, access to the cloud account, data center or network where n8n will run, and details of your identity provider if SSO is in scope. Decision makers must agree on the edition, hosting model, backup approach and who owns encryption keys. Test data and a test window for side-effect checks also help. Confirm these inputs in writing before the work starts.
Can our own team deploy and run n8n without outside help?
Yes, a team with container, database and identity skills can deploy and run n8n without a partner. n8n publishes documentation for self-hosting, queue mode and SAML, and the Community edition has no license fee. The harder parts are design decisions that persist: where the encryption key is stored and how it is shared with worker and webhook processors, how PostgreSQL and Redis are backed up and sized, how upgrades are tested against live workflows, and how monitoring and alerts are set up. Assess whether your team has time and experience for these tasks, and whether anyone will own them after go-live. A partner can take on the build or run it as a retainer.
How do n8n running costs change after go-live?
Recurring costs continue after go-live, and the largest ones are often not the license. On the Business or Enterprise plans, the license is a recurring subscription, and the Business price on the n8n pricing page is 667 euros per month billed annually. Community has no license fee, but infrastructure still recurs for compute, PostgreSQL, Redis, worker capacity, storage, backups and monitoring. Staff time for upgrades, testing, credential rotation and incident response also recurs. If you compare with n8n Cloud, note that the pricing page counts an execution as one run of a whole workflow regardless of steps. Ask any quote to separate one-time build costs from each recurring line item.
How DeployOpen works on this
DeployOpen plans and implements self-hosted open-source platforms inside your own cloud accounts, data centers or air-gapped networks. For n8n, we start by mapping which features your workflows need against the Community, Business and Enterprise editions, then document the resulting license and running costs before any build begins.
How we scope
- Inventory the features you need, such as SSO, Git environments, multi-main or log streaming, and map each to the edition that includes it
- Review the Sustainable Use License against how your organization will use n8n, and flag questions for legal counsel to confirm
- Estimate hosting, PostgreSQL, Redis and staffing components in a written scope, with each cost line tied to a named assumption
How we build
- Size the hosting footprint for the main instance, workers and any webhook processors based on your workflow volume and execution profile
- Configure PostgreSQL and, where queue mode is chosen, Redis, with the encryption key handling documented for every node that reads credentials
- Test license-gated features in a non-production environment before enabling them, and record which edition each environment runs
How we hand over
- Deliver a cost model listing one-time setup items separately from recurring infrastructure, license and staffing costs
- Document the edition decision, the license terms that apply, and the feature dependencies that would change if the edition changed
- Walk your team through the runbook so the owners of hosting, credentials and licensing know what to review each quarter
How we support
- Offer ongoing support and upgrade planning as a retainer, covering weekly minor releases and the review of any breaking major versions
- Re-check the cost model when your plan changes, for example when you add users, move to multi-main or add a worker pool
- Confirm with your procurement team and with n8n which current pricing and license terms apply at the time of your quote
