Trying to create a Multi-tenant n8n system without breaking ToS

Questions
1

Describe the problem/error/question

I’m building a multi-tenant SaaS for contractor businesses that needs to integrate with their CRMs (ServiceTitan, Housecall Pro, etc.). My architecture stores client OAuth tokens in Supabase (not in n8n’s credential system) and passes them to n8n workflows at runtime via webhook payloads. n8n never stores the tokens, just uses them for API calls during execution.
My questions:
Does this architecture comply with the Sustainable Use License, or does passing client OAuth tokens at runtime still require an Embed license?
If this requires the Enterprise plan, what’s a viable alternative? Using API keys for CRMs that support them? Building a different token management approach? Limiting to only CRMs with API key auth?
If I have to go single-tenant, how do experienced n8n developers manage updates/maintenance across 30+ instances without drowning in manual work?

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hi @Zaki_Shah

Welcome to the n8n community!!

Based on the official docs and n8n team clarifications, this architecture is not covered by the Sustainable Use License.

The deciding factor is that n8n executes requests using each client’s own OAuth credentials, even if those tokens are only passed at runtime and not stored. n8n explicitly states that this pattern requires an Embed/commercial agreement, regardless of token storage or proxying.

To stay within SUL, n8n must use only your company’s own credentials (API keys or service accounts). If per-client OAuth is required, the supported options are either an Embed license or running one n8n instance per client on the client’s own infrastructure, where you act as the maintainer.

Anything else falls outside the clearly permitted SUL use cases, and n8n recommends contacting them directly for a formal ruling.

3

Hi @Zaki_Shah Welcome!

I agree with @tamy.santos, but The multi-tenant SaaS architecture will require an n8n Embed license (pricing starts at $50,000/year as what i have found) the Sustainable Use license does not permit use by 3rd parties it only allows internal use by your business if this is too expensive for you, then consider using a dedicated embedded iPaaS platform like Prismatic or building custom integrations.