Task 2: How should we handle AGPL and GPL licensed tools in NEXUS?

[BasilSuhail]

Context

As we move into Task 2 (Audit License Compatibility), we need a clear policy for handling non-MIT licensed tools.

From the initial research, several strong candidates use AGPL or GPL licenses:

Tool	License	Module
Nextcloud	AGPL	Productivity Suite
ERPNext	GPL	ERP (Premium)
Kiwix	GPL	Knowledge Base
Vaultwarden	AGPL	Password Manager
n8n	Fair Code (Sustainable Use)	Automation

Questions for discussion

1. Should AGPL tools like Nextcloud be offered as optional Docker Compose services that users deploy separately, or should we build an API bridge wrapper to keep them at arms length while still integrating?

2. For GPL tools like ERPNext, the current plan is to make them paid premium add-ons. Is there a better approach?

3. How strict should we be with the MIT-only policy? Some Apache 2.0 tools (Home Assistant, Matrix Synapse) are compatible with MIT. Should we explicitly allow Apache 2.0 as a first-class citizen alongside MIT?

4. For the license audit document itself, what format works best? A simple table per tool, or should we include a scoring rubric?

Would love your input @saadsh15

[saadsh15]

This would not pose as an issue to us since we plan to opensource our tool. Out main issue will be tackling Apache license for technologies like n8n because we cannot integrate it directly into our tool.