# Qwen3-Coder-Next vs Ripple-65B Preview (slim)

> Qwen3-Coder-Next scores 57.6 (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/qwen3-coder-next-vs-ripple-65b-preview.md (~7,850 tokens) · this version ~1,380 tokens · JSON https://www.anchorterminal.com/compare/qwen3-coder-next-vs-ripple-65b-preview.json · canonical https://www.anchorterminal.com/compare/qwen3-coder-next-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)

Qwen3-Coder-Next scores 57.6 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 1 of 4 scored categories. Ripple-65B Preview leads on risk and documentation and upkeep. Both do open-weight models you run yourself.

- Qwen3-Coder-Next: C 57.6, rank #81 of 121 open-weight models · https://www.anchorterminal.com/tools/qwen3-coder-next.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
- Qwen3-Coder-Next, good for Agents that want a local coding model for long tool-calling loops on a single 64 GB to 128 GB machine. Ahead on Reach, 85 against 45.
- 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 Risk, 55 against 50; Documentation and upkeep, 49 against 41.

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

| Fact (where they differ) | Qwen3-Coder-Next | Ripple-65B Preview |
| --- | --- | --- |
| Vendor | Alibaba (Qwen team) | Ricursive Intelligence |
| Last release | 2026-02-03 | 2026-11-04 |
| Terms last updated | no document linked | not read yet |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Reach, Qwen3-Coder-Next +40: Qwen3-Coder-Next 85 (Memory earns 15 of 30, since Alibaba's own Q4_K_M GGUF is 48.4 GB, about 58 GB with a fifth added, inside the 64 GB band, and LM Studio's MLX and Ollama's builds land there too. Runtimes reach the 25 cap on released vLLM (v0.33.0), SGLang (v0.5.23), llama.cpp, Ollama (its library entry, and llama.cpp b11963 pinned by Ollama 0.40.14 has qwen3next), LM Studio and Transformers. Alibaba's FP8 and GGUF builds give builds 15. The Apache 2.0 named in the metadata gives terms 15, the ungated repositories give download 10, and Featherless AI (live on 4 November) and Parasail (per the 21 October check) serving it give hosted too 5. 15+25+15+15+10+5 = 85.); 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 +8: Qwen3-Coder-Next 41 (The card covers four of the seven items and misses limitations, languages and a cut-off (11). The technical report names the data sources, the cut-off and the filtering with some sizes (15). The files last changed on 3 February 2026 (4 February in the GGUF repository), 274 days ago, within a year (5). Alibaba's staff answered none of the 40 discussions; the one reply from a Qwen organisation member is not the publisher's (0), and GitHub issues couldn't be counted. It's a first release (5), and reports of a broken shipped parser and the missing licence wait unanswered (5). 11+15+5+0+5+5 = 41.); 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.)
- Risk, Ripple-65B Preview +5: Qwen3-Coder-Next 50 (Safetensors and GGUF only, with the two shipped parsers outside the documented loading path, gives file safety 25, and files in the Qwen organisation the publisher's GitHub links to, each hashed on the Hub, give provenance 15. Licence risk loses 5 because the card's licence link is broken and no LICENSE file exists anywhere. Safety evaluation, agent guidance and a security programme score 0, since the report's cybersecurity appendix measures skills rather than safe behaviour, nothing guides agent use and no reporting route was found.); Ripple-65B Preview 55 (File safety 15, safetensors only, less 10 because the documented way to run it loads Ricursive's Python. Provenance 15, the files are in the organisation ricursive.com links to, with a checksum on every file. Safety evaluation 10, Ricursive's own FORTRESS and StrongREJECT results. Agent guidance 0, nothing on prompt injection, refusals or safeguards. Licence risk 15, Apache 2.0. Security programme 0, no way to report a flaw.)