What happened?

On 28 July 2026, Pipe Network published an MLX port of Moonshot’s Kimi K3 and said the quiet part out loud: full K3 is 2.8T parameters / ~1.6TB on disk — “impossible” on Apple Silicon in naive form — until you change the load path and the expert set.

Two moves:

  1. Streaming converter — walk the model one layer at a time so mlx_lm never has to materialize the whole checkpoint in RAM at convert time.
  2. REAP pruning — score all 896 experts against a calibration corpus and keep the experts your workload actually needs. That is what they claim brings the footprint to ~350GB, inside a high-end Mac Studio unified-memory envelope.

Quants are public (REAP73, REAP80, REAP73 specialized for Chinese + code). Recipe, converter, calibration, and pruning scripts are open on GitHub.

Why this is interesting

  • The laptop/desktop boundary just moved — for real hardware, not cosplay. Our K3 piece said open frontier is leverage for racks and hosts, not MacBooks. Pipe’s work does not put 1.6TB K3 on a MacBook Air. It puts a pruned MoE on a Mac Studio-class box. Same story, sharper knife: unified memory + MLX is a legitimate inference tier if you accept expert selection.
  • Pruning is the product, not the port. Streaming conversion is plumbing. REAP is the bet: which of 896 experts matter for your corpus? A “general” REAP73 and a “zh+code” REAP73 are different products wearing the same base name. Operators should treat expert masks like deployment configs, not free lunch.
  • This is the Mac answer to “Ollama vs vLLM.” vLLM still wants NVIDIA and multi-tenant GPU serving. On Apple Silicon the production path is MLX-native (or Ollama sitting on similar metal). Pipe is doing the unglamorous work of making a frontier MoE loadable on that metal — the same class of decision as pinning one warm model on a studio box for agents.
  • 350GB is still not “consumer.” A Mac Studio that can hold that class of resident weights is capital equipment. The win is sovereign / air-gapped / low-latency desk inference for labs and serious indie ops — not replacing a $20 API key for every Swiss KMU overnight.
  • Quality is a research question until you eval. Dropping experts changes behavior. REAP80 vs REAP73 vs zh+code will disagree on long-horizon coding, multilingual chat, and tool loops. Run your harness (Terminal Bench–style jobs, your agent tools, your language mix) before you trust marketing screenshots.
  • Pairs with K3’s own over-help problem. A huge MoE on your desk still needs stop conditions, authz, and audit if it drives real work. Local does not mean unsupervised. It means the failure domain is yours.
  • Open recipe compounds. Converter + calibration scripts mean other labs can REAP different workloads (staffing ops DE/PL/RO, Treuhand German, code-only). The interesting fork is expert policy, not another chatbot UI.

What it is not

Not proof that full unpruned K3 runs casually on Apple Silicon. Not a free ElevenLabs-killer or a reason to abandon cloud APIs tomorrow. Not a substitute for independent quality boards on the pruned checkpoints. Not “open weights” magic that erases license and commercial terms on the base model.

Bottom line

Pipe Network turned K3’s “64+ GPU supernode” aura into a sharper claim: with streaming convert + expert REAP, a Mac Studio can host a serious slice of a 2.8T MoE under MLX. That is a real shift in who can self-host a frontier-adjacent worker — still capital-heavy, still eval-gated, still judgment-bound.

For builders on Apple metal: stop arguing Ollama vs vLLM as ideology. MLX + one pinned workload-shaped quant + keep-warm + healthchecks is the production shape. For the industry: open frontier now includes desktop-rack hybrids — not just neoclouds and API meters.