n8n Business Tier Review: Is €667/Month Worth It for Production Workflows?

n8n Business is the self-hosted plan for teams that need governance, scale and longer operational visibility. At €667 per month when billed annually, it includes 40,000 monthly workflow executions, SSO/SAML/LDAP, Git version control, environments and 30 days of Insights. It is a sensible upgrade when those controls are the bottleneck, but it does not replace a production workflow operating loop.

What does n8n Business include?

n8n Business is a self-hosted plan for companies with fewer than 100 employees that need collaboration and scale. The current plan includes 40,000 executions each month, six shared projects, SSO/SAML/LDAP, 30 days of Insights, different environments, scaling options and Git version control.

That combination matters when a team has outgrown one shared instance. Environments reduce the risk of changing a live workflow from the editor. Version control makes workflow changes reviewable. SSO and directory integration make access easier to govern. The execution allowance is charged per completed workflow run rather than per node step, so a multi-step workflow counts as one execution.

Is €667 per month the real cost of n8n Business?

The published annual-billing price is €667 per month, before the cost of hosting, database operations, observability and the people who operate the workflows. It is best treated as the price of the n8n plan, not a complete reliability budget.

Teams should also model their trigger volume. A workflow scheduled every five minutes runs roughly 8,600 times in a 30-day month before retries or event-driven runs. Business includes 40,000 executions, and n8n says workflows continue to run beyond a quota but overage charges can apply. A license can be used on unlimited instances, with combined production usage counting toward the quota.

When is Business the right n8n upgrade?

Business is a strong fit when the immediate problem is controlled collaboration. Choose it when you need identity management, a development and production separation, Git-backed change history, more shared projects or a longer Insights window.

It is not an either-or decision against self-hosting. The plan is designed for self-hosted deployments, so you still retain infrastructure control. The practical question is whether a missing platform entitlement is stopping safe delivery. If the answer is yes, the Business tier directly removes that constraint.

What does Business not do for a failing workflow?

Business gives useful execution history and operational controls, but it does not automatically decide whether a live workflow repaired the right field mapping, rerun a failed case with verified output, or turn an error payload into a bounded remediation. Those are operating tasks around a real instance.

For example, a payment-sync workflow can fail because an upstream API changes an object shape. Git history tells the team what changed and Insights helps locate the execution. Someone still needs to inspect the input and node output, validate a fix against the instance, rerun safely and confirm the downstream record is correct. This distinction is important: platform controls reduce risk, while an operational loop closes the incident.

How should a team evaluate the upgrade?

Start with three checks. First, list workflows that need production versus development separation and identify the people who require access. Second, calculate expected monthly executions from schedules, webhooks, retries and test traffic. Third, review a month of incidents: how long did it take to find the execution, isolate the cause, apply a change and verify the replay?

If access control, environments or change history are the repeated failure points, n8n Business has a direct answer. If the slow step is evidence-driven diagnosis and verified recovery on running workflows, add a reliability process as well. The two investments are complementary.

Where does Synta fit with n8n Business?

Synta does not replace n8n Business or claim its governance features. It is the production-reliability layer for n8n, working with the real instance to inspect running workflows, validate changes, trigger executions, capture errors, apply bounded fixes and verify reruns. That matters after a workflow exists and the job is keeping it producing correct outcomes.

Before upgrading, separate two bottlenecks: governance and incident recovery. If your team needs SSO, environments, or Git history, Business solves that. If failures still take hours to diagnose and verify, see how Synta helps an operator inspect and recover a real n8n workflow.

FAQ: Is n8n Business hosted by n8n?

No. The Business plan is listed as self-hosted, while n8n's Cloud Starter and Pro plans are hosted by n8n.

FAQ: Does Business include unlimited workflow executions?

No. The current Business plan includes 40,000 monthly workflow executions. Each complete workflow run counts as one execution regardless of its number of steps.

FAQ: Does Business include dedicated support?

No. n8n describes Business as self-serve with forum support. Dedicated support with an SLA is an Enterprise feature.

FAQ: Can Business prevent every production workflow failure?

No. It provides governance and operational visibility, but a team still needs to diagnose failed data, validate a change and verify the recovery outcome.