- Which models can I use?
- Qwen, DeepSeek, Kimi and more. Exact versions change as labs release new models; the current list will be published on the models page.
- Where are Gateway requests processed, and what happens to my data?
- Gateway requests are processed by our upstream provider in mainland China, under PRC law. Meruva stores account details, billing records and usage metadata (model, token counts, cost, time), not your prompts or outputs. Our upstream says it keeps no request logs, but until we can publish written terms, assume prompts may be retained. The Gateway suits experiments, side projects and code you're happy to share; please don't send personal, regulated or confidential data. For that, use Meruva Sovereign, which runs in your jurisdiction. Full details are on our Trust page. Read the Trust page.
- Why no US models?
- We focus on open frontier models you can also run yourself. That keeps the Gateway and the sovereign stack consistent, and US labs' terms do not allow us to resell their APIs. If you need US models, use them directly alongside Meruva.
- Does Meruva train on my data?
- No. Meruva never trains on your data.
- How is pricing set?
- Gateway: pay as you go by card, per model usage, shown in the dashboard before you commit. Sovereign: a scoped project plus a support agreement, quoted after discovery. Published prices are coming soon.
- Can I start on the Gateway and move to Sovereign later?
- Yes. It is the same stack, so your integrations carry over, and your data moves into your own jurisdiction.
- How do I leave?
- The API is OpenAI-compatible and the models are open-weight. Change your base URL and go.
- What certifications do you hold?
- None yet. Meruva doesn't hold ISO 27001, SOC 2 or Cyber Essentials certification, and isn't listed on G-Cloud. If your procurement needs one of these, tell us early and we'll be straight with you about timing.