Hi @Synaptic724,
Good question. The short version is that your users do not need to display “Powered by Modular” merely because they install, evaluate, or develop with your Python/Mojo package.
The Community License obligations apply to each party’s own use of the Modular SDK. Under Section 2.3, the “Powered by Modular” display obligation applies when the licensee is an entity and deploys Modular’s infrastructure for production, commercial usage, on each product or service incorporating the SDK.
So:
- If someone uses your package for development, testing, or non-commercial use, the Section 2.3 display obligation does not apply.
- If a business uses your package in a production commercial product or service that incorporates/deploys the Modular SDK, they would need to comply with Section 2.3, including usage notification and the “Powered by Modular” display requirement.
- If your package only contains your own Mojo/Python code and lists Mojo or mojo-compiler as an external dependency, you should make the Modular dependency and Community License clear, but that is different from bundling SDK redistributables yourself. This can be achieved by including a reference to the Modular Community License in your package’s LICENSE file or README, and note that Mojo / the Modular SDK is a required dependency governed by those terms.
- If you do bundle parts of the SDK with your package, Section 3 of the Community License applies. Among other things, your application needs material functionality beyond the SDK, your distribution terms must be consistent with the Community License, required notices and license text must be included, and you cannot redistribute SDK components as standalone libraries or tools that enable license violations. If you’re planning to bundle SDK components, reach out to licensing@modular.com so we can walk through the specifics with you.
On your AGPLv3/proprietary dual-license plan: you can license your own code separately, but Modular SDK components remain under the Modular Community License and cannot be relicensed under AGPLv3 or your proprietary license. Whether a specific AGPL distribution is compatible depends on how the project is packaged and combined with the SDK, so we can’t give a definitive compatibility determination in a forum reply. If you plan to redistribute SDK components or need a definitive answer for a commercial release, please contact licensing@modular.com.
For use of Modular or Mojo names, logos, or badge assets beyond the required ‘Powered by Modular’ display, see ourTrademark Guidelines.
Hope this helps clarify. Let us know if you have any other questions on the license. Thank you!