On July 21, 2026, Poolside released Laguna S 2.1, a 118-billion-parameter Mixture-of-Experts coding model whose download weights went live on Hugging Face the same day. The model activates only 8 billion parameters per token and ships under the OpenMDW-1.1 license, which allows download, self-hosting, and fine-tuning without negotiation. Poolside is pitching the release as a Western open-weight option in a coding-model segment it argues has been dominated by Chinese labs, and the company published benchmark numbers that put Laguna S 2.1 ahead of several models many times its effective size.
What changed for code-focused open-weight models on July 21, 2026
Laguna S 2.1 is a sparse MoE model built with 256 routed experts plus one shared expert. It uses grouped-query attention and interleaved sliding-window layers, and the model accepts a context window of up to 1 million tokens. Pre-training started on May 22, 2026, and the public release landed fewer than nine weeks later, the third shipped model from Poolside in three months. Training ran on 4,096 Nvidia H200 GPUs, and the model is small enough at inference time to run on a single Nvidia DGX Spark, since serving cost tracks the active 8-billion-parameter footprint rather than the full 118 billion.
Why this release matters for teams auditing their own infrastructure
For technical SEO work specifically, the practical question is whether a hosted API change or a self-hosted swap can be validated on your own pages without a sales call. A few checkpoints worth running the next time you evaluate a coding model that lands on Hugging Face:
- Crawl and render parity. Before you trust a model to fix template fragments, schema markup, or hreflang wiring, run a controlled batch of pages through the model and compare the rendered HTML against your staging baseline. Watch for silent changes to canonical tags, robots meta directives, and JSON-LD blocks.
- Latency under realistic context. A 1-million-token context window is only useful if the model still returns within the budgets your pipelines assume. Time end-to-end runs on logs, sitemaps, and template dumps you’ll actually feed it.
- Cost mapping. Because only 8B parameters activate per token, project your monthly bill against the full 118B model you might otherwise rent. The active-parameter count is the number that drives inference cost, and Laguna S 2.1’s published hardware footprint (a single DGX Spark) is the benchmark to pressure-test.
- License surface area. OpenMDW-1.1 is permissive, but read the terms for redistribution, fine-tuning disclosure, and any use-case restrictions before you ship a derivative into a production crawler or indexer.
- Versioning and rollback. If you replace a previous coding model inside an internal tool that emits redirects, sitemaps, or robots.txt updates, version-pin the model and keep the prior artifact reachable so a regression can be reproduced.
How does Laguna S 2.1 score on coding benchmarks?
Terminal-Bench 2.1 long-horizon tasks
On Terminal-Bench 2.1, a benchmark for long-horizon terminal tasks, Laguna S 2.1 posts 70.2 percent, which places it 11th on Poolside’s compiled leaderboard. Ahead of it on that board sit other models, but the comparison Poolside highlights is against larger systems: DeepSeek-V4-Pro-Max at 1.6 trillion parameters scored 64.0, Thinking Machines Inkling at 975 billion parameters scored 63.8, and Nvidia Nemotron 3 Ultra at 550 billion parameters scored 56.4. Laguna S 2.1 is reported as beating all three despite an active parameter count roughly 1/200th of DeepSeek-V4-Pro-Max’s.
Other coding benchmarks
On SWE-Bench Multilingual, Laguna S 2.1 reaches 78.5 percent. On the SWE-Bench Pro public dataset, the model lands at 59.4 percent. With thinking mode enabled on its hardest benchmark, the model consumes roughly 249,000 completion tokens per trajectory, a number worth pricing in if you intend to run long reasoning passes in production.
Why is Poolside releasing open weights now?
Poolside frames the launch as a response to what it describes as Chinese open-weight dominance in coding models. The company’s release materials name DeepSeek, Qwen, Kimi, GLM, MiniMax, and Tencent Hunyuan as the labs it is positioning against. Poolside also notes that Laguna S 2.1 occupies a size class into which no Western lab has shipped open weights in 11 months, dating back to OpenAI’s gpt-oss-120b in August of the prior year.
Co-CEO Jason Warner tied the strategy to sovereignty, stating that the West needs open-weight models it can trust, run, and build on. Co-founder and co-CEO Eiso Kant wrote on X that he believes intelligence should and will become a commodity. Poolside has historically sold primarily to government and defense buyers, and a self-hostable, auditable, modifiable coding model fits that buyer profile, since sovereign customers can keep the weights on their own infrastructure.
What developers and procurement teams get
The OpenMDW-1.1 license on Hugging Face is the access mechanism. Anyone can download the weights, run them on their own hardware, and fine-tune them under the license’s terms. Because the active parameter count is 8 billion rather than the full 118 billion, the published claim is that organizations can serve Laguna S 2.1 on far less hardware than the larger models it outperforms on coding tasks. The smallest supported deployment Poolside cites is a single Nvidia DGX Spark.
FAQ
What is Laguna S 2.1?
Laguna S 2.1 is a 118-billion-parameter Mixture-of-Experts coding model released by Poolside on July 21, 2026. It activates 8 billion parameters per token, supports a 1 million-token context window, and is available on Hugging Face under the OpenMDW-1.1 license. Pre-training ran on 4,096 Nvidia H200 GPUs and took under nine weeks from start to public release.
How does Laguna S 2.1 compare to larger models on coding benchmarks?
On Terminal-Bench 2.1, Laguna S 2.1 scores 70.2 percent, ahead of DeepSeek-V4-Pro-Max at 64.0 (1.6 trillion parameters), Thinking Machines Inkling at 63.8 (975 billion parameters), and Nvidia Nemotron 3 Ultra at 56.4 (550 billion parameters). It also posts 78.5 percent on SWE-Bench Multilingual and 59.4 percent on SWE-Bench Pro. With thinking mode enabled on its hardest benchmark, the model consumes roughly 249,000 completion tokens per trajectory.
Why is Poolside releasing an open-weight coding model?
Poolside says the release responds to the dominance of Chinese open-weight labs such as DeepSeek, Qwen, Kimi, GLM, MiniMax, and Tencent Hunyuan, and fills a gap left by Western labs, which had not released open weights in this size class since OpenAI’s gpt-oss-120b in August of the prior year. Co-CEO Jason Warner said the West needs open-weight models it can trust, run, and build on, and the company’s historical focus on government and defense buyers explains the emphasis on self-hosting and auditability.