# Hy3 vs Ripple-65B Preview (slim)

> Hy3 scores 62.6 (B) 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/hy3-vs-ripple-65b-preview.md (~7,300 tokens) · this version ~1,380 tokens · JSON https://www.anchorterminal.com/compare/hy3-vs-ripple-65b-preview.json · canonical https://www.anchorterminal.com/compare/hy3-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)

Hy3 scores 62.6 (B) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in 3 of 4 scored categories. Both do open-weight models you run yourself.

- Hy3: B 62.6, rank #28 of 121 open-weight models · https://www.anchorterminal.com/tools/hy3.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
- Hy3, good for Teams with an 8-GPU server who want an agent-tuned MoE model under plain Apache 2.0 Ahead on Reach, 70 against 45; Risk, 60 against 55; Documentation and upkeep, 56 against 49.
- 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.

| Category | Hy3 | Ripple-65B Preview |
| --- | --- | --- |
| Capability (35%) | pending | pending |
| Reach (25%) | 70 | 45 |
| Risk (20%) | 60 | 55 |
| Agent interface (10%) | 75 | 75 |
| Documentation and upkeep (10%) | 56 | 49 |

| Fact (where they differ) | Hy3 | Ripple-65B Preview |
| --- | --- | --- |
| Vendor | Tencent (Hy team) | Ricursive Intelligence |
| Last release | 2026-07-20 | 2026-11-04 |
| Terms last updated | no document linked | not read yet |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Reach, Hy3 +25: Hy3 70 (Memory earns 5, because the smallest build of 4-bit precision or better is AngelSlim's GPTQ-Int4 of 168.5 GB, about 202 GB with the fifth added, which is within 256 GB but beyond any single workstation. The 1-bit IQ1_M GGUF fits our reference machine but sits below the 4-bit line. Runtimes earn 20, for model code in released Transformers, vLLM, SGLang and llama.cpp; Ollama and LM Studio have no entry for it. Builds earn the full 15, with Tencent's FP8 repository and AngelSlim's GPTQ and GGUF builds. Terms earn 15 for plain Apache 2.0. Download earns 10, with no gate and no account. Hosted earns 5, since Featherless AI and DeepInfra serve it live through Hugging Face.); 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, Hy3 +7: Hy3 56 (The model card earns 11, covering intended use, architecture, parameters and context but not limitations, languages or a knowledge cut-off. Training data earns 5 for a general statement with no cut-off. The last change earns 10, a config.json edit on 20 July and AngelSlim uploads on 21 July, within 180 days on 2 November 2026; the line drops to 5 after 17 January 2027 unless the files change. Responsiveness earns 10, with Tencent replies on 7 of 19 discussions and none since 22 July. Version policy earns the full 10, since the preview stays in its own repository and the card dates it and says what changed. File health earns 10, with files that agree and no broken-file report waiting.); 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, Hy3 +5: Hy3 60 (File safety earns the full 25, safetensors only with no pickle files, and the documented route runs vLLM or SGLang from their own code with a Jinja template, so nothing from the repository runs at load or prompt time. Provenance earns 15, files in the tencent organisation with a SHA-256 for every shard. Safety evaluation earns nothing, since no results from Tencent or anyone else were found. Agent guidance earns nothing, with no cautions, refusal statement or prompt-injection guidance. Licence risk keeps all 15 under plain Apache 2.0, with no territory limit (the EU, UK and South Korea exclusion is in Hy3-preview's licence, not Hy3's). The security programme earns 5 for Tencent's company-wide Security Response Center, which the card doesn't link, and nothing for advisories, since none were 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.)