Home / Blog / K3 Open Weights
ENGINEERING_BLOG · 2026.07.22

Kimi K3 Open Weights:
Release Date, Benchmarks & How to Run It (2026)

Moonshot AI releases Kimi K3 full weights on July 27, 2026 under a Modified MIT license on Hugging Face, alongside a technical report. The model is a 2.8-trillion-parameter MoE with 1M-token context, native vision, and quantization-aware training (MXFP4/MXFP8). If you are an AI engineer or infrastructure lead deciding whether to invest in a 64+ accelerator cluster for self-hosting, this guide covers release timeline, architecture specs, benchmark wins and losses vs Claude Fable 5 and GPT-5.6 Sol, real API cost with caching, open weights vs open source, honest hardware requirements, industry impact, a July 27 launch checklist, citable data, and FAQ.

  • TL;DR: API went live July 16; downloadable weights land July 27 — do not conflate the two dates.
  • License: Modified MIT plus tech report. Commercial terms are final only when the Hugging Face LICENSE file publishes.
  • Self-host reality: ~1.4TB at 4-bit quantization, 64+ GPUs for production — not consumer hardware.

One week after API launch, self-deployment teams still sit in a "can test, cannot host" window. Common pain points before July 27:

  • Hardware cost misread: 2.8T parameters at 4-bit quantization need roughly 1.4TB storage and a 64+ accelerator super-node — far beyond typical enterprise budgets, impossible on a laptop.
  • Open vs closed gap shrinking: Artificial Analysis Intelligence Index v4.1 puts K3 at 57.1 (#3), only 2-3 points behind Claude Fable 5 (59.9) and GPT-5.6 Sol (58.9).
  • Benchmarks are not a clean sweep: K3 loses on DeepSWE (67.5 vs Sol 73.0), GDPval Elo, and Moonshot admits hallucination rates rose vs K2.6 — open weights does not mean universal superiority over closed models.
  • Framework uncertainty: vLLM needs Day-0 KDA and prefix caching support; Ollama/GGUF timelines remain community-dependent.
  • License and geopolitics: Modified MIT terms are not final until July 27; Anthropic briefly pulled Claude Fable 5 from China on July 1, a reminder to plan multi-vendor and data-residency fallbacks.

SECTION 01 What Is Kimi K3?

Kimi K3 is Moonshot AI's frontier MoE model — API-accessible since July 16 and becoming the largest downloadable open-weights release on record when weights drop July 27. For full KDA architecture analysis, see our Kimi K3 review.

Kimi K3 core specifications
Parameter Value
Total parameters 2.8 trillion (2.8T)
MoE config Stable LatentMoE: 896 experts, 16 active per token (1.8% sparsity)
Architecture stack KDA + AttnRes + Gated MLA
Training stability Quantile Balancing, Per-Head Muon optimizer, SiTU activation
Context window 1,048,576 tokens (1M)
Quantization design MXFP4 weights + MXFP8 activations (quantization-aware from training)
Vision Native multimodal (text, image, video input; text output)
Long-context decode KDA delivers up to 6.3× faster decode at 1M tokens; KV cache cut up to 75%
4-bit weight size ~1.4TB
Scaling efficiency ~2.5× vs Kimi K2

One-line positioning: Kimi K3 is the largest open-weights model by parameter count — 2.8T total, roughly 75% above DeepSeek V4 Pro (1.6T). It targets complex coding, long-document reasoning, and knowledge work at max effort by default.

SECTION 02 Kimi K3 Release Date: API Launch vs Open Weights

Many teams ask "Is K3 already open source?" The official timeline splits cloud API access from downloadable weights:

Kimi K3 launch timeline
Date Event What developers get
2026-07-16 K3 goes live API, Kimi App, Kimi Work, Kimi Code — cloud inference only, model ID kimi-k3
2026-07-17 WAIC Shanghai + Xinhua milestone Public architecture preview, benchmark updates, on-site demos
2026-07-27 Full weights release Hugging Face (Modified MIT) + technical report; first open weights above 2T

July 16 is when you can call the API. July 27 is when you can download weights, read the LICENSE, and plan private-cloud inference. Until then, offline inference, custom fine-tuning, and full data-residency control are not available.

SECTION 03 Kimi K3 Benchmarks vs Claude Fable 5 and GPT-5.6

Moonshot has been candid: K3 still trails Fable 5 and Sol on overall intelligence index, but the gap is now 2-3 points. Figures below are Moonshot self-reported (each vendor uses its own inference harness) — treat as directional until independent reproduction after July 27.

Artificial Analysis Intelligence Index and per-task cost
Model AA Index v4.1 Rank AA per-task cost
Claude Fable 5 59.9 #1 Baseline
GPT-5.6 Sol 58.9 #2
Kimi K3 57.1 #3 $0.94 (65.8% cheaper than Fable 5)

Where Kimi K3 wins

Kimi K3 benchmark wins
Benchmark Kimi K3 Notes
Frontend Code Arena #1 Frontend coding scenarios
SWE Marathon 42.0 Sustained multi-hour coding — first place
BrowseComp 91.2 Web browsing Agent tasks
Terminal Bench 2.1 88.3 Terminal and toolchain-heavy Agents
Program Bench 77.8 General programming ability
Automation Bench 30.8 Workflow automation
SpreadsheetBench 2 Leads Spreadsheet reasoning and manipulation
FrontierSWE 81.2 Competitive, though Fable 5 leads at 86.6

Where Kimi K3 loses

Kimi K3 benchmark losses and caveats
Benchmark Kimi K3 Leader Notes
DeepSWE 67.5 Sol 73.0 / Fable 5 70.0 Deep repo-level SWE tasks
GDPval Elo Trails Fable 5 / Sol General knowledge work composite
Hallucination rate (vs K2.6) Rose K2.6 baseline Moonshot internal eval — honest admission

Moonshot's framing is straightforward: K3 is not a universal #1, but it leads on sustained coding, frontend work, and document-heavy Agent flows. Once weights release July 27, the community can independently reproduce these numbers — the most important validation milestone on the calendar.

SECTION 04 Kimi K3 API Pricing (Real Cost With Caching)

Kimi K3 API pricing (per 1M tokens)
Line item Price Notes
Input $3.00 Matches Claude Sonnet 5 standard rate
Output $15.00 Flat pricing — no length surcharge at 1M context
Cache-hit input $0.30 One-tenth standard input; coding Agents can exceed 90% hit rate
Kimi K3 vs frontier closed models — pricing comparison
Model Input Output Cache hit Context
Kimi K3 $3.00 $15.00 $0.30 1M
Claude Fable 5 $3.00 $15.00 200K
GPT-5.6 Sol $5.00 $30.00 400K
DeepSeek V4 Pro $1.74 $3.48 $0.145 128K

Under Artificial Analysis per-task cost modeling, K3 runs about $0.94 per task65.8% cheaper than Claude Fable 5 while trailing by only 2-3 index points. With 90%+ cache hit rates in coding Agent scenarios, effective input cost drops to $0.30/M. Closed-model premium is shifting from a universal intelligence gap toward SLA, compliance, and a handful of top benchmarks — not blanket capability superiority.

SECTION 05 Is Kimi K3 Open Source? (Open Weights vs Open Source)

Headlines often say "open source." The accurate term for Kimi K3 is open weights. The distinction matters for compliance, fine-tuning rights, and reproducibility.

Open weights vs open source — what Kimi K3 actually provides
Dimension Open weights (K3) Full open source
Model weights Yes — Hugging Face download July 27 Yes
Training data Not released Typically published or documented
Training code Not fully released Full pipeline available
License Modified MIT — extra terms possible Standard permissive license (MIT, Apache 2.0)
What you can do Run, fine-tune, deploy privately Reproduce training end-to-end

Modified MIT may add conditions beyond standard MIT — scale limits, derivative model attribution, or restrictions on competing AI services. Read the LICENSE file in the Hugging Face repo on July 27 before commercial deployment or publishing fine-tuned variants. Open weights gives you the strongest downloadable base model in 2026; it does not mean you can rebuild Kimi K3 from scratch.

SECTION 06 Can You Run Kimi K3 Locally? Hardware Requirements

Be honest about scale: Kimi K3 is not runnable on a laptop, Mac Mini, or typical workstation. Moonshot targets production inference on a 64+ accelerator super-node (NVIDIA H100 class). At 4-bit quantization, weights alone consume roughly 1.4TB. For reference, Kimi K2.7 Code at INT4 is about 577GB — K3 is roughly 2.4× larger.

Self-host vs API — decision matrix
Scenario Recommendation Why
Production use before July 27 K3 API Weights unavailable; API is ready today
Data residency / compliance Self-host after July 27 Weights must stay on-premises or in a private region
Domain fine-tuning at scale Self-host after July 27 Full weights + tech report required for custom training
High-volume inference (cost at scale) Self-host after July 27 API cache helps, but petabyte-scale traffic may justify owned clusters
Cost-sensitive, 128K context enough DeepSeek V4 Pro API Output at $3.48/M — far below K3
Consumer hardware Not feasible 1.4TB / 64+ GPUs — datacenter class only

Three scenarios justify self-hosting after July 27: data residency, fine-tuning, and high-volume inference. Everyone else should stay on the API until cluster economics pencil out.

On release day, infrastructure teams can follow this seven-step checklist:

  1. Verify Hugging Face repo and license: Open the official Moonshot HF repo and read every line of Modified MIT before commercial use or derivative publication.
  2. Download the technical report: Cross-check KDA, Stable LatentMoE, and Gated MLA inference configs against compatible vLLM versions.
  3. Size hardware and storage: Plan for ~1.4TB at 4-bit and a 64+ accelerator super-node; confirm bandwidth for weight sync.
  4. Deploy vLLM inference cluster: Install a build with KDA and prefix caching support; configure MXFP4 weight loading and KV cache policy.
  5. Set up API gateway and monitoring: Front the cluster with an OpenAI-compatible gateway; track latency, throughput, and GPU memory.
  6. Run benchmark regression tests: Compare self-hosted output against API on SWE Marathon and Terminal Bench internal suites.
  7. Plan fine-tuning pipeline (optional): Reserve extra GPU time and confirm Modified MIT obligations for derivative models with legal review.
vllm_serve.sh
vllm serve moonshotai/Kimi-K3 \
  --tensor-parallel-size 8 \
  --max-model-len 1048576 \
  --enable-prefix-caching \
  --quantization mxfp4

Exact model ID, parallelism, and quantization flags will be in the July 27 tech report and vLLM release notes. Day-0 support is expected in vLLM, SGLang, and transformers, with MXFP4/NVFP4 quantized variants on Hugging Face. Ollama/GGUF conversions will follow the community timeline — still not a laptop workload even when quantized.

SECTION 07 Why the July 27 Weights Release Matters

Mid-2026, the intelligence gap between open weights and closed frontier models has collapsed to 2-3 index points. China's model wave is accelerating on a clear timeline:

  • GLM-5.2 and DeepSeek V4 Pro set new open-model baselines in general reasoning and coding.
  • Moonshot K2 → K2.5 → K3 reclaims the "world's largest open-weights model" title at 2.8T.
  • Geopolitical signal: Anthropic briefly removed Claude Fable 5 from China on July 1 — multi-vendor backup and on-prem weights are no longer optional for regulated teams.
  • Closed-model premium redefined: When K3 trails by 2-3 points but costs 65.8% less per task, premium pricing survives on FrontierSWE, DeepSWE, enterprise SLA, and compliance — not a blanket capability moat.

July 27 makes K3 the first downloadable model above 2 trillion parameters, a new fine-tuning baseline for the open community, and a forcing function for independent benchmark reproduction. For most developers and SMB teams, API access with $0.30/M cache hits remains the pragmatic path after weights land.

  • Parameter scale: 2.8T total, 896-expert Stable LatentMoE (16 active) — largest downloadable open weights on record.
  • Storage floor: ~1.4TB at 4-bit; production inference needs 64+ accelerators.
  • Architecture efficiency: KDA cuts KV cache 75%, 6.3× faster decode at 1M tokens; ~2.5× scaling efficiency vs Kimi K2.
  • License: Modified MIT — final terms in the July 27 Hugging Face LICENSE file.
  • Framework support: vLLM Day-0 KDA + prefix caching; SGLang and transformers follow.
  • Composite ranking: AA Index v4.1 score 57.1 (#3); per-task cost $0.94, 65.8% below Fable 5.

Re-open these sources after upstream updates to verify specs and benchmark claims:

Moonshot AI official blog — Kimi K3 launch

Kimi API Platform official documentation

Artificial Analysis — Intelligence Index v4.1 model rankings

VentureBeat — Moonshot AI Kimi K3 open-weights coverage

Kimi K3 open weights are a model-selection upgrade for API users, but teams integrating Kimi Code Agents, macOS CI/CD, and 7×24 automated test pipelines still face three practical gaps: (1) weights are unavailable until July 27, stretching private-cloud procurement cycles; (2) macOS CI on VMs hits Metal and Core ML compatibility overhead; (3) a local Mac goes dark when it sleeps, breaking always-on Agent pipelines. For production environments that need zero-overhead native Apple compute, stable iOS CI/CD, and always-on AI Agent automation, MACNOX cloud physical Mac nodes are usually the better fit: 100% genuine Apple hardware, full root access, no hypervisor tax, flexible daily/weekly/monthly billing. See our Kimi K3 architecture review, DeepSeek V4 GA pricing and benchmarks, and Mac Mini M4 rent vs buy TCO analysis, or visit the pricing page.

SECTION 08 FAQ

What will Moonshot release on July 27, 2026?

Full model weights on Hugging Face under a Modified MIT license, plus a technical report. The community expects Day-0 vLLM support for KDA and prefix caching, with Ollama/GGUF quantized variants following later.

How is Modified MIT different from standard MIT?

Modified MIT may add extra terms on top of standard MIT, such as scale limits or attribution requirements for derivative models. Read the LICENSE file in the Hugging Face repo on July 27 before any commercial use.

Can I run Kimi K3 on a laptop or consumer hardware?

No. 4-bit quantized weights are roughly 1.4TB. Production inference requires a 64+ accelerator super-node. This is not a laptop or Mac Mini workload.

Does Kimi K3 hallucinate more than K2.6?

Moonshot internal evaluations show K3 hallucination rates rose versus K2.6 in some scenarios, a known trade-off when scaling parameters and context. Run your own A/B tests on critical workloads.

Should I self-host Kimi K3 or use the API?

Data residency, high-volume fine-tuning, or compliance needs favor self-hosting after July 27. Most teams should use the API first ($3/$15 per 1M tokens, $0.30/M cache hits). Self-hosting requires sizing a 64+ accelerator cluster and 1.4TB storage.

When will vLLM support Kimi K3 KDA architecture?

Moonshot says vLLM will support KDA and prefix caching on release day. Exact version numbers and install commands will be in the official tech report and vLLM release notes.

Is Kimi K3 open source or open weights?

Kimi K3 is an open-weights release under Modified MIT, not a full open-source stack. You get downloadable weights and a tech report, but training data, full training code, and standard MIT terms are not guaranteed. Open weights means you can run and fine-tune; open source implies broader reproducibility.

Do closed models still command a premium after K3 weights drop?

On Artificial Analysis Intelligence Index v4.1, K3 (57.1) still trails Claude Fable 5 (59.9) and GPT-5.6 Sol (58.9) by 2-3 points, but per-task cost is 65.8% lower than Fable 5. Closed-model premium now shows up mainly in FrontierSWE, DeepSWE, and enterprise SLA, not a universal capability gap.