Official n8n Select PartnerBefore n8n touches production data, your security team wants single sign-on, credentials in the vault and audit events in the SIEM. We deploy n8n Business or Enterprise in your cloud account, connect it to your identity provider and vault, then build and run the workflows on it.
Bring your workflow count and your identity provider, and Jason maps the plan with you on the call.
Clients include
All three plans self-host and run queue mode. They differ in sign-in, change control, security tooling and how much volume one instance carries.
| Community | Business | Enterprise | |
|---|---|---|---|
| License cost | No license fee to self-host | Annual fee plus executions | Annual fee plus executions |
| Monthly volume | No n8n limit | Up to 2 million executions | Uncapped |
| Scaling | Queue mode | Queue mode | Queue mode, multi-main and workers view |
| Sign-in | n8n accounts only | SSO and LDAP | SSO and LDAP, plus scoped API keys |
| Change control | Edits made in production | Environments and Git | Environments and Git |
| Security tooling | Not included | Not included | External secrets and log streaming |
| History kept | Limited | 180 days of logs, 30 days of workflow versions | Unlimited logs, 365 days of workflow versions |
| Support from n8n | Community forum | Ticket support | Dedicated support and a customer success manager |
Source: n8n, Partner Pricing enablement deck (June 2025). n8n changes plan contents and prices from time to time, so we confirm the current terms with n8n before you sign.
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.
Sign-in stays inside n8n, a handful of people build, and nobody needs an audit trail yet. Community is the right place to prove the first workflow.
Sign-in has to go through your identity provider, and changes have to move from staging to production through Git before they go live.
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.
The Community edition runs the same workflows. Business and Enterprise add the controls a security team asks for once several departments share one instance.
Sign-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.
Workflows are built in development, reviewed, and promoted to production through source control, so nobody edits a live workflow by hand.
Credentials 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.
Two 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.
Architecture
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.
Your account holds the n8n mains for the editor, webhooks and triggers, Redis with parallel workers, and Postgres for workflows and execution history, backed up with retention you set.
Sign-ins, workflow changes and runs arrive as they happen.
Model calls go to Claude, OpenAI or a model you host, and prompts leave only under agreements you hold. See the enterprise context layer
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. See how we work
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.
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 reach production through source control, with retries, an error workflow and alerts in place. Moving from Zapier, Make or a Community instance, old and new run side by side until the outputs match.
We watch executions and worker load, apply n8n upgrades, and fix workflows when an upstream API changes, through AI managed services.
Three clients run n8n we built, from a nightly scheduler on top of an ERP to multi-agent content pipelines. See all case studies
Five sync workflows feed a Supabase planning cache every night. The agent weighs healing intervals, roles and urgency, books the slots and reports every exception.
Content pipeline on n8nn8n 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.
Our listing sits on experts.n8n.io, the directory n8n runs for buyers looking for implementation partners. View our n8n listing
A scheduler on Odoo that places 1,500 dental appointments a week, and GoKickflip's content pipeline, which runs about 33 n8n executions per article.
We count your expected executions and map your security requirements first, so you buy Business or Enterprise because you need it.
Yes. The Community edition is released under n8n's Sustainable Use License, which lets you self-host it for your own business processes with no license fee. The license restricts reselling n8n itself, for example hosting it as a paid service for other companies, which needs a separate agreement with n8n. Business and Enterprise add features, not the right to commercial use.
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 do not count. We estimate your execution count during scoping, so you know which plan and volume to ask n8n for. Your cloud provider bills the infrastructure separately.
Business covers SSO and LDAP, roles, environments with Git and queue mode, up to 2 million executions a month. Enterprise adds multi-main, 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.
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 log streaming. n8n says it aligns its own security program to SOC 2, with annual audits by an independent auditor. Our AI agents in healthcare page shows a regulated setup.
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.
Your n8n stays self-hosted in your own cloud account, and we run it through AI managed services: alerts on failed executions, worker scaling, n8n upgrades and fixes when an upstream API changes. Your team keeps admin access and documentation for every workflow.
Agents that answer or route tickets, like our enterprise AI chatbot, finance workflows such as AI invoice automation, and ERP integrations like the one in our n8n and SAP guide. Our n8n agency page covers that work, and n8n training teaches your team to build on the instance.
Answer a few questions about your team and what you want automated, then Jason scopes it with you on the call.
