N8n as a SaaS backend — How much does the license allow?

Questions
3

Yes, I am very sorry. We really have to get better at communicating what is allowed and what is not. It is something we want to simplify.

  1. n8n as backend → Totally OK
  2. How users log into your SaaS does not make a difference → Totally OK
  3. As connecting to user’s account and not an own one → Needs Embed (assuming you then connect via n8n to the users account. If your SaaS does it somewhere else, then obviously totally OK. It matters what you use n8n for, and not what other external code does.)
  4. Does not matter where they are stored → Needs Embed
  5. You can for sure create an MVP and test it. But if you launch it to the public and make it accessible for external people, it normally needs an embed license. We should, however, probably consider adding something in the future to allow smaller deployments, no matter what.
  6. That is something we are working on right now to simplify. The switch will happen in Q1. So that users with an Enterprise license can do that.

I hope that is helpful.