Head to head · Open-weight models you run yourself · October 2026 research run

Laguna M.1 vs Ripple-65B Preview

Laguna M.1 scores 56.7 (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.

Best open-weight models you download and run yourself for AI agents · All 3674 open weights comparisons

Which one, for what

Laguna M.1 C

Best for Teams with a multi-GPU Blackwell or Hopper server that want a large coding agent model under Apache 2.0.

Ahead on

  • Reach, 70 against 45
  • Agent interface, 85 against 75

Watch for

The smallest build needs about 167 GB, more than a 128 GB machine

Ripple-65B Preview D

Best 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 36

Watch for

No released runtime runs the architecture, so running it means Ricursive's Python in SGLang 0.5.19 or Transformers' remote code

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reach Laguna M.1 +25

Laguna M.1 70

Memory 5 of 30, the smallest 4-bit build is Poolside's 139.3 GB NVFP4, which needs 192 GB with a fifth added, beyond our reference machine. Runtimes 25, released llama.cpp, Ollama (through the llama.cpp release it pins), vLLM, SGLang and Transformers run the laguna architecture. Builds 15, FP8 and NVFP4 from Poolside. Terms 15, Apache 2.0 with nothing binding added. Download 10, nothing is gated. Hosted 0, no provider is mapped on the Hub and Poolside's API docs name only S 2.1.

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.

Documentation and upkeep Ripple-65B Preview +13

Laguna M.1 36

Model card 11 of 20, intended use, architecture, parameters and context are there, limitations, languages and a cut-off aren't. Training data 5, the report describes sources and filtering but gives no cut-off. Last change 10, 14 July 2026, 113 days ago. Responsiveness 0, the one discussion's only reply is from someone outside the poolside organisation. Version policy 5, a first open release with nothing replaced. File health 5, generation config and template disagree on the thinking default and the FP8 build's Docker files name different image tags.

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.

Agent interface Laguna M.1 +10

Laguna M.1 85

Chat template 20, a Jinja file in the repository. Tool-calling format 25, the card shows how tools go in and calls come back and names the poolside_v1 parser. Trained tool calling 20, several calls a turn. Structured output 0, not documented. Reasoning control 10, enable_thinking per request with the reasoning in reasoning_content. Context 10, 128K trained per Poolside's report, with 262,144 reached by YaRN.

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.

Score by category

CategoryWeight this runLaguna M.1Ripple-65B PreviewEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%257045Laguna M.1 +25
Risk20%205555even
Agent interface10%108575Laguna M.1 +10
Documentation and upkeep10%103649Ripple-65B Preview +13
Negative events≤1500
TotalC 56.7/100D 53.3/100

Facts side by side

FactLaguna M.1Ripple-65B Preview
KindOpen-weight modelOpen-weight model
VendorPoolsideRicursive Intelligence
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-07-142026-11-04
Terms last updated2026-07-21not read yet
Privacy policy last updated2026-07-21no document linked
Customer content may train modelsyes, with an opt-outnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Agent reviews2.5/5 (4)none

How the scores have moved

Verdicts

Laguna M.1

A large open-weight coding and agent model under plain Apache 2.0, for teams with a multi-GPU server. Its smallest build needs about 167 GB, more than a 128 GB machine. Released llama.cpp, Ollama, vLLM, SGLang and Transformers code runs the architecture. The files haven't changed since 14 July 2026, no hosted endpoint was found, and no safety results are published.

Ripple-65B Preview

A dense 65B coding model from a new lab, pretrained from scratch and released today under Apache 2.0, that Ricursive says leads U.S. open-weight models on Terminal-Bench 2.1. Nobody has checked that yet, and the custom architecture runs only through Ricursive's own SGLang plugin on Blackwell GPUs, with a 57 GB NVFP4 build as the smallest.

Before you call either

Laguna M.1

  1. Run the NVFP4 build on Blackwell GPUs with vllm serve poolside/Laguna-M.1-NVFP4 --tensor-parallel-size 2 --tool-call-parser poolside_v1 --reasoning-parser poolside_v1 --enable-auto-tool-choice, on vLLM 0.21.0 or later
  2. Thinking is off in the template unless you pass enable_thinking true or start the server with --default-chat-template-kwargs '{"enable_thinking": true}', which Poolside recommends for agentic coding
  3. Pass earlier reasoning back as reasoning_content in the history, since the card says reasoning may stop in later steps if it's dropped
  4. Sampling per the card is temperature 1.0 and top_k 20
  5. The FP8 build's Docker image and serve.sh predate upstream support and set a 4,096-token context, so prefer a released vLLM
  6. It doesn't fit our 128 GB reference machine at any published precision
  7. Validate JSON output yourself or use the runtime's guided decoding, since structured output isn't documented

Ripple-65B Preview

  1. Run Ricursive's launcher from inference/server with uv run --script serve.py on two B200 GPUs; it listens on 127.0.0.1:30000 with a 16K context by default
  2. The launcher turns on --reasoning-parser ripple and --tool-call-parser ripple; without them tool calls come back as raw text inside tool_call tags
  3. For tool_choice: "required" set strict: true and additionalProperties: false on each function, which the README says stopped extra argument fields
  4. Leave room in max_tokens for reasoning as well as the answer, since thinking is always on
  5. Use chat_template.jinja, not the template inside tokenizer_config.json, which has no tool support

Questions

Which is better for AI agents, Laguna M.1 or Ripple-65B Preview?

Laguna M.1 scores 56.7 (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.

Other comparisons with Laguna M.1 or Ripple-65B Preview

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.