n8n Enterprise, Set Up and Run Inside Your Own Cloud
Before n8n touches production data, your security team wants single sign-on, credentials in the vault and audit events in the SIEM. As an n8n Select Partner, we deploy n8n Business or Enterprise in your cloud account, connect it to your identity provider and vault, and build and run the workflows on it.
Your cloud accountQueue modeYour identity provider
What we configure on day one
The controls your security review asks for, set up before the first workflow goes live.
SSOSAML or LDAP against your identity provider
RolesProjects per team, with scoped API keys
EnvironmentsDevelopment to production through Git
SecretsCredentials read from your vault
Log streamingAudit events sent to your SIEM
MainsTwo
RedisQueue
WorkersScale out
n8n Select Partner
Listed in n8n's expert partner directory
Your cloud
AWS, Azure, Google Cloud or your own servers
Right-sized plan
Community, Business or Enterprise, sized to your volume
Run after launch
Upgrades, alerts and fixes by a named team
Ovidius clients include
n8n Enterprise Rollouts by an Official Select Partner
n8n lists Ovidius as a Select Partner in its expert partner directory, where companies look for teams to build and run n8n. For an Enterprise rollout, the status comes with work you can check.
Listed by n8n
Checkable in n8n's own directory
Our Select Partner listing sits on experts.n8n.io, the directory n8n runs for buyers looking for implementation partners.
A scheduling agent on Odoo that places 1,500 dental appointments a week, and a content pipeline that runs 33 agent executions per article for GoKickflip.
The Community edition runs the same workflows. Business and Enterprise add the controls a security team asks for once several departments share one instance.
Single sign-on and rolesSign-in through SAML or LDAP, projects that keep each team's workflows and credentials apart, and API keys scoped to what each integration needs. Enterprise AI governance covers the policy around it.
Environments through GitWorkflows are built in development, reviewed, and promoted to production through source control, so nobody edits a live workflow by hand.
Secrets and log streamingCredentials stay in HashiCorp Vault, AWS Secrets Manager, Azure Key Vault or Google Cloud Secret Manager. Audit events stream to your SIEM, so security sees who changed or ran a workflow.
Multi-main and uncapped volumeTwo or more main processes behind a load balancer keep the editor and webhooks up when one fails, and Enterprise sets no ceiling on monthly executions. AI managed services keeps it running.
n8n Enterprise Architecture: SSO, Vault, Queue Mode and SIEM
Everything n8n stores, from workflows and credentials to execution history, stays in your cloud account. Sign-in, secrets and audit events run through the systems your security team already operates.
Identity provider
SAML or LDAP
Okta, Entra ID or your own directory signs every user in
Your vault
External secrets
n8n reads credentials at run time instead of storing them
Your cloud account
n8n mains
Editor, webhooks, triggers
Behind a load balancer
Redis
Execution queue
Holds each run until a worker is free
Workers
Run in parallel
Add workers as volume grows
Postgres
Workflows and execution history
Backed up, with retention you set
Git repository
Environments
Development→Staging→Production
Your SIEM
Log streaming
Sign-ins, workflow changes and runs, as they happen
Model providers you approve
Claude, OpenAI or a model you host
Prompts leave only under agreements you hold
If you handle patient or financial data, n8n runs under the access controls and agreements you already hold with your cloud provider. Our AI agents in healthcare page shows that data boundary for a regulated build, and the enterprise context layer is how agents on n8n get your business rules.
n8n Community vs Business vs Enterprise
All three plans self-host and run queue mode. The differences sit in sign-in, change control, security tooling and how much volume one instance can carry.
Community
Business
Enterprise
License cost
CommunityFree to self-host
BusinessAnnual fee plus executions
EnterpriseAnnual fee plus executions
Monthly volume
CommunityNo n8n limit
BusinessUp to 2 million executions
EnterpriseUncapped
Scaling
CommunityQueue mode
BusinessQueue mode
EnterpriseQueue mode, multi-main and workers view
Sign-in
Communityn8n accounts only
BusinessSSO and LDAP
EnterpriseSSO and LDAP, plus scoped API keys
Change control
CommunityEdits made in production
BusinessEnvironments and Git
EnterpriseEnvironments and Git
Security tooling
CommunityNot included
BusinessNot included
EnterpriseExternal secrets and log streaming
History kept
CommunityLimited
Business180 days of logs, 30 days of workflow versions
EnterpriseUnlimited logs, 365 days of workflow versions
Support from n8n
CommunityCommunity forum
BusinessTicket support
EnterpriseDedicated support and a customer success manager
n8n changes plan contents and prices from time to time, so we confirm the current terms with n8n before you sign.
Not sure which plan you need?
Bring your workflow count and your identity provider, and we will map the plan on the call.
Most teams do not need Enterprise on day one. The answer depends on who signs in, where credentials live and what your security team needs to see.
Community
One team, internal workflows
Sign-in managed inside n8n, a handful of builders, no audit requirement yet. Free to self-host, and the right place to prove the first workflow.
Business
Several teams on one instance
Sign-in has to go through your identity provider, and changes have to move from staging to production through Git before they go live.
Enterprise
Security owns the sign-off
Audit events must reach the SIEM, credentials must stay in the vault, the editor cannot go down with one main process, or volume runs past 2 million executions a month.
How We Roll Out n8n Enterprise
Four phases with one accountable team. How long each takes depends on how many workflows you run and what they connect to, so we tell you before you commit.
ScopeVolume, identity and data first We count your expected executions, map who signs in and which systems n8n will touch, and recommend Community, Business or Enterprise before you talk to n8n sales. Larger programs start with an AI Audit that ranks use cases first.
BuildInfrastructure in your account We deploy n8n in queue mode with Postgres and Redis in your cloud, connect SSO and your vault, set up projects and roles, and send audit events to your SIEM. Workflows are built and tested in the development environment.
ShipPromoted through Git Workflows reach production through source control, with retries, an error workflow and alerts in place. If you are moving from Zapier, Make or a Community instance, old and new run side by side until the outputs match.
RunMonitored after launch We watch executions and worker load, apply n8n upgrades, and fix workflows when an upstream API changes, through AI managed services. How we work covers each phase in full.
n8n Builds Already in Production
A Dutch Odoo implementation partner had spent a year trying to automate scheduling natively in Odoo for a dental care group. We built it as an agent on n8n instead.
Odoo + n8n · Dental care scheduling
An n8n agent schedules 1,500 dental appointments a week on top of Odoo
Source
Odoo ERP
Practitioners, locations, treatment series
Nightly
Five sync workflows
Into a Supabase planning cache
n8n agent
Selects the slots
Healing intervals, roles, urgency
Out
Booked calendar
Plus a report on every exception
1,500
Appointments scheduled per week, processed nightly
200
Practitioners coordinated across multiple locations
25K
Dependent residents served across the network
5
Sync workflows between Odoo and Supabase
Ovidius did in weeks what we couldn't build natively in Odoo for a full year. They architected an AI-powered n8n layer on top of our ERP that now schedules well over a thousand appointments a week automatically. They are our preferred AI delivery partner.
Accountable for delivery and everything after launch.
Questions About n8n Enterprise
Can we use n8n for commercial purposes?
Yes. The Community edition is released under n8n's Sustainable Use License, which lets you self-host and run it for your own business processes at no license cost. What the license restricts is reselling n8n itself, for example hosting it as a paid service for other companies, which needs a separate agreement with n8n.
Business and Enterprise are paid licenses on top of the same software. They add the features in the comparison above, not the right to use n8n commercially.
How much does n8n Enterprise cost?
n8n prices Business and Enterprise as an annual fee that includes a block of executions, with more volume bought in packages. An execution is one production run of a top-level workflow, so sub-workflows and test runs in the editor do not count.
That makes your execution count the number that decides the price. We estimate it from your workflows during scoping, so you know which plan and volume to ask n8n for. The infrastructure in your cloud is billed by your cloud provider, separately from the license.
What is the difference between n8n Business and Enterprise?
Business covers SSO and LDAP, roles, environments with Git and queue mode, up to 2 million executions a month. Enterprise adds multi-main for high availability, external secrets, log streaming, scoped API keys, unlimited log retention, uncapped volume and a dedicated support contact at n8n.
If your security team does not need audit events in a SIEM or credentials in a vault, Business is usually enough. The plan comparison above sets the two side by side.
Is n8n secure enough for regulated industries?
Self-hosted, n8n runs inside your own cloud account under the controls and agreements you already hold, and Enterprise adds SSO, vault-based secrets and audit events streamed to your SIEM. n8n says it aligns its own security program to SOC 2, with annual audits by an independent auditor.
The deployment still has to be set up for your rules: execution data pruned or not saved where it holds personal data, and model calls sent only to approved providers. Our AI agents in healthcare page shows that setup, and enterprise AI governance covers the controls around it.
Can we upgrade our existing n8n instance to Enterprise?
Yes. Enterprise features switch on with a license key on a self-hosted instance, so your workflows and credentials stay where they are. If the instance runs on SQLite or in a single process, we move it to Postgres and queue mode first, then connect SSO and set up environments.
Who runs n8n after launch?
We do, through AI managed services: alerts on failed executions, worker scaling, n8n version upgrades, fixes when an upstream API changes, and new workflows as your needs grow. Jason, our COO, is accountable for everything after launch. Your team keeps admin access and documentation for every workflow.
Tell us how many workflows you run today, who needs to sign in and what your security team asks for. On the call we tell you which n8n plan fits, what the rollout involves and what the build would take. If n8n is one part of a wider AI program, our enterprise AI consulting team scopes the rest.
