Licensing Inquiry: Commercializing a SaaS with Self-Hosted n8n as Backedn Engine

Hello n8n community,

I am building a web platform and would like to clarify the licensing requirements for my specific use case.

Product Overview: I have developed a "resume and job search” web application. The workflow is as follows:

  • Input: Users upload a resume and a job URL via my custom HTML frontend.

  • Processing: A self-hosted n8n instance (running on Docker) processes the resume and job url in the backend to generate a tailored resume, cover letter, and jobs.

  • Output: The user receives the updated resume and a personalized cover letter through their email. While also getting jobs through a job API straight to my custom frontend.

Architecture & User Access

  • Backend: n8n is used strictly as an internal backend engine.

  • No UI Access: End-users interact only with my custom web UI. They have absolutely no access to the n8n canvas, credentials, or node interface.

  • No Syncing: User accounts are managed entirely on my platform - postgres database (email/user account); there is no user account creation or syncing within the n8n instance using external accounts.

My Question: If I monetize this current platform using a freemium model, since the n8n instance is not open to the end-user, can I operate this under the standard self-hosted license (since it powers my backend only), or does this constitute a commercial use case that requires a specialized Embed or Commercial license (due to monetization efforts)?

Thank you for your time and clarification.

I think you’ll need a license for this since it’s a commercial use,

Read this and compare it with your case:

1 Like