Is Kimi K3 Open Source? Inside Moonshot AI's 2.8-Trillion-Parameter Model

Background reading: our July 17 K3 review, pre-release anticipation guide, and distillation controversy roundup. Cross-vendor context: GPT-5.6 Sol review, Claude Fable 5 alternatives, OpenRouter July rankings.

01 · TL;DR

• What landed July 27: Full 2.8T weights, technical report, and open-source infra stack (MoonEP + AgentEnv; FlashKDA had shipped earlier). The download hit #1 on Hugging Face trending within 30 minutes.
• Terminology matters: Moonshot never says "open source." Under OSI standards, K3 is open weight—weights and inference tooling are public; training data and full training code are not.
• Capability: SWE-bench Verified 93.4% (Vals AI, independent); Artificial Analysis Intelligence Index ~57 (#3 overall, #1 open weight). Leads Frontend Code Arena; trails Opus 5 / GPT-5.6 Sol / Fable 5 on composite coding benchmarks.
• Commercial reality: Custom license with two gates—$20M trailing-12-month MaaS revenue and 100M MAU / $20M monthly revenue attribution. Fine for startups; red flag if you plan to compete with Moonshot's API at scale.
• Practical path for Mac developers: API at $3/$15 with 90%+ cache hits on coding workloads beats trying to host 1.56TB on a MacBook. Validate via Kimi Code on an isolated rental node first.

02 · Three Decision Pitfalls After the Weight Drop

1. Calling it "open source" in production docs: r/LocalLLaMA will correct you. K3 is open weight with a custom license—not OSI open source. Legal and procurement teams need the distinction before signing vendor assessments.
2. Treating the Hugging Face download as a local-dev plan: At ~1.56TB, even downloading K3 on a Mac is a multi-day bandwidth exercise with no inference payoff. Production needs 64+ GPUs with expert and tensor parallelism—not Apple Silicon unified memory tricks.
3. Ignoring license gates because "it's free": Most teams sail through untouched. But if your roadmap includes reselling K3 inference or scaling past 100M MAU, the custom license has teeth that K2's Modified MIT framing did not.

03 · Release Timeline: API to Weights in 11 Days

Eleven days from API launch to full weight release is unusually fast for a 2.8T model—and it landed squarely in the middle of a geopolitical firestorm over training-data provenance.

04 · Open Weight vs Open Source: What Moonshot Actually Shipped

The OSI definition of open source requires public training data, public training code, and a reproducible pipeline—not just downloadable weights. Kimi K3 delivers:

• Public: Trained weight files (~1.56TB), technical report, MoonEP, FlashKDA, AgentEnv, and inference-oriented tooling
• Not public: Training datasets, full training codebase, and end-to-end reproduction instructions

Moonshot's own materials consistently say "open weight" and never "open source." That is not modesty—it is a legally meaningful distinction. You can download, fine-tune, and commercially deploy K3 within license bounds, but you cannot rebuild it from scratch or audit its training provenance the way a fully open pipeline would allow.

Also note: the K2 era's "Modified MIT" branding is gone. K3 ships under a fully custom license with commercial thresholds detailed in the next licensing section.

05 · Kimi K3 Spec Sheet (Post-Release)

Hard data point #1: K3 is the first complete 3T-class model ever released as downloadable open weights—and the 1.56TB footprint alone disqualifies casual local hosting.

06 · Architecture: KDA, AttnRes, and Per-Head Muon

Moonshot did not simply scale K2—it rebuilt three foundational components: attention, residual connections, and the optimizer.

6.1 Kimi Delta Attention (KDA)

Standard Gated DeltaNet applies a single scalar forgetting gate across an entire memory state. KDA upgrades to channel-wise gating: each feature dimension gets its own decay rate, so the model can retain some features indefinitely while aggressively forgetting others. Implemented as a chunkwise Diagonal-Plus-Low-Rank (DPLR) recurrence, KDA stays linear in sequence length and hardware-efficient. K3 interleaves KDA layers with fewer full global-attention (Gated MLA) layers—the hybrid that makes 1M context practical without KV cache explosion.

6.2 Attention Residuals (AttnRes)

Standard residual connections accumulate every layer's output uniformly, diluting early-layer signal at depth. AttnRes replaces uniform accumulation with selective, input-dependent aggregation across all preceding layers. Overhead is minimal—one RMSNorm and one pseudo-query vector per layer. Moonshot reports ~25% training efficiency gain for under 2% added compute. Pseudo-query vectors initialize to zero, so early training behaves like uniform averaging and avoids instability.

6.3 Per-Head Muon

Muon is a widely adopted large-scale optimizer. K3 extends it to operate per attention head rather than applying one global optimization strategy. Each head gets a more adaptive convergence path. This is invisible at API call time but helps explain why ~104B active parameters punch near frontier closed-model quality.

6.4 Stable LatentMoE

896 experts with 16 active per token demands careful load balancing. Moonshot uses Quantile Balancing for expert routing and pairs it with MoonEP (below) to prove a mathematical upper bound on redundant experts per compute rank—guaranteeing feasible balanced routing even under load skew.

07 · MoonEP, FlashKDA, and AgentEnv: The Infra Stack

The July 27 release was not weights-only. Moonshot open-sourced the infrastructure that made training K3 tractable—a major reason the drop earned strong developer-community reception.

Hard data point #2: FlashKDA's 1.72×–2.22× H20 prefill speedup is the kind of kernel-level detail that separates "we released weights" from "we released an engineering stack."

08 · Benchmarks: SWE-bench 93.4% and Where K3 Sits

Vendor-reported numbers vary by harness. Below prioritizes independent third-party data where available.

8.1 SWE-bench Verified (Vals AI, July 2026)

K3 trails the top three closed models by 1.6–3.6 points but leads the open-weight cohort by a wide margin on this independent benchmark.

8.2 Artificial Analysis Intelligence Index (max reasoning)

• Claude Fable 5 (max + fallback): 60
• GPT-5.6 Sol (max): 59
• Kimi K3 (max): ~57 — #3 overall, #1 open weight
• GLM-5.2 (max): 51 (previous open-weight leader)
• DeepSeek V4 Pro (max): 44

Per-task cost on the Intelligence Index: K3 ~$0.95 vs Fable 5 ~$2.40 (~60% cheaper) but vs GLM-5.2 ~$0.47 (more expensive). K3 is the capability ceiling of open weights, not the value pick. It also ranks #1 on Arena.ai's Frontend Code Arena.

Hard data point #3: 93.4% SWE-bench Verified + ~57 Intelligence Index + #1 Frontend Code Arena = credible frontier-tier coding, with known gaps on long-horizon judgment (GDPval) and dialogue stability versus Fable 5.

09 · Custom License: Two Commercial Gates

The K3 license is the most controversial part of the release for enterprise legal teams. Two thresholds did not exist in the K2 family:

1. Model-as-a-Service revenue gate: If you or your affiliates operate a MaaS business built on K3 and that business exceeds $20 million in aggregate revenue over any trailing 12 months, you must negotiate a separate commercial agreement with Moonshot before continuing.
2. Attribution gate: If your product exceeds 100 million monthly active users or $20 million in monthly revenue, you must prominently display "Kimi K3" in the product UI.

For startups, indie developers, and most mid-size companies, neither gate triggers in practice. The first gate matters only if your business model is reselling K3 inference at scale in direct competition with Moonshot's own API—a scenario our July 25 distillation roundup shows regulators are already watching closely.

10 · API Pricing and Effective Cost After Caching

Moonshot exposes an OpenAI-compatible API at https://api.moonshot.ai/v1 with model ID kimi-k3. Mooncake's disaggregated prefill/decode architecture reportedly holds cache hit rates above 90% on typical coding workloads—so real bills cluster near $0.30/M input, not the $3.00 headline. Seven OpenRouter providers already host K3, mostly at official pricing. See our July OpenRouter rankings for traffic context.

11 · Can You Self-Host? The 64-GPU Floor

Short answer: not on a Mac, not on a single consumer GPU, and not without serious datacenter budget.

• Download size: ~1.56TB on Hugging Face (full weight shards)
• Official recommendation: Supernode with 64 or more accelerators, expert parallelism + tensor parallelism
• Reference scale: Prior-gen K2.7 Code needed ~577GB at INT4; K3 is 2.8× that parameter scale

For individual developers and most companies, the correct path is API access or OpenRouter routing—not downloading 1.56TB to a Mac Studio hoping Ollama will save the day. Self-hosting only makes sense when data residency, fine-tuning on proprietary data, or call volume at scale justifies owned hardware.

12 · US-China AI Dispute: Why the Timing Matters

K3's open-weight drop did not happen in a vacuum. It landed during WAIC 2026 and days after the US-China "model distillation" dispute escalated:

• July 22–23: White House science adviser Michael Kratsios accused Moonshot of "large-scale, covert industrial distillation" against Anthropic's Fable model to train K3. Treasury Secretary Scott Bessent floated sanctions and Entity List designation.
• July 27: Moonshot releases full weights, technical report, and infra stack—arguably the strongest possible transparency signal short of publishing training data.
• July 28: China's Ministry of Commerce publicly pushes back, accusing Washington of "AI hegemonism" and threatening countermeasures.
• July 30 (preview): Alibaba—an investor in Moonshot—unveils Qwen3.8-Max-Preview (2.4T), widely read as a direct competitive response, pushing China's open-weight race into the "3T club."

The geopolitical backdrop reframes a technical release as a sovereignty statement: regulators can restrict closed API access (as the June Fable 5 export ban showed), but weights already on Hugging Face cannot be un-published. For background on that precedent, see our Fable 5 export ban guide.

13 · Five Steps After the July 27 Release

1. Read the LICENSE file on Hugging Face before integrating K3 into any commercial product—confirm MaaS and attribution gates against your revenue projections
2. Register at platform.kimi.ai and run baseline tasks via OpenAI-compatible SDK with kimi-k3 (long document / bug fix / multi-file refactor, one each)
3. Enable context caching and log hit rates plus real $/task versus Claude Fable 5 and GPT-5.6 Sol on identical repo tasks
4. Evaluate MoonEP / FlashKDA only if you operate training infrastructure—API users can skip this; self-hosters should check vLLM/SGLang launch notes bundled with the weight release
5. Trial Kimi Code on an isolated Mac (not your daily driver)—validate million-token agent workflows without polluting primary Keychain or shell profiles; cross-read architecture details in our July 17 deep review

14 · Frequently Asked Questions

Q: Is Kimi K3 open source?
A: No, not by OSI standards. It is open weight: trained weights, technical report, and infra tools are public; training data and full training code are not. Moonshot uses "open weight" in its own materials, never "open source."

Q: Can I use Kimi K3 commercially?
A: Yes for the vast majority of use cases. Restrictions apply if you run MaaS on K3 exceeding $20M trailing-12-month revenue (separate agreement required), or if your product exceeds 100M MAU or $20M monthly revenue (must display "Kimi K3").

Q: How much hardware do I need to self-host?
A: Moonshot recommends 64+ accelerator supernodes. The Hugging Face download is ~1.56TB. Consumer Macs cannot run production inference.

Q: What is K3's SWE-bench score?
A: 93.4% on SWE-bench Verified per Vals AI (July 2026)—behind Opus 5 (97%), GPT-5.6 Sol (96.2%), and Fable 5 (95%), but the top open-weight result in that cohort.

Q: What are MoonEP, FlashKDA, and AgentEnv?
A: MoonEP handles MoE communication at scale; FlashKDA accelerates KDA kernels (1.72×–2.22× H20 prefill); AgentEnv is a Firecracker microVM sandbox for agentic RL training co-built with KVCache.ai.

Q: How much does the API cost?
A: $3/$15 per 1M tokens; cached input $0.30/M. Coding workloads report 90%+ cache hits, making effective spend far below list price.

Q: How does K3 differ from K2?
A: ~3× parameter scale vs K2.5, new AttnRes and Per-Head Muon architecture, 1M context, native vision, and new commercial license gates absent from the K2 family.

15 · Rent an Isolated Mac: API Acceptance Without the 1.56TB Download

The highest-value move after July 27 is not starting a multi-day Hugging Face download on your MacBook—it is validating the Kimi K3 API workflow on an isolated Apple Silicon node. Moonshot keys on a rental machine instead of your primary Keychain, million-token Kimi Code experiments that do not pollute local caches, and same-repo comparisons against Claude/GPT in a burn-after-reading environment.

Windows and Linux users can partially trial via kimi.com Web or OpenRouter, but cannot fully exercise macOS-native Kimi Code toolchains. Isolated Mac trials reduce key-leak and long-context experiment risk; rental avoids buying hardware just to test a model you will likely call via API anyway. Billing details are on our Mac mini M4 pricing guide.

16 · Sources

• Official: kimi.com/en/blog/kimi-k3 (technical blog), platform.kimi.ai (API docs and pricing)
• Hugging Face: Moonshot AI organization (K3 weight repository and LICENSE)
• GitHub: moonshotai/FlashKDA, MoonEP, AgentEnv repositories
• Independent benchmarks: Vals AI SWE-bench Verified, Artificial Analysis Intelligence Index
• Reporting: VentureBeat, Simon Willison's blog, Hacker News, SCMP
• Community: r/LocalLLaMA (open-weight definition debates), Arena.ai Frontend Code Arena

Data compiled July 28, 2026 (day after weight release). Confirm Hugging Face direct links and LICENSE text against the live repository.