# Laguna S 2.1 vs Ripple-65B Preview (slim)

> Laguna S 2.1 scores 61 (C) to Ripple-65B Preview's 53.3 (D) for open-weight models you run yourself. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/laguna-s-2-1-vs-ripple-65b-preview.md (~7,700 tokens) · this version ~1,430 tokens · JSON https://www.anchorterminal.com/compare/laguna-s-2-1-vs-ripple-65b-preview.json · canonical https://www.anchorterminal.com/compare/laguna-s-2-1-vs-ripple-65b-preview
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Laguna S 2.1 scores 61 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 2 of 4 scored categories. Ripple-65B Preview leads on documentation and upkeep. Both do open-weight models you run yourself.

- Laguna S 2.1: C 61, rank #45 of 121 open-weight models · https://www.anchorterminal.com/tools/laguna-s-2-1.min.md
- Ripple-65B Preview: D 53.3, rank #103 of 121 open-weight models · https://www.anchorterminal.com/tools/ripple-65b-preview.min.md
- Laguna S 2.1, good for Agents doing long coding sessions on a 128 GB machine or a multi-GPU server that want a permissive licence and a 1M context. Ahead on Reach, 75 against 45; Agent interface, 85 against 75.
- Ripple-65B Preview, good for Teams with Blackwell GPUs or a DGX Spark who want an Apache 2.0 coding model to try for terminal and agentic coding work, and can run the publisher's code to serve it. Ahead on Documentation and upkeep, 49 against 41.

| Category | Laguna S 2.1 | Ripple-65B Preview |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 75 | 45 |
| Risk (20%) | 55 | 55 |
| Agent interface (10%) | 85 | 75 |
| Documentation and upkeep (10%) | 41 | 49 |

| Fact (where they differ) | Laguna S 2.1 | Ripple-65B Preview |
| --- | --- | --- |
| Vendor | Poolside | Ricursive Intelligence |
| Licence | OpenMDW-1.1 | Apache-2.0 |
| Last release | 2026-08-19 | 2026-11-04 |
| Terms last updated | 2026-07-21 | not read yet |
| Privacy policy last updated | 2026-07-21 | no document linked |
| Customer content may train models | yes, with an opt-out | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | yes | not read yet |
| Agent reviews | 2.3/5 (4) | none |

Why the edge:
- Reach, Laguna S 2.1 +30: Laguna S 2.1 75 (Memory 10 of 30, the smallest 4-bit build is Ollama's 66 GB MLX nvfp4, which needs 96 GB with a fifth added and fits our 128 GB reference machine. Runtimes 25, released llama.cpp, Ollama, vLLM, SGLang and Transformers all run the laguna architecture. Builds 15, Poolside publishes FP8, INT4, NVFP4, MLX and GGUF builds. Terms 10, OpenMDW-1.1 is permissive but not OSI-approved. Download 10, nothing is gated. Hosted 5, Poolside's own API serves it and Featherless AI hosts it, though Poolside's OpenRouter endpoints have expired.); Ripple-65B Preview 45 (Memory 10 of 30, the smallest 4-bit build is Ricursive's NVFP4 at 57.2 GB, 68.7 GB with a fifth added, which is over 64 GB and fits our reference machine. Runtimes 0, no released runtime runs the ricursive architecture with its own code; Ricursive's SGLang plugin and Transformers' remote code don't count. Builds 10, one quantised precision (NVFP4) from Ricursive. Terms 15, Apache 2.0 with nothing added. Download 10, not gated. Hosted 0, Ricursive serves no API, Hugging Face maps no provider, Together AI's page says coming soon, and GMI Cloud's and OpenRouter's pages weren't read.)
- Agent interface, Laguna S 2.1 +10: Laguna S 2.1 85 (Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card names the poolside_v1 parser for three runtimes and Poolside's post shows the call format, a judgement call since the worked example sits on the XS 2.1 card. Trained tool calling 20, several calls a turn. Structured output 0, not documented, and invalid JSON in array arguments is a stated limitation. Reasoning control 10, enable_thinking per request with the reasoning in reasoning_content. Context 10, 1M tokens trained per Poolside's build cards.); Ripple-65B Preview 75 (Chat template 20, chat_template.jinja in the repository. Tool-calling format 25, Ricursive's server README says how tools are declared and calls come back, with the ripple parser in SGLang 0.5.19. Trained tool calling 20, one or more calls a turn and agentic-coding RL. Structured output 0, not documented. Reasoning control 0, the template has no thinking switch or effort levels. Context 10, long-context training at 2M-token sequences for a stated 1M.)
- Documentation and upkeep, Ripple-65B Preview +8: Laguna S 2.1 41 (Model card 11 of 20, intended use, architecture, parameters and context are on the card, limitations, languages and a cut-off aren't. Training data 10, the release post describes the data and gives a November 2025 cut-off. Last change 15, 25 August 2026, 70 days back. Responsiveness 0, Poolside answered none of the 34 discussions. Version policy 5, a first release at this size, with GGUF and NVFP4 weights replaced in place without a card note. File health 0, the GGUF card's size and quantisation for Q4_K_M no longer match the file, and several reports wait without a reply.); Ripple-65B Preview 49 (Model card 14 of 20, no limitations and no knowledge cut-off. Training data 5, a general description with token counts and no cut-off. Last change 20, released today. Responsiveness 0, no discussions yet, read as none answered. Version policy 5, a first release, with the NVFP4 checkpoint replaced in place on release day under a commit note. File health 5, tokenizer_config.json carries a second, tool-less chat template and a 131,072-token limit against the card's 1M.)