n8n instance per client: why it beats a shared instance

Ask why agencies move to one n8n instance per client and the answer is rarely a feature — it's an incident. A shared instance means one bad workflow, one credential leak, or one runaway loop touches every client at once. Instance-per-client draws a hard line around each one.

The isolation argument

Separate instance means separate credentials — no client's API keys sit in the same store as another's. Separate failure domain — a workflow error, a rate limit, or a crash in one instance doesn't propagate. And a clean handover — if a client leaves, you hand over or delete exactly one instance, not a set of tagged workflows tangled into a shared system.

The tradeoff isn't subtle: it's operational, not financial. Every instance you add is another thing to patch, monitor, back up and log into separately.

The DIY reality

The evidence that this overhead is real isn't theoretical — it's a string of people building tools to manage it themselves, within a five-week window on r/n8n and the n8n community forum:

• A builder (SiennaBase) hand-rolled container-per-client isolation on a shared box, after describing the alternative as 'every new client meant the same 2-3 days of manual work.' (community.n8n.io, Jun–Jul 2026)
• A custom Stripe true-up billing pipeline, built to bill per client. (r/n8n, Jul 26 2026)
• A client health-score engine, built in Notion because nothing tracked it natively. (r/n8n, Jul 30 2026)
• An open-source n8n cost tracker that groups workflows by client with per-client budgets — 73 points on the thread. (r/n8n, Aug 9 2026)

None of these are the isolation itself — they're the management layer isolation creates a need for once you have it. The credential side is still unresolved: a July thread on community.n8n.io was asking, without a settled answer, how to handle per-client Google OAuth cleanly on self-hosted n8n.

What people say once they're living it

“After a while the more client instances the more overhead?”

r/n8n, Jul 2026

“We've got 7 client instances and i'd rather not add an 8th line to that notepad.”

r/n8n, Jul 2026

That's the real cost of instance-per-client: not the isolation decision, which is close to obviously correct, but the tracking, billing, propagation and OAuth setup that isolation forces you to solve yourself, once per client, forever — unless something else solves it once.

What a control plane adds

This is the gap we're building Tenvik to close. n8n runs unmodified, on the agency's own infrastructure — their Hetzner, Hostinger, DigitalOcean or AWS account — so workflow JSON imports and runs exactly as it would anywhere else, because it is exactly n8n, not a reimplementation of it. Tenvik sells the layer on top: one place to see every client instance, propagate a workflow change across all of them instead of redoing it by hand, track cost and budget per client the way the 73-point open-source tracker was trying to do generically, and hold credentials with proper per-client scoping.

Disclosure: we build and sell this, so read the recommendation with that in mind. The underlying case for instance-per-client doesn't depend on us — it's the pattern agencies converge on once a shared instance burns them, control plane or not.