Clarification Needed on Using Flowise Codebase Without Enterprise License + Open Source vs. Commercial Features

[GW00241522]

Hello Flowise Team,
I hope you're doing well. I'm currently working with the Flowise codebase and would like to confirm a few things regarding licensing, especially when not using the Enterprise version.

🔧 My Use Case:
I have cloned the Flowise repository from GitHub.
I’ve made customizations to the codebase, including:
-Adding custom MCP tools
-Implementing LLM authentication logic
-Creating custom nodes
-etc
I’m using the Flowise frontend UI to visually build Agentic workflows, and planning to deploy the resulting chatbot in a commercial setting.
I do not plan to purchase an Enterprise license , and no ENTERPRISE_KEY is set in my .env file.

❓ My Questions:

1. How can I verify whether my current application (after modifications and extensions) includes any code from the /packages/server/src/enterprise directory or other files under commercial licensing?
2. Are there any specific indicators, logs, or checks I can perform to ensure that no Enterprise-restricted code is being used?
3. Would it be safer to remove the entire /packages/server/src/enterprise folder from my local repo before building and deploying my customized version?
   If so, are there any dependencies or side effects I should be aware of when removing this folder?
4. Could you please clarify which features are considered part of the Commercial License versus the Apache 2.0 Open Source License?
   For example:
   What are the enterprise-only features (e.g., RBAC, multi-tenancy, SSO)?
   Which features are available for free use under Apache 2.0?
   Is there an official list or documentation outlining these distinctions?

🙏 Additional Request:
If possible, could you also provide any guidance or best practices for safely using and modifying the open-source version of Flowise without inadvertently including Enterprise-licensed components?

Thank you very much for your help in advance!
Best regards