Advice Needed: Running n8n for Multiple Clients (Agency Setup)
Hey everyone 👋I’m running an automation agency and looking for advice from people who are already using n8n with real clients.
What I need:
  • Each client must have a fully isolated n8n instance (no shared workflows, credentials, or execution data)
  • Setup must be 100% compliant with n8n licensing
  • Ability to manage multiple client instances as an agency
  • Clients should only see their own automations
  • Access automations via a white-labeled subdomain (e.g. client1.ouragency.com, client2.ouragency.com)
  • Needs to scale from a few clients to 100+
What I’m trying to avoid:
  • Shared multi-tenant n8n setups
  • Non-compliant licensing workarounds
  • Heavy DevOps complexity if possible
Questions for those already doing this:
  • How are you hosting n8n for clients today?
  • Are you using one VPS per client, multiple instances per server, or something else?
  • How do you handle white-labeling and client access?
  • Any gotchas with licensing I should be aware of?
  • Any lessons learned or things you’d do differently?
Thanks in advance 🙌
Looking for real-world experience, not theory.Appreciate any insights 🙏
4
2 comments
Syed Bilgrami
4
Advice Needed: Running n8n for Multiple Clients (Agency Setup)
AI Automation Society
skool.com/ai-automation-society
A community built to master no-code AI automations. Join to learn, discuss, and build the systems that will shape the future of work.
Leaderboard (30-day)
Powered by