Is this considered a license violation?

Questions
1

So, I have read the license terms for Community Edition. I am using it for internal business purposes and not selling it.

Is it considered a violation of terms if I remove feature gates for features only available for enterprise if it doesn’t use a .EE file?

For example, in users.controllers.ts:307 we have a decorator @Licensed(‘feat:advancedPermissions’). Can I remove this line and use the route normally since it is not on a .EE file and I’m not selling any software?

image
image512×157 14.4 KB

I’m trying to understand how far I can go when modifying code without violating the Sustainable Use License.

2

Technically since you’re not selling the software and it’s an internal modification, removing @Licensed ‘feat:advancedPermissions’ to unlock advanced permissions for your own use might not break the letter of the license especially because it’s not in a .ee file. But it could be against the spirit of the license, which aims to protect enterprise features for paying customers. If n8n audited your setup let’s say, if you asked for support, they might argue it’s a violation, even for internal use because you’re accessing functionality they gate for revenue.

2 Likes
3

How Far Can You Go? @j-fal
You can modify the code freely for internal purposes, add features, fix bugs, whatever as long as you keep the license terms and copyright notices intact

  • Don’t distribute the modified version outside your organization.
  • Don’t use it in a way that directly competes with n8n’s paid plans

Hope this helps

2 Likes
4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.