I’m building WhatsApp automation using n8n where each client has:
Their own WAHA credentials
Their own WhatsApp number
WhatsApp as the primary user interface
I’m considering a multi-tenant architecture on a self-hosted n8n setup for scalability, where multiple client workflows run inside the same infrastructure while keeping credentials/data isolated.
My biggest question is:
Is this allowed under the n8n license/business usage terms, or would each client require a separate n8n instance/account even in a self-hosted setup?
Would love to hear from people already running agency-style or SaaS-style deployments at scale.
Hi @Ash_2007 If you’re self-hosting n8n for an agency/SaaS-style setup, the important part is how you’re offering the service.
Using one self-hosted n8n instance for multiple clients internally is usually fine
But if clients directly access/use n8n as part of your product/platform, licensing can become more specific
The safest approach is to review the official licensing terms or contact the n8n team directly for clarification on your exact SaaS model.
From a technical side, a multi-tenant setup with isolated credentials/data is a pretty common architecture for this kind of WhatsApp automation
@Niffzy Clients having nothing to with backend, they just use whatsApp interface as chatbot and only have access to their database that’s it nothing else is visible to them!! Now can you give me a clarity whether it requires license
Based on what you described, this typically does not require an embedded/OEM license because your clients are only interacting with the system through WhatsApp and are not getting direct access to the n8n editor/platform itself.
Only if Clients only use the WhatsApp chatbot
They do not access the n8n UI/editor
They cannot create/edit workflows
Each client only accesses their own data/database
You are providing it as a managed automation service
Then it generally falls under a normal self-hosted/service usage model rather than reselling n8n as a standalone workflow product. The main concern usually starts when:
You expose the n8n editor to customers
Customers build/manage their own workflows
You white-label n8n as your own automation platform/SaaS product
For official clarification, you should still review the licensing terms or contact n8n official licensing page or n8n support/community for a definitive legal answer.
oi @Ash_2007
I’d recommend diving into those docs for a better understanding. I’ll admit I got a bit confused while analyzing this and still haven’t formed a solid opinion on the topic yet
Running exactly this type of setup — single self-hosted n8n instance handling multiple client WhatsApp automations with isolated credentials per client.
Niffzy’s explanation is accurate. The key distinction: if clients never touch the n8n editor (they only interact via WhatsApp, and you manage the workflows), you’re operating in standard agency/service mode, not reselling n8n as a platform.
Practically, for credential isolation at scale, using n8n Projects is the cleanest approach — each client gets their own project with scoped credentials. Combined with n8n’s RBAC, you can prevent cross-client data bleed at the application level.
