The one-line pick: Take Laguna S 2.1 if you want an open-weight coding agent you can genuinely self-host on hardware you can buy today; take Kimi K3 if you want the more capable open frontier and you'll rent it through a hosted API instead of running its weights yourself. They both say "open weights," but they are not the same purchase.

Two open-weight coding models landed in the same week of July 2026, and a founder skimming the headlines could be forgiven for thinking they're rivals for the same slot. They aren't. Kimi K3 and poolside's Laguna S 2.1 are open in the same legal sense and frontier-adjacent in the same marketing sense — but the moment you try to actually deploy either one, they split into two completely different products. One is a box on your desk. The other is a data center you rent. Here's the decision, made concrete.

They are not measured on the same yardstick#

Start by throwing out the instinct to rank them by score. Kimi K3 took the #1 spot on the Frontend Code Arena. Laguna S 2.1 is reported by poolside at 70.2% on Terminal-Bench 2.1 — but in poolside's own agent harness, with thinking enabled. Those are different benchmarks measured in different harnesses, and a vendor-run number on a vendor's harness is a starting point, not a verdict. Neither figure tells you which model is better at your task. So the honest comparison isn't "which wins" — it's "which one fits how you need to run it." On that axis, the gap is enormous and unambiguous.

Kimi K3 — the open frontier you rent#

Kimi K3 is Moonshot's 2.8-trillion-parameter mixture-of-experts model. Only about 16 of its 896 experts fire per token, so roughly 50 billion parameters are active on any given forward pass and per-token compute feels like a mid-size model. It carries a 1M-token context, and its full weights publish on Hugging Face on July 27 under a modified MIT license.

Here's the catch that governs everything: those weights need roughly 1.4TB of fast memory even in four-bit (MXFP4) precision — before a single token of context loads. That is not a single-machine number. For nearly every solopreneur and early-stage team, "self-hosting Kimi K3" is a fantasy, and the real path is to call it through a hosted API (in the neighborhood of $3 per million input tokens and $15 per million output). K3 is the most capable open weight you can point at — just not the one you'll own. We ran the full economics in the 1.4TB decision.

Laguna S 2.1 — the open weight you own#

Laguna S 2.1 is poolside's answer to exactly that problem. It's a 118-billion-parameter sparse MoE with about 8 billion active parameters per token and a 1M-token context, billed as the West's most capable open weight. The number that matters most isn't the benchmark — it's that it runs on a single NVIDIA DGX Spark. One box. It ships under the OpenMDW-1.1 license, from the Linux Foundation's open-model-weights family.

That single-box footprint is the whole pitch. When your model fits on hardware you can buy and rack yourself, you get the things a hosted API can never give you: tokens that never leave your network, fine-tuning on private data without a data-processing agreement, and a cost curve that's a fixed capital expense instead of a per-token meter. For a founder building something where data residency or a private fine-tune is the product, Laguna S 2.1 is the first genuinely frontier-adjacent open coder that fits. Note that poolside also shipped a smaller Laguna XS 2.1 earlier in July that runs on a laptop — if 118B is more than you need, start there.

The decision, in one paragraph#

Pick Laguna S 2.1 when self-hosting is the point — private data, network isolation, a fine-tune you own, or volume high enough that a box beats a meter. Pick Kimi K3 when you want the most capable open frontier available and you're comfortable renting it, because owning it isn't realistic at 1.4TB. And if neither "I must self-host" nor "I want the open frontier specifically" is true for you, the quiet third answer is that a cheap hosted workhorse like Gemini 3.6 Flash at $1.50/$7.50 per million tokens will out-simplify both — a point we make in the late-July model-wave shipping log. Open weights are leverage. Only take on the ones whose deployment shape you actually want to run. </content>