Where self-hosted n8n costs less than Workato, and where it costs more
Self-hosted n8n removes the Workato subscription and usage line, but it replaces them with a one-time rebuild of your recipes and recurring costs for hosting, upgrades and on-call operations. For an integration team facing a renewal, a usage bill or a network the Workato cloud cannot reach, the saving depends on how many recipes must be rebuilt, how much of the runtime you already operate, and whether you need a paid n8n license. Workato prices are not published on this page, so the Workato side of the comparison must come from a written quote that lists edition, connector tier, task or usage metering and any on-prem agent fees.
On the n8n side, the Community edition is free to self-host, so the license line is zero only if your use fits its terms and you do not need the Business or Enterprise features. n8n's pricing page lists the Business plan at 667 euros per month billed annually and notes that it is currently self-hosted only, and it lists Enterprise at custom pricing for self-hosted or cloud. SSO and LDAP, environments with Git and log streaming sit in Business and above, so teams that need SAML single sign-on or Git-based environments should price those tiers. Because n8n counts an execution as one run of a whole workflow regardless of the number of steps, and all plans include unlimited users, workflows and integrations, the cost driver shifts from per-step or per-task metering to compute and staff time. Confirm the source-available Sustainable Use License terms with your legal team before you deploy in a commercial setting.
The costs that rise with self-hosting are easy to underestimate. Budget for the recipe rebuild, the servers or Kubernetes capacity, PostgreSQL and Redis if you run queue mode, the on-call rota for upgrades and incidents, and the support contract you need. In queue mode, the encryption key must be shared with every worker and webhook processor, so key handling becomes a recurring control to run. Ask any implementation partner for a fixed-scope estimate that separates one-time migration from recurring operations, and compare it with the Workato quote line by line.
Cost components on each side and what recurs
This table splits the total cost of running Workato against running self-hosted n8n into components, showing who is paid for each and whether it is one-time or recurring. Read it as a checklist for building your own comparison, since Workato pricing comes from a quote and n8n Business and Enterprise pricing is either published or custom. The main takeaway is that the largest self-hosted costs are usually people and connectivity work, not the license.
| Cost component | Commercial side (Workato) | Self-hosted side (n8n) | One-time or recurring |
|---|---|---|---|
| Subscription or edition and usage fees | Workato subscription and usage terms set by quote; confirm which metrics are billed and how overage works | n8n license is free for Community; Business is published as self-hosted only and Enterprise is custom, per n8n's pricing page | Recurring |
| n8n license (Community, Business or Enterprise) | Not applicable | Community needs no key. Business or Enterprise unlock SSO, Git environments and log streaming. Confirm terms under the Sustainable Use License for your use case | Recurring |
| Hosting and database | Included in the cloud service; on-prem agent runs on infrastructure you already provide | Compute, storage and a PostgreSQL database in your cloud or data center, sized for main, worker and webhook nodes | Recurring |
| Recipe rebuild and testing | Migration work only if you move off recipes; exported packages reduce discovery effort | Rebuilding each recipe as an n8n workflow, plus test data, credential re-entry and cutover checks | One-time |
| On-prem connectivity and worker capacity | Agent makes only outbound TLS WebSocket connections, so no inbound firewall rules are needed | Your network team must provision connectivity to internal systems, and worker capacity must scale with execution volume | Recurring, with one-time setup |
| Platform operations, upgrades and backups | Handled by Workato as the cloud provider; you manage the agent | Patching, n8n version upgrades, encryption key handling, backups and monitoring of main and worker nodes | Recurring |
| Vendor support | Included in the subscription tier you buy; confirm response terms in writing | Community has no vendor support; Enterprise includes dedicated support with an SLA, or use a retained partner | Recurring |
| Internal skills and implementation partner | Recipe builders and admins, with Workato's documentation as reference | Engineers who know Node.js, Docker or Kubernetes and PostgreSQL, or a fixed-scope implementation partner for the initial build | One-time build, recurring operations |
What moves the total cost of each option
Each option's total cost rises or falls with a small set of drivers: how many runs you execute, how many workers you need, which edition unlocks your identity and governance requirements, how much availability you need, and who operates the platform. Check each driver against your own workload before comparing the subscription lines of the two quotes.
Workflow count and execution volume
n8n counts one execution as one run of a whole workflow, regardless of how many steps it contains, and every plan includes unlimited workflows. That means a workflow with twenty steps costs the same run count as one with two, so long multi-step recipes are cheaper per run on n8n than a per-step meter would suggest. Workato's price is set by its own edition and usage terms, so ask Workato to show how it counts a recipe run and a recipe step in your quote. Multiply your monthly run count by the cost of the n8n plan you need to see where the curve bends.
Data volume and worker count
Self-hosted cost grows with the compute that runs your jobs. For comparison, Windmill's README gives a rule of thumb of one worker per vCPU with 1 to 2 GB of RAM, which helps size a Windmill pool but not n8n, so estimate n8n worker needs with your own load tests. Large payloads, long-running steps and high concurrency raise cloud compute and database storage costs, and those costs are yours to pay under either a self-hosted model or a managed Workato bill. Ask your platform team to measure peak concurrency before you commit to a size.
Editions for SSO, Git and log streaming
Several controls that enterprise teams treat as baseline sit in paid tiers. On n8n, SAML single sign-on, environments with Git and log streaming are included in the Business and Enterprise plans, not in Community. Windmill places SAML, SCIM, audit logs and full Git sync in its Enterprise Edition. Map each control your security team requires to an edition on both sides, because a Community or lower tier can change the total more than any usage line.
High availability and multi-main setup
Running n8n with several main instances for high availability is restricted to Enterprise self-hosted deployments. Queue mode also requires a shared encryption key across main and worker processes, Redis and PostgreSQL, each of which needs its own backup and upgrade plan. If your integrations must survive a node failure, price the Enterprise license, the extra infrastructure and the testing effort together. Workato's cloud availability terms are in its own contract, so compare the availability you are paying for, not the list prices.
Availability and on-call coverage
A self-hosted platform needs someone to answer when a queue backs up at 2 a.m. Under n8n Enterprise, dedicated support with an SLA is included, while Community users rely on community channels and their own staff. Under a managed Workato subscription, the vendor operates the cloud service but your team still owns recipes and connections. Ask each vendor for response times in writing and count the on-call hours your team must cover on top of the platform fees.
In-house integration and platform skills
The largest cost of a self-hosted option is often the people who build, test, upgrade and back up the platform. Teams that already write JavaScript, Python or TypeScript can rebuild recipes faster, while teams that depend on low-code builders may need training or outside help for the rebuild. Estimate the hours for rebuilding each recipe, for testing connectors against your systems and for upgrades, then ask a partner for a fixed-scope quote that names those deliverables.
How to build the comparison with your own numbers
This sequence turns a vague sense that Workato is expensive into a three-year comparison built from your own recipe inventory, written quotes and hosting estimates. Each step produces a figure you can defend in a budget review.
Export the recipe inventory with lifecycle management
An integration lead with a Workato account that has the privilege to run recipe lifecycle management exports creates a manifest and downloads the zip of recipe and dependency JSON files. Count the recipes, the distinct connectors they use, the on-prem connections, the lookup tables and the recipes that run on a schedule versus those triggered by events or API calls. Group them by business domain, such as finance, HR, or security operations, because each group will be costed separately later. The step is complete when you have a spreadsheet with one row per recipe and a count of connectors per group that a second person has checked against the Workato console.
Request a written Workato quote
Ask your Workato account team for a written quote that states the edition, the usage metric and the included volume, and the cost of the on-prem agent and any additional environments. Ask how usage is counted for your recipe mix, since the answer determines whether your forecast tracks real consumption. Request the quote to cover the term you plan to model, and ask which items are renewable at a fixed rate and which can change at renewal. The step is complete when the quote is on file with line items you can map to the three-year model.
Price the n8n edition your features require
Read n8n's pricing page and choose the edition that includes the features you need, such as SAML single sign-on, environments with Git, log streaming, multi-main high availability and dedicated support. Note that the Community edition is free to run but lacks several of these features, and that the Business plan is listed as self-hosted only. Ask n8n for an Enterprise quote if you need SLA-backed support, and confirm the license terms under the Sustainable Use License with your legal team, since internal business use is permitted but distribution and commercial redistribution are not. The step is complete when you have a single annual license line with a named edition and a written note on license terms.
Estimate hosting for queue mode
If you plan to run n8n in queue mode, list the main instance, the webhook processors, the worker pool, PostgreSQL and Redis, and map each to compute, storage and network on your own cloud account or data center. Remember that the encryption key must be shared with every worker and webhook processor so they can read stored credentials, which affects how you manage secrets. Use your infrastructure team's internal rates for virtual machines, managed or self-run databases and backups, and ask them to confirm sizing against your expected execution volume, which you can estimate from the recipe inventory. The step is complete when the hosting estimate lists each component, its owner and its recurring monthly or annual cost.
Cost the rebuild per recipe group
Take the recipe groups from the first step and estimate the effort to rebuild each one as an n8n workflow, including connector setup, credential recreation, on-prem connection design, error handling and testing. Use your own internal hourly rates for in-house engineers, or request a fixed-scope quote from a partner for the groups you do not want to build yourself. Treat this as a one-time cost and record the assumptions for each group, such as complexity, number of connectors and whether a recipe has a dependency on another. The step is complete when each group has an effort estimate, a rate and a total, and the assumptions are written next to the total.
Add operations and support as recurring rows
Add recurring rows for the people who will run the platform: patching and upgrades, on-call coverage, credential rotation, monitoring, backups and access reviews, and vendor support if you choose a paid support tier. Assign a share of existing staff time to each row and state it explicitly, so the budget owner can see what is absorbed and what is new headcount. Keep this separate from the license and hosting rows so the recurring total is visible. The step is complete when the operations rows sum to a recurring annual figure with a named owner for each line.
Model a three-year view
Build a three-year model with two sections: one-time costs, including the rebuild and migration testing, and recurring costs, including the Workato subscription, the n8n license, hosting and operations. Add the Workato figures for each year from the quote, and the n8n and hosting figures from your estimates, then show the cumulative totals for both paths side by side. Run a sensitivity check by changing the execution volume, the number of recipes that move in the first year and the staff time assumption, and note which input changes the result most. The step is complete when the model shows one-time and recurring totals for each platform and a short list of assumptions that the finance and integration leads have reviewed.
What the n8n license changes in the model
The n8n license is the first thing to settle, before any cost comparison. n8n's main codebase is licensed under the Sustainable Use License, which allows use or modification for your own internal business purposes and non-commercial or personal use. It does not permit reselling n8n or offering it as a managed service to others. n8n is source-available, not OSI open source, so a model that treats the self-hosted option as free software with no conditions will be wrong. Files with .ee in their name or directory are not covered by that license and require a valid n8n Enterprise License, so the license terms apply to specific parts of the code, not only to the product as a whole.
The license also changes the price model. The free Community edition is not enough for many enterprise requirements. According to n8n's pricing page, SSO and LDAP, environments with Git, and log streaming are included only in the Business and Enterprise plans, and multi-main setup for high availability is restricted to Enterprise self-hosted deployments. If your Workato comparison depends on SSO, separate environments or high availability, the license tier needed for each must be a line item in the model, not an assumption. The Business plan is listed as self-hosted only, and Enterprise is priced on request, so ask n8n for written terms covering your deployment shape and user count.
Before you commit, ask legal to confirm whether your intended use fits the internal business purposes allowed by the Sustainable Use License. Pay particular attention to any plan to run n8n for a subsidiary, a customer, a partner or a managed service run by a third party, since those uses may fall outside the internal-use grant. Ask the same question about the .ee components you expect to need. Record the answer and the license version you reviewed, because license terms can change between releases and the decision should be reviewable at renewal.
Questions buyers ask before comparing n8n and Workato costs
How much does self-hosted n8n cost compared with Workato?
Self-hosted n8n has no per-execution or per-user fee in its free Community edition, but a production team usually pays for n8n Business or Enterprise licensing, the infrastructure to run it, and the people who operate it. Workato is priced through a sales quote, so the comparison has to be made line by line: Workato subscription and usage fees against n8n license fees, hosting, database and backup services, rebuild labor, platform operations and vendor support. The n8n pricing page lists its Business plan at 667 euros per month billed annually and states that the Business plan is currently self-hosted only. Ask Workato for a written quote that names its billing units, and build your own model from the same components before deciding.
What recurs after launch, and what is a one-time cost?
The one-time costs are the inventory of existing automations, the rebuild and testing of each workflow, connector and on-prem connection setup, and the first deployment. Recurring costs include the n8n license renewal if you choose a paid edition, infrastructure for the main instance, workers, PostgreSQL and Redis, backups, patching and upgrades, monitoring, and the staff time needed to maintain credentials and workflows. Support is recurring if you buy a vendor or partner retainer. Your Workato subscription also recurs, so the savings depend on how much of the Workato bill your self-hosted running cost actually replaces.
How long does a Workato rebuild take, and what drives it?
The timeline depends on the number of recipes, how many are business-critical, how many connectors and on-prem connections they use, and how much custom logic they contain. Recipes that rely on lookup tables, complex error handling or data mapping take longer to rebuild and test than simple triggers that copy records. Your own environment matters too: network approvals for reaching internal systems, identity integration, and change control all add time. Start with the inventory from Workato's recipe lifecycle exports, then ask any partner for a written scope and timeline that lists the recipes covered before work starts.
Can our integration team do the migration without a partner?
Yes, many teams do, provided they have engineers who can operate containers, a PostgreSQL database and an identity provider, and who can test workflows against production-like data. A partner adds value when the team lacks that capacity, when the inventory is large, or when the migration has to be done in a regulated environment with documented controls. DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted platforms in the client's own infrastructure, and most engagements are fixed-scope with deliverables agreed in writing before work starts. Ask any provider for a written scope that separates what your team does from what they do.
What skills do our staff need to run self-hosted n8n?
Plan for three skill areas. Container skills cover running n8n with Docker Compose or Kubernetes, managing images, volumes and environment variables, and upgrading versions safely. Database skills cover PostgreSQL administration, backups, restores and connection management, and, in queue mode, Redis. Identity skills cover configuring SAML single sign-on with your identity provider and managing user roles. In queue mode, the main instance's encryption key must also be shared with every worker and webhook processor, so someone must own key handling and rotation. Confirm these skills in your own team before you commit to a timeline.
Does n8n Community support SSO and high availability?
No. The n8n Community edition is free, but SAML single sign-on, LDAP, environments with Git 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 and is not available in Community. Plan for a paid license if your security or availability requirements include SSO or high availability. Confirm the current feature split on the n8n pricing page before you finalize a budget, because the plan contents may change.
Does the n8n license allow us to run it for internal use?
The Sustainable Use License permits use for your own internal business purposes and for non-commercial or personal use. It does not make n8n OSI open source, and it does not allow you to offer n8n as a managed service to others. Files with .ee in their name require a valid n8n Enterprise License. Have your legal team review the license text and confirm how your internal use, any customer-facing workflows and any affiliate use fit its terms before you commit to a rollout.
How DeployOpen scopes a fixed-price implementation
DeployOpen is a Chainscore Labs company that plans, implements, hardens, documents and supports self-hosted open-source platforms inside your own infrastructure. For a Workato cost vs self-hosted n8n decision, we start with a written scope that separates licensing, hosting, rebuild and operations costs so your team can compare options on the same basis.
How we scope
- Inventory of Workato recipes, connections and on-prem agent dependencies agreed in writing before any build work starts
- Written split of n8n edition needs, hosting, rebuild effort and operations so each cost line can be quoted separately
- Confirmation of n8n license terms with your legal team, including the Sustainable Use License and Enterprise License requirements
How we build
- Deployment of n8n in your own cloud account, data center or air-gapped network, using the install method your platform team selects
- Rebuild of prioritized workflows with credentials, queue mode and encryption key handling configured to your security standards
- Testing of each rebuilt workflow against the original Workato output, with failures logged and resolved before cutover
How we hand over
- Runbooks covering deployment, upgrades, backups, credential rotation and workflow change control in your own tooling
- Evidence pack describing configuration, access controls and logging, prepared for your auditors, who issue any attestation
- Knowledge transfer sessions with your integration and platform engineers, with a documented list of open items
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover
- Retainer scope, response expectations and upgrade cadence are written into the agreement, so you can confirm them before signing
- Your team keeps ownership of the environment, and we can step back to advisory work whenever your staff take over operations
