Proposal for a Flexible, Threshold-Based Commercial License
Hello m-a-p,
I would like to propose a licensing model that keeps YuE2 broadly accessible while creating a clear path for commercial compensation as users and businesses scale their use.
The proposed approach would make the model available for free commercial use under defined conditions. Users could develop products, services, integrations, and derivative tools without an upfront licensing fee. A separate commercial payment or agreement would apply only when a user exceeds an agreed revenue, sales, usage, funding, or organizational threshold.
Proposed licensing structure
Free usage tier
Users may:
- Download and run the model;
- Use it for personal, research, nonprofit, and small-scale commercial projects;
- Integrate it into products and services;
- Fine-tune or adapt it, subject to the license terms;
- Sell products or services that use the model.
Commercial threshold
A paid license would be required only when one or more of the following limits is exceeded:
- [Annual revenue threshold];
- [Total product sales threshold];
- [Monthly active-user threshold];
- [Inference or API usage threshold];
- [Company size or funding threshold];
- [Number of commercial deployments];
- [Enterprise or hosted-service use].
For example, a user could commercially use the model without charge until their product generates more than [$X in annual revenue], reaches [X users], or exceeds [X monthly generations].
Scaled commercial license
After the threshold is reached, the user would enter into a paid commercial agreement. Pricing could be based on:
- A fixed annual license fee;
- Usage-based fees;
- A percentage of revenue above the threshold;
- A per-unit or per-generation fee;
- An enterprise subscription;
- A negotiated API or hosted-service agreement.
The fee should apply only after the threshold is exceeded, rather than retroactively charging users for earlier use.
Suggested principle
The license should distinguish between:
- Open access for individuals, researchers, developers, startups, and small businesses;
- Standard commercial use for products operating below the agreed threshold;
- Enterprise or large-scale use requiring a paid license or direct agreement.
This would allow the model to spread widely and encourage experimentation while ensuring that large commercial users contribute financially when their use creates substantial value or imposes significant infrastructure and support costs.
Additional terms
The license could also define:
- Prohibited uses;
- Attribution requirements;
- Rules for redistributing model weights;
- Conditions for hosting the model as an API;
- Requirements for fine-tuned versions;
- Whether generated outputs may be sold commercially;
- Reporting and audit procedures;
- Different thresholds for startups, nonprofits, and enterprises;
- Separate pricing for self-hosted, API, and managed-cloud use;
- A reasonable transition period after a user crosses the threshold.
I believe this model would combine the advantages of open access with a sustainable commercial structure. It would reduce barriers for smaller developers while giving m-a-p a clear way to earn revenue from large-scale or highly profitable deployments.
I would be glad to discuss the appropriate thresholds, qualifying uses, and payment structure.
Best regards,
Adam Wayne