docs/QA-about-License.md
| 1 | # Q&A About License |
| 2 | |
| 3 | ## Why is MiniMax-H3's open-weight license currently limited to the EU, UK, South Korea, and US? |
| 4 | |
| 5 | MiniMax-H3 was built with the goal of global availability. The current territory scope is not about excluding specific countries or regions, but about recognizing that video generation models are facing a more complex and rapidly evolving regulatory environment compared with text or code models. |
| 6 | |
| 7 | Regions such as the EU, UK, South Korea, and the US are currently developing or enforcing AI-related regulations that may have specific implications for generative video models, especially around areas such as likeness generation, copyright, content safety, and responsible deployment. |
| 8 | |
| 9 | - The EU AI Act has started enforcement, while practical requirements for models capable of generating video and likeness-related content are still evolving. |
| 10 | - Similar regulatory uncertainties exist in the UK and South Korea regarding AI-generated content and video generation. |
| 11 | - In the US, AI regulation remains a rapidly changing landscape, and MiniMax is also involved in ongoing copyright-related legal proceedings specifically concerning generative video AI. |
| 12 | |
| 13 | For open-weight models, once the weights are released, developers can deploy and modify them independently. This creates different compliance challenges compared with hosted services. |
| 14 | |
| 15 | We had two options: |
| 16 | |
| 17 | 1. Wait until every jurisdiction reaches complete regulatory clarity before releasing open weights, which could take a long time while AI technology continues to evolve. |
| 18 | 2. Release the model now with a transparent license scope, while continuing to evaluate and expand availability. |
| 19 | |
| 20 | We chose the second approach. The current limitation means "not yet", not "not ever." |
| 21 | |
| 22 | ## Why can MiniMax-H3 API be used globally if open weights are restricted in some regions? |
| 23 | |
| 24 | The difference is the distribution model. |
| 25 | |
| 26 | The main concern is not the existence of MiniMax-H3 itself, but the ability to control compliance after open weights leave our infrastructure. |
| 27 | |
| 28 | For API access, MiniMax operates the serving infrastructure and can enforce appropriate safeguards, including: |
| 29 | |
| 30 | - Protection against misuse involving minors. |
| 31 | - Copyright-related compliance measures. |
| 32 | - Content safety controls. |
| 33 | - Compliance with applicable laws and regulations. |
| 34 | |
| 35 | With open weights, users can independently deploy, modify, and distribute the model, which makes it much harder to ensure the same level of compliance. |
| 36 | |
| 37 | Therefore, the API and open-weight release follow different approaches: |
| 38 | |
| 39 | - API: Globally available with built-in safeguards and responsible-use controls. |
| 40 | - Open weights: Temporarily limited in certain regions until the regulatory and compliance framework becomes clearer. |
| 41 | |
| 42 | ## Can organizations in restricted regions still use MiniMax-H3? |
| 43 | |
| 44 | Yes. |
| 45 | |
| 46 | Organizations in these regions can apply for a formal license. After reviewing the deployment scenario and confirming that appropriate compliance controls and safeguards are implemented, MiniMax may authorize usage. |
| 47 | |
| 48 | [Application form](https://platform.minimax.io/h3-license) |
| 49 | |
| 50 | Through authorized deployments, MiniMax can ensure that MiniMax-H3 is used responsibly while meeting local legal and regulatory requirements. |
| 51 | |
| 52 | ## Will MiniMax expand open-weight availability in the future? |
| 53 | |
| 54 | Yes. We will continue monitoring legal developments and reassessing the territory scope. |
| 55 | |
| 56 | Our commitments: |
| 57 | |
| 58 | - Continuously review regulations and compliance requirements across regions. |
| 59 | - Keep MiniMax-H3 API available globally, so users can continue accessing the model. |
| 60 | - Clearly communicate any future license changes instead of making silent updates. |
| 61 | - Listen to feedback from developers, researchers, and organizations affected by these restrictions. |
| 62 | |
| 63 | Our goal remains the same: bringing intelligence to everyone with responsible AI use. |
| 64 | |
| 65 | The current license scope reflects today's regulatory reality, not our long-term vision. |
| 66 | |