Here’s the bottom line up front. Terry had been going back and forth for a few days about adding Kimi K3 as a team bot — then he saw the announcement on X and opened the app, only to find new subscriptions were already sold out. The same week, Alibaba announced Qwen 3.8. The preview is usable right now, but the open-weight release itself has no confirmed weights, benchmarks, or license. And the model our team actually runs locally every day is neither of these. This piece sorts out what’s actually confirmed from what’s still vendor claim in this week’s noise around Chinese open-weight AI.
🚀 What Happened This Week — Kimi K3 Launches, Then New Sign-Ups Freeze
Moonshot AI’s Kimi K3 launched on July 16, 2026. The official spec: 2.8 trillion parameters, natively multimodal, a 1-million-token context window. It’s a Mixture-of-Experts (MoE) architecture released as open weights — downloadable, runnable, modifiable.
The trouble started about 48 hours after launch. Moonshot paused new subscriptions. The official statement: “Over the past 48 hours, demand has pushed close to the limits of our current capacity. To protect the experience of existing subscribers, we’re temporarily pausing new subscriptions.” Existing subscribers are unaffected, and Moonshot says it plans to scale infrastructure and reopen in controlled batches — but gave no reopen date.
Community reaction was largely favorable. A comparison spread on X along the lines of “Moonshot gave up revenue, Anthropic cut usage back in April — that difference says it all.” Worth noting: that’s one popular framing, not something this piece independently verified — what Anthropic actually did in April remains unconfirmed here.
📊 Where Does K3 Actually Stand — Frontier-Adjacent, Not Top-Tier
The accurate framing isn’t “beats the frontier” — it’s “just below it.” Per Simon Willison’s hands-on review, K3 beats Claude Opus 4.8 and GPT-5.5 on most tasks, but loses to Claude Fable 5 and GPT-5.6 Sol. Forbes confirms the same ranking — trailing Fable 5 and GPT-5.6 Sol, but “frontier-level,” competitive on coding and agentic work, and clearly ahead of Opus 4.8.
Specific Elo or GDPval scores remain unverified — they only turn up in search snippets, with no fetchable page to confirm them. The qualitative ranking is corroborated by three independent sources; the exact numbers are not.
Pricing jumped sharply. K3’s API runs $3 per million input tokens ($0.30 on a cache hit) and $15 per million output tokens — the same tier as Claude Sonnet. That’s a steep climb from the previous version, K2.6, at $0.95/$4. The reflexive “cheap Chinese model” image no longer holds at the flagship tier. Open weights are promised for July 27 — if that happens, it lets you bypass the API pricing entirely by self-hosting.
🌀 Qwen 3.8 — You Can Try the Preview, But the Verdict Isn’t In
Alibaba announced Qwen 3.8 on July 19. It claims 2.4 trillion parameters and calls itself “one of the most powerful models available, second only to Fable 5.” The Max-Preview version is genuinely usable right now — it’s already live on Alibaba’s Token Plan and Qoder platforms. But that’s an API/cloud preview, not an open-weight release.
What’s actually unconfirmed is the open-weight side. No Hugging Face model card, no release date, no independent benchmark, no license — none of it exists yet. Qwen 3.5/3.6 shipped under Apache 2.0, but 3.7-Max switched to a closed, API-only model, so a return to open weights with 3.8 is a promise, not an established fact. The “second only to Fable 5” line is Alibaba’s own evaluation, and multiple outlets have explicitly flagged it as vendor positioning.
Reception of the preview you actually can try is mixed so far. With no independent benchmark yet, it’s too early to say anything definitive, but some hands-on users have reported that the live Qwen 3.8 Max underperforms Kimi K3 (single source, low-to-medium confidence — not independently cross-verified).
Terry’s honest read on this: he’s watching from the sidelines for now. He’s hoping for an open-weight release he can actually run locally, but if he had to pick something today, he’d rather try Kimi first — at least K3 has a real, shipped artifact with more accumulated evaluation behind it.
🖥️ The Self-Hosting Reality — Frontier Tier Doesn’t Fit Our Box
We do run models locally ourselves — Qwen 3.6-27B or Gemma4-26B, depending on the task. But to answer the honest question — “it’s open weight, can’t we just run it ourselves?” — most flagship models don’t fit on a single box. Here’s what the actual VRAM requirements look like.
| Model | Hardware needed |
|---|---|
| Kimi K3 (2.8T), DeepSeek V4-Pro (~1.6T), Kimi K2.x (1T) | ~8x H100/H200-class multi-node |
| Qwen3-235B (MoE, 4-bit) | ~140GB — just over a single 128GB box |
| Qwen 3.6-27B, Qwen3 32B, Gemma4 31B, dense 72B (Q4) | Fits a single box (17-46GB) |
We confirmed directly with free -h that our own DGX Spark has 121GiB actually usable. By that number, our box lands squarely in the “mid-tier” band — Qwen 27B-72B-class dense models and Gemma4 run comfortably, but a 2.8-trillion-parameter K3 or a 1.6-trillion-parameter DeepSeek V4-Pro were never in our hardware’s weight class to begin with. Open weights being available doesn’t automatically mean “we can run it” — we confirmed that on our own box.
💰 So What Does It Actually Cost — Why Structure Matters More Than a Single Number
Our own infrastructure’s “cost per token” is hard to state as a single precise figure — doing so would misrepresent the actual structure. A DGX Spark is a $4,699 one-time purchase with a modest ~35W under load. Once you’ve bought it, the marginal cost of an additional token is effectively zero. An API, by contrast, is metered — cost scales with usage. This isn’t a “how many cents per token” comparison problem; it’s the difference between a sunk-cost structure and a pay-as-you-go one.
Across the Chinese open-weight model family as a whole, one comparison puts pricing at roughly 10 to 30 times cheaper than Western frontier models (DeepSeek Flash ~$0.14-0.55/M input, Qwen Max ~$0.80-1.25, Kimi K2 ~$0.60-0.95, GLM flagship ~$1.00-1.40). But that “cheap Chinese model” narrative breaks precisely at K3 — its flagship pricing moved to Sonnet-tier. So “cheap” still holds at the mid-tier and for older flagships, but the gap is narrowing at the very top. The real cost lever now isn’t API pricing — it’s whether you can self-host the open weights, which requires an 8-GPU-class node to even be physically possible.
💬 Community Reaction
Reaction to the Kimi sellout was largely favorable. There was some cynicism about “selling out on purpose,” but the dominant framing was that Moonshot protected existing users even at the cost of new revenue. r/LocalLLaMA’s reaction to the Qwen 3.8 announcement was split — relief (“glad it’s going open-weight again”) and anxiety (“what we actually need is the 27B tier, are they chasing the stars again?”) coexisted in the same thread across 478-plus comments.
So what do people actually default to right now? Locally, the Qwen 3.5/3.6 family (27B, 35B-A3B class) is still the practical standard. Among Chinese frontier models usable via API, it’s K3 if you’re already subscribed, and a waitlist if you’re not. And there’s a firm consensus in the community that flagships in the 1.6-to-2.8-trillion-parameter range were never in an individual’s local-hosting weight class to begin with.
✅ Conclusion — Three Honest Takeaways
2. Qwen 3.8 — the Max-Preview is usable now, but reception is still mixed, and the open-weight release itself has specs, benchmarks, and license all still in claimed-not-shipped territory. Until there’s a real, locally-runnable artifact, watching from the sidelines is the right call.
3. Our actual daily driver — Qwen 3.6-27B or Gemma4-26B locally, depending on the task (Gemma4 by default). Regardless of country of origin, the real flagships were never going to be a single box’s job.
⚠️ Easy-to-Miss Risks
- Benchmark-correlation skepticism — Willison’s core warning: topping a leaderboard, especially a single-benchmark “arena” win, no longer correlates reliably with overall model capability, and often misses agentic tool-calling performance. “Beats Claude/GPT” isn’t a settled fact until you’ve tested it yourself.
- “Announced” isn’t “shipped” — Qwen 3.8 is the exact case in point. K3’s promised July 27 open-weight release date is likewise a promise, not a confirmed deliverable.
- Data governance and provenance — for regulated data (EU/US public sector, healthcare, finance), using the API means routing data to a China-operated endpoint. Self-hosting prevents data egress, but doesn’t resolve training-data or model-provenance questions.
- License gotchas — “open weight” doesn’t mean “open source.” DeepSeek and GLM lean MIT-family, and Qwen’s open tiers ship Apache 2.0, both clean for commercial use — but Kimi K2 shipped under a “Modified MIT,” and K3’s license hadn’t been published as of this writing. Verify before any commercial use.
- Capacity risk is now a live variable — the fact that Moonshot froze new sign-ups within 48 hours of launch shows that even the vendor can’t guarantee frontier-tier serving capacity. Building a product on a Chinese frontier API means carrying exactly the supply risk that open weights were supposed to solve — assuming you have the hardware to run them yourself in the first place.
📚 References
- Moonshot AI official site — Kimi K3 specs
- Simon Willison — Kimi K3 hands-on review (2026-07-16)
- Forbes — Moonshot’s Kimi K3 launch coverage (2026-07-17)
- Hacker News — Kimi K3 new-subscription-freeze thread
- MLQ.ai — Qwen 3.8 announcement coverage
- r/LocalLLaMA — Qwen 3.8 community reaction megathread
- Kimi_Moonshot official X — new-subscription-freeze announcement