"co-create intelligence with everyone"
MiniMax is a multimodal foundation model provider with models for text, coding, agents, speech, video, music, image, and multimodal applications. Its products include MiniMax Agent, Hailuo AI, MiniMax Audio, Talkie, and an Open Platform for developers and enterprises.
MiniMax
LLM “co-create intelligence with everyone”
Location: China ⓘ Xuhui District in Shanghai.
Token Plan – Plus Expanded Token Plan with a higher M2.7 quota and additional daily multimodal quotas for Speech, Image, and other models.
Token Plan – Max Higher standard Token Plan with a larger request quota and expanded daily quotas for multimodal models.
Plus-Highspeed / Max-Highspeed / Ultra-Highspeed High-speed Token Plans with access to faster M2.7/M2.5 Highspeed models and expanded quotas for coding-related workflows. Other Pay-as-you-go API Standard Open Platform API key for usage-based billing according to actual consumption; supports text, video, speech, image, and additional modalities.
Audio Subscription / Video Packages Separate packages for speech and video generation with product-specific quotas and billing logic.
Local / Private Deployment Open M2 model weights can be run locally or privately via Hugging Face and frameworks such as SGLang, vLLM, Transformers, ModelScope, or NVIDIA NIM.
Target audience
MiniMax is aimed at developers, creative teams, media companies, marketing departments, app developers, agencies, and businesses that want to use multimodal AI for text, code, video, audio, music, and agents.
Outstanding features
The greatest strength is the combination of powerful text/agent models and creative models for speech, video, and music. In addition, open model weights and local deployment paths are interesting for privacy-conscious or technical teams.
Key application areas
MiniMax is suitable for coding, chatbots, agents, text generation, voice apps, video generation, music production, creative campaigns, social media, digital characters, and multimodal prototypes.
Usage & notes
MiniMax is very versatile for creative and technical testing. However, for GDPR-relevant data, companies should clarify API data protection, hosting, subprocessors, and content usage directly by contract or operate open models locally.
| Target audience | Assessment |
|---|---|
| Private individuals | Conditionally – usable via MiniMax Agent, Hailuo, Audio, or Video, but as an LLM provider it is rather technical. |
| Self-employed / freelancers | Yes – suitable for coding, text, audio, video, image, music, and agentic productivity tasks. |
| SMEs | Yes, with data protection review – strong for multimodal workflows and API projects, but the GDPR situation is not publicly transparent enough. |
| Large enterprises | Conditionally – powerful models and API, but DPA/AVV, server locations, and subprocessors must be clarified in advance. |
| Developers / teams | Very well suited – API, OpenAI-/Anthropic-compatible usage, token plan, pay-as-you-go, local model weights, and coding tool integrations. |
| Privacy-critical organizations | Conditional to critical – local/private deployments are possible for open models, but API data protection details are only publicly secured to a limited extent. |
MiniMax – Model overview
| Model / family | Type | Best suited for |
|---|---|---|
| MiniMax M2.7 | Text/agent model | Software development, agents, office tasks, long contexts, complex tasks. (platform.minimax.io) |
| MiniMax M2.7-highspeed | Fast M2.7 variant | Low latency, agile chat, coding, and agent processes. (platform.minimax.io) |
| MiniMax M2.5 | Text model | Price/performance-oriented text, coding, and agent tasks. (platform.minimax.io) |
| MiniMax M2.5-highspeed | Fast M2.5 variant | High-throughput API, fast dialogues, and automations. (platform.minimax.io) |
| MiniMax M2.1 | Text/coding model | Multilingual programming and complex tasks. (platform.minimax.io) |
| MiniMax M2.1-highspeed | Fast M2.1 variant | Latency-sensitive coding and chat applications. (platform.minimax.io) |
| MiniMax M2 | Agentic reasoning model | Advanced reasoning, agents, long context, complex workflows. (platform.minimax.io) |
| MiniMax M2-Her | Text/character model | Role interaction, emotional dialogues, character chat. (MiniMax) |
| MiniMax M1 | Open-weight reasoning model | Long thinking, complex tasks, local research, and self-hosting. (GitHub) |
| MiniMax-Text-01 | Long-context text model | Very long contexts, research, self-hosting, text and agent applications. (GitHub) |
| MiniMax-VL-01 | Vision-language model | Image understanding, multimodal QA, visual analyses. (GitHub) |
| MiniMax Speech 2.8 / 2.6 / 2.5 | Speech/audio models | Text-to-speech, voice applications, audio generation. (MiniMax) |
| Hailuo 2.3 / 2.3 Fast / Hailuo 02 | Video models | Text/image-to-video, marketing clips, creative video production. (MiniMax) |
| MiniMax Music 2.6 / 2.5+ / 2.5 / 2.0 / 1.5 | Music models | Music generation, creative audio production, sound ideas. (MiniMax) |
| Image API | Image model | Text-to-image, image-to-image, creative visuals. (platform.minimax.io) |
Hosting & Data
1) On-prem / local hosting
Meaning: The company operates the solution on its own hardware or within its own infrastructure. In the strictest sense, not only the application runs locally, but ideally the model as well.
2) Private cloud / data center
Meaning: The solution runs in a dedicated or more clearly separated cloud environment, often with a hosting provider or hyperscaler, but in a German data center or in a particularly controlled environment.
3) EU SaaS / managed
Meaning: The provider operates the solution itself as a service. The company uses the tool as a ready-made cloud service, ideally with EU data residency.
4) Hybrid
Meaning: One part of the processing remains internal / local / in a private cloud, while another part runs in an external cloud or EU SaaS.
5) AVV / DPA
Meaning: This is the data processing agreement or Data Processing Addendum. It governs that the provider processes personal data on behalf of the customer and is bound by the customer's instructions.
6) No training
Meaning: The provider does not use your prompts, uploads, attachments, chat histories, or outputs for training or improving the general model — ideally excluded by contract.
7) Open-source / transparency path
Meaning: There is a path toward greater technical transparency and sovereignty, for example through:
- open models
- documented components
- self-hostable parts
- traceable architecture
- export / switching options
| On-prem / local hosting | ✅ |
| Private cloud / data center | ❓ |
| EU SaaS / Managed | ❓ |
| Hybrid | ⚠️ |
| DPA / AVV | ❓ |
| No training on customer data | ⚠️ |
| Open source / transparency path | ⚠️ |
On-prem / local hosting: supported
Supported for MiniMax-M2.7: There is a documented "Local Deployment Guide" for Linux GPU servers and Mac Studio, including fully local operation on Apple Silicon hardware.
Private Cloud / Data Center: Indirect / Not Available
There are references to enterprise/API integrations in the pricing overview, but no specifically described dedicated private cloud, VPC, or EU data center options on the website.
EU SaaS / Managed: unclear
SaaS/API usage is clearly documented, but EU/EEA data residency, EU data centers, or a European hosting option are not specified on the website.
Hybrid: Partially
Partially inferable, as on-premises deployment is documented for MiniMax-M2.7 and self-hosted MCP services, while other features are offered as API/SaaS. However, an explicit hybrid architecture or an officially described combination of on-premises and hosted processing is not specifically guaranteed.
DPA: unclear
Although the Terms of Service mention “data privacy and security agreements” as part of the Service Rules, no specific DPA or process for entering into one is provided on the website.
No training: partial
Partially, and only for a specific area: The API documentation for the synchronous text-to-speech interface states that the interface is stateless and “the model does not store any user data.” A general, contractual prohibition on using prompts, uploads, chat histories, or outputs to train general models is not specified on the website.
Open Source / Transparency Path: Partially
There is a transparency/sovereignty path: The website documents local deployment of MiniMax-M2.7 and refers to MiniMax M2 on the website as an open-source model context. In addition, official MCP servers in Python and JavaScript, as well as self-hosting of these MCP services, are described. However, the website does not fully specify which components are open source overall.
Data Processing
For standard use, processing via the MiniMax API is documented. Files can be uploaded to the platform, and task and file management functions are described for asynchronous speech and video processing. For TTS Async, it is described that generated audio files are made available via a time-limited URL and may be lost after the expiration date; for Voice Cloning, temporary voices are described that are automatically deleted after 7 days if they are not used. However, for the European region, there is no information on in which country or region this processing takes place or whether EU/EEA data residency is available.
Conclusion
The best way, as documented on the website, to achieve greater European data protection sovereignty is through the local deployment of MiniMax-M2.7 or self-hosted MCP components. For regular SaaS/API use within the EU/EEA, however, key GDPR compliance evidence is missing. Therefore, the overall assessment for the European region is unclear and not “yes.”
Sources
- https://platform.minimax.io/docs/api-reference/api-overview
- https://platform.minimax.io/protocol/privacy-policy
- https://platform.minimax.io/protocol/terms-of-service
- https://platform.minimax.io/docs/guides/local-deploy
- https://platform.minimax.io/docs/guides/mcp-guide
- https://platform.minimax.io/docs/pricing/overview
- https://platform.minimax.io/docs/llms.txt
| On-prem / local hosting | ✅ |
| Private cloud / data center | ❓ |
| EU SaaS / Managed | ❓ |
| Hybrid | ⚠️ |
| DPA / AVV | ❓ |
| No training on customer data | ⚠️ |
| Open source / transparency path | ⚠️ |
On-prem / local hosting: supported
Supported for MiniMax-M2.7: There is a documented "Local Deployment Guide" for Linux GPU servers and Mac Studio, including fully local operation on Apple Silicon hardware.
Private Cloud / Data Center: Indirect / Not Available
There are references to enterprise/API integrations in the pricing overview, but no specifically described dedicated private cloud, VPC, or EU data center options on the website.
EU SaaS / Managed: unclear
SaaS/API usage is clearly documented, but EU/EEA data residency, EU data centers, or a European hosting option are not specified on the website.
Hybrid: Partially
Partially inferable, as on-premises deployment is documented for MiniMax-M2.7 and self-hosted MCP services, while other features are offered as API/SaaS. However, an explicit hybrid architecture or an officially described combination of on-premises and hosted processing is not specifically guaranteed.
DPA: unclear
Although the Terms of Service mention “data privacy and security agreements” as part of the Service Rules, no specific DPA or process for entering into one is provided on the website.
No training: partial
Partially, and only for a specific area: The API documentation for the synchronous text-to-speech interface states that the interface is stateless and “the model does not store any user data.” A general, contractual prohibition on using prompts, uploads, chat histories, or outputs to train general models is not specified on the website.
Open Source / Transparency Path: Partially
There is a transparency/sovereignty path: The website documents local deployment of MiniMax-M2.7 and refers to MiniMax M2 on the website as an open-source model context. In addition, official MCP servers in Python and JavaScript, as well as self-hosting of these MCP services, are described. However, the website does not fully specify which components are open source overall.
Data Processing
For standard use, processing via the MiniMax API is documented. Files can be uploaded to the platform, and task and file management functions are described for asynchronous speech and video processing. For TTS Async, it is described that generated audio files are made available via a time-limited URL and may be lost after the expiration date; for Voice Cloning, temporary voices are described that are automatically deleted after 7 days if they are not used. However, for the European region, there is no information on in which country or region this processing takes place or whether EU/EEA data residency is available.
Conclusion
The best way, as documented on the website, to achieve greater European data protection sovereignty is through the local deployment of MiniMax-M2.7 or self-hosted MCP components. For regular SaaS/API use within the EU/EEA, however, key GDPR compliance evidence is missing. Therefore, the overall assessment for the European region is unclear and not “yes.”
Sources
- https://platform.minimax.io/docs/api-reference/api-overview
- https://platform.minimax.io/protocol/privacy-policy
- https://platform.minimax.io/protocol/terms-of-service
- https://platform.minimax.io/docs/guides/local-deploy
- https://platform.minimax.io/docs/guides/mcp-guide
- https://platform.minimax.io/docs/pricing/overview
- https://platform.minimax.io/docs/llms.txt
Strengths & weaknesses at a glance
| Strengths | Weaknesses |
|---|---|
| • Very broad multimodal portfolio. | • GDPR documentation is only publicly assessable to a limited extent. |
| • Strong text/coding/agent models. | • No publicly verified EU-only operation. |
| • Audio, video, and music models from a single platform. | • No publicly verified DPA/AVV in the sources reviewed. |
| • Open-weight models and local deployment paths for multiple models. | • Multimodal data such as voice, image, and video increase data protection risks. |
Reviews
0 reviews in total
There are no confirmed reviews for this tool yet.
Submit review
Your review will only become visible after email confirmation. This protects the portal against abuse.
Report review
Please select the reason why this review should be checked.
GDPR-compliant usage possible?
For the European market, it is unclear whether the website is GDPR-compliant. On the positive side, a privacy policy with EEA/UK/Switzerland-specific information has been published, and there is a documented local deployment path for MiniMax-M2.7. However, for SaaS/API use, the website lacks essential evidence such as EU/EEA data residency, server locations, a readily accessible Data Processing Agreement (DPA), a list of subprocessors, a clear contractual exclusion of model training using customer data, and robust compliance certifications.
Positive
The website features a published privacy policy with a reference to “jurisdiction-specific provisions” for users in the EEA, UK, and Switzerland. In addition, a local deployment path for MiniMax-M2.7 is documented; there, “complete data privacy” is explicitly described for Mac Studio when operating entirely locally. Furthermore, developers can host MCP services themselves.
Negative
The website does not specify an EU/EEA server location, EU data residency, a specific, accessible text of the AVV/DPA, a list of subprocessors, an explicit opt-out from AI training for general models, or ISO 27001, SOC 2, or similar certifications. The Terms of Service name Nanonoble Pte Ltd. as the provider and refer to Singaporean law; this does not replace GDPR compliance documentation for EU/EEA use.
Server location
Not specified on the website. API endpoints are documented under 'api.minimax.io', but there is no information on the location of servers or data centers, nor is there any mention of EU/EEA data residency.