Question
Hey,
First off, love what you're building with OpenCode Go — the curation angle and pricing make a lot of sense for reliable model access.
I have some questions about the Go plan documentation that I think need clarification:
The infrastructure claim:
Your docs state that Go models are "hosted in the US, EU, and Singapore for stable global access." However, when I tested the API with Qwen3.5 Plus (which is on your Go model list), I received this error:
Error from provider (Alibaba): You exceeded your current quota, please check your plan and billing details
This error coming directly from "provider (Alibaba)" suggests that Go is actually proxying requests to Alibaba's DashScope infrastructure, not hosting them on OpenCode-controlled servers.
Looking at your codebase (specifically the AI SDK packages referenced in the endpoint table), models like Qwen use @ai-sdk/alibaba, Kimi uses Moonshot's infrastructure, etc., which further suggests third-party proxying rather than self-hosting.
What I need clarified:
- Which Go models are actually on OpenCode-owned/controlled infrastructure?
- Which are proxied through third-party providers (Alibaba, Moonshot, etc.)?
- For proxied models, what exactly does "zero-retention" cover? Is it just between the user and OpenCode, or does it include guarantees about the upstream provider's data handling?
- For Chinese-based models, does hosting data on US/EU/Singapore infrastructure change the compliance obligations under Chinese data residency laws?
Why this matters:
For users in GDPR jurisdictions or with data privacy requirements, the difference between "OpenCode hosts it" and "OpenCode proxies to Alibaba/Moonshot" is significant. The zero-retention promise is reassuring, but if data flows through third-party APIs before OpenCode receives it, that's a different privacy profile than what the docs currently imply.
Happy to discuss this further. Making this explicit in the docs would build a lot of trust with privacy-conscious users.
Question
Hey,
First off, love what you're building with OpenCode Go — the curation angle and pricing make a lot of sense for reliable model access.
I have some questions about the Go plan documentation that I think need clarification:
The infrastructure claim:
Your docs state that Go models are "hosted in the US, EU, and Singapore for stable global access." However, when I tested the API with Qwen3.5 Plus (which is on your Go model list), I received this error:
This error coming directly from "provider (Alibaba)" suggests that Go is actually proxying requests to Alibaba's DashScope infrastructure, not hosting them on OpenCode-controlled servers.
Looking at your codebase (specifically the AI SDK packages referenced in the endpoint table), models like Qwen use
@ai-sdk/alibaba, Kimi uses Moonshot's infrastructure, etc., which further suggests third-party proxying rather than self-hosting.What I need clarified:
Why this matters:
For users in GDPR jurisdictions or with data privacy requirements, the difference between "OpenCode hosts it" and "OpenCode proxies to Alibaba/Moonshot" is significant. The zero-retention promise is reassuring, but if data flows through third-party APIs before OpenCode receives it, that's a different privacy profile than what the docs currently imply.
Happy to discuss this further. Making this explicit in the docs would build a lot of trust with privacy-conscious users.