Moonshot AI launched Kimi K3 on July 16, 2026 — API, Kimi App, Kimi Work, and Kimi Code went live overnight with model ID kimi-k3. The weights themselves follow 11 days later: July 27 brings the full 2.8T checkpoint, technical report, Modified MIT license, and expected Day-0 vLLM/SGLang builds on Hugging Face.

That split — API first, weights second — is deliberate. Moonshot validated production inference, pricing, and cache economics before opening the largest downloadable model in history. For most teams, the API remains the correct path through July and beyond; self-hosting is a specialized play for data residency, fine-tuning, or extreme volume.

What you get on release day: complete model weights (not a distilled variant), inference configs for vLLM and SGLang, quantization-aware MXFP4/NVFP4 artifacts, and a technical report documenting KDA, AttnRes, and Stable LatentMoE. What you do not get: training data, full training codebase, or a standard unmodified MIT license.

Open weights means you can download, inspect, fine-tune, and deploy the trained parameters. Open source traditionally means full code, data, and license freedom to reproduce training from scratch. Kimi K3 is firmly in the first camp: Moonshot ships weights and a technical report under Modified MIT, not a reproducible open-source stack.

Practical impact: researchers and enterprises can fine-tune K3, run private inference, and audit weight behavior. They cannot retrain K3 from public artifacts alone or claim a standard MIT license without reading Moonshot's modifications — especially around commercial redistribution. The industry increasingly uses "open weights" precisely because frontier labs rarely open everything.

Why the architecture matters for self-hosting

KDA's 3:1 linear-to-full attention ratio is why million-token inference is even discussable — without it, KV-cache memory at 1M tokens would be prohibitive. AttnRes adds cross-depth selective retrieval (~25% training efficiency gain). Stable LatentMoE with Quantile Balancing removes brittle expert-routing heuristics that break at 896-expert scale.

Quantized release artifacts (MXFP4/NVFP4) are designed for Day-0 vLLM and SGLang deployment. Moonshot trained with quantization-aware methods so INT4/FP4 inference does not collapse quality the way post-hoc quantization sometimes does on other frontier models.

K3 is competitive — not dominant. Moonshot's own blog acknowledges shortcomings vs K2.6 on hallucination rate and vs Fable 5/Sol on polish and output variance. Below mixes Artificial Analysis aggregate scores with Moonshot self-reported task benchmarks (different harnesses per vendor).

Where K3 wins:

Where K3 loses:

The open/closed intelligence gap has narrowed to roughly 2–3 AA Index points at the frontier tier. K3's pitch is not "we beat Claude" — it is "we are within striking distance at one-third the price, with downloadable weights and 1M context."

K3 standard pricing aligns with Western quality-tier models ($3/$15) but ships a 5x larger context window than Sonnet-class APIs at no length surcharge. Cached input at $0.30/M (one-tenth standard) plus 90%+ cache hit rates in coding workflows makes effective input cost very low. AA single-task pricing at $0.94 sits 9.4% below Sol and 65.8% below Fable 5 — the near-frontier cost story in one number.

Six operational steps:

from openai import OpenAI

client = OpenAI(
    api_key="your_moonshot_api_key",
    base_url="https://api.moonshot.ai/v1"
)

response = client.chat.completions.create(
    model="kimi-k3",
    messages=[{"role": "user", "content": "Analyze this codebase for security issues..."}]
)

Self-deploy math: 4-bit quantized K3 weights land around ~1.4 TB. Production inference requires a 64+ accelerator supernode — not a MacBook, not a single RTX 4090. For scale reference, Kimi K2.7 Code INT4 sits near ~577 GB; K3 at 2.8T is a different infrastructure class entirely.

Three scenarios where self-hosting makes sense: (1) Data residency — workloads that cannot leave your VPC; (2) Fine-tuning — domain adapters on top of open weights; (3) High volume — sustained token throughput where capex beats opex. Everyone else should use the API through July 27 and likely after.

Industry context: The open/closed gap at the frontier is now 2–3 AA points, not 20. Geopolitics shapes the narrative — K3 launched on the eve of WAIC 2026, while Anthropic's Claude Fable 5 faced a brief US export-control takedown on July 1 (since restored) that pushed foreign developers toward alternatives. China's open-weights wave — GLM-5.2, DeepSeek V4 Pro, MiniMax, now Kimi K3 — is no longer "cheap copies" but a coordinated push at the frontier tier.

Moonshot's arc matters: after DeepSeek R1 shook the market, Kimi briefly fell to rank 7 on some leaderboards. The K2 → K2.5 → K3 sequence is a deliberate comeback — each generation adding context, MoE scale, and now the largest open weights drop in history. API revenue exceeds 70% of total; overseas paid users up 400%. This is not charity open weights; it is a commercial platform play with a downloadable moat.

Summary: July 27 is a landmark for open weights — not because K3 beats every closed model, but because it puts 2.8T near-frontier parameters in downloadable form at API prices that undercut Claude and GPT on cost-per-task. Validate on your workloads, read the Modified MIT license, and plan hardware honestly before self-hosting.

Lay out the alternatives: running Kimi Code agents on a personal Mac hits sleep and network interruptions on long-context jobs; waiting for July 27 self-hosting requires a 64+ card supernode most teams lack; relying on a single closed API misses K3's 1M flat-pricing advantage. For iOS CI/CD, persistent Kimi Code, and 24/7 AI agent production, KVMNODE dedicated Mac Mini M4 cloud rental is usually the better host: Apple Silicon unified memory, open sudo, flexible daily/weekly/monthly terms. See the pricing page, help center, or order directly.

Data as of: July 22, 2026 · Benchmarks include Moonshot AI self-reported figures · Sources: kimi.com/en/blog/kimi-k3, platform.kimi.ai, Artificial Analysis, VentureBeat, Northflank, r/LocalLLaMA, Hacker News