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

NVIDIA Nemotron 3.5 Bolt E4B 4GB vs Ripple-65B Preview

NVIDIA Nemotron 3.5 Bolt E4B 4GB scores 61 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in every scored category. 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

NVIDIA Nemotron 3.5 Bolt E4B 4GB C

Best for Agents and apps that need a fast local conversational model with tool calls on an 8 to 12 GB GPU, a Mac or a Jetson, such as voice assistants and game characters.

Ahead on

  • Reach, 90 against 45
  • Risk, 80 against 55
  • Agent interface, 85 against 75
  • Documentation and upkeep, 65 against 49

Watch for

64K tokens of context against the base's 128K, and Ollama's and LM Studio's pages show 128K anyway

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.

No category where it leads by five points or more, and no fact that sets it apart.

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 NVIDIA Nemotron 3.5 Bolt E4B 4GB +45

NVIDIA Nemotron 3.5 Bolt E4B 4GB 90

Memory earns 30, since NVIDIA's Q4_K_M GGUF is 6.18 GB, 7.4 GB with a fifth added. Runtimes earn the full 25 from released llama.cpp, vLLM, Transformers, SGLang, Ollama and LM Studio. Builds earn 10, as NVIDIA's only quantised build is the Q4_K_M GGUF and the DFlash repositories are drafters. Terms earn 10, because OpenMDW-1.1 is permissive with no threshold or use policy but isn't an OSI licence, and the Gemma 4 base adds plain Apache 2.0. Download earns 10, with no gate. Hosted earns 5, as NVIDIA's own API serves it.

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.

Risk NVIDIA Nemotron 3.5 Bolt E4B 4GB +25

NVIDIA Nemotron 3.5 Bolt E4B 4GB 80

File safety earns 25, safetensors and GGUF only, and the documented routes run no repository code (an undocumented Inference Endpoints handler.py sits in the BF16 repository). Provenance earns 15, NVIDIA's linked organisation with a hash for every file. Safety evaluation earns 0, since NVIDIA names its content-safety and bias datasets but publishes no results. Agent guidance earns 15, for instruction-hierarchy training NVIDIA documents and a subcard on prompt injection and the safeguards to add. Licence risk keeps all 15 under OpenMDW-1.1 and Apache 2.0. The security programme earns 10 for the card's reporting route and NVIDIA's public bulletins.

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.

Documentation and upkeep NVIDIA Nemotron 3.5 Bolt E4B 4GB +16

NVIDIA Nemotron 3.5 Bolt E4B 4GB 65

The model card earns 20, all seven items with limitations in the linked subcard. Training data earns 15, the RL datasets published and a cut-off given, but the card's data section describes a larger SFT corpus the report says wasn't used, and the base's pre-training is described only in general. Last change earns 20 for 23 October 2026. Responsiveness earns 0, as NVIDIA hasn't answered either of the two discussions. Version policy earns 5 as a first release whose GGUF was replaced on release day with only a commit title. File health earns 5, since the card and the template disagree on the thinking default and both cards carry leftover lines.

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 NVIDIA Nemotron 3.5 Bolt E4B 4GB +10

NVIDIA Nemotron 3.5 Bolt E4B 4GB 85

The chat template earns 20, a Jinja file in the repository and the GGUF. The tool-calling format earns 25, with OpenAI-style tools, the gemma4 parser named and an asynchronous pattern documented. Trained tool calling earns 20, multi-step tool-use training and several calls per turn. Structured output earns 5, trained but with no instructions. Reasoning control earns 10, thinking per request, the reasoning returned apart and a budget. Context earns 5 for 64K, half the base's 128K.

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 runNVIDIA Nemotron 3.5 Bolt E4B 4GBRipple-65B PreviewEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259045NVIDIA Nemotron 3.5 Bolt E4B 4GB +45
Risk20%208055NVIDIA Nemotron 3.5 Bolt E4B 4GB +25
Agent interface10%108575NVIDIA Nemotron 3.5 Bolt E4B 4GB +10
Documentation and upkeep10%106549NVIDIA Nemotron 3.5 Bolt E4B 4GB +16
Negative events≤1500
TotalC 61/100D 53.3/100

Facts side by side

FactNVIDIA Nemotron 3.5 Bolt E4B 4GBRipple-65B Preview
KindOpen-weight modelOpen-weight model
VendorNVIDIARicursive Intelligence
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceOpenMDW-1.1Apache-2.0
Read-only variant documentednono
llms.txtnono
Last release2026-10-232026-11-04
Terms last updatedno document linkednot read yet
Privacy policy last updatedno document linkedno document linked
Agent reviews4/5 (4)none

Verdicts

NVIDIA Nemotron 3.5 Bolt E4B 4GB

A small cousin for voice and device assistants, game characters and robot interfaces, trained for multi-turn tool calls, instruction hierarchy and short spoken replies, with thinking switchable per request. NVIDIA's Q4_K_M GGUF needs about 8 GB, and Ollama and LM Studio carry it. Context is 64K, half the Gemma 4 base, and NVIDIA publishes no safety results.

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

NVIDIA Nemotron 3.5 Bolt E4B 4GB

  1. Quickest start is ollama run nemotron-3.5-bolt:e4b, about 8 GB of files, and set num_ctx to 65536 or less, since NVIDIA supports 64K
  2. With NVIDIA's GGUF use llama-server -m Nemotron-3.5-Bolt-E4B-Q4_K_M.gguf -c 65536 -ngl 999 --jinja, and add --reasoning on --reasoning-budget <tokens> to cap thinking
  3. With vLLM 0.31.0 or later pass --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4 and the repository's chat_template.jinja
  4. Pass enable_thinking explicitly in chat_template_kwargs, since the template defaults to off whatever the card says, and set skip_special_tokens false as the card's examples do
  5. Use temperature=1.0 and top_p=0.95 in both modes, as the card says
  6. Set conversational_mode true for spoken replies, which appends a brevity instruction to the system prompt
  7. Answer a slow tool at once with a pending tool message, then send the result later as a user message starting TOOL RESULT, as the card's asynchronous pattern says
  8. Keep persistent rules in the system prompt and send state updates as separate user or system messages in order, per the card's prompting guidelines

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, NVIDIA Nemotron 3.5 Bolt E4B 4GB or Ripple-65B Preview?

NVIDIA Nemotron 3.5 Bolt E4B 4GB scores 61 (C) on agent readiness against Ripple-65B Preview's 53.3 (D), and leads in every scored category.

Other comparisons with NVIDIA Nemotron 3.5 Bolt E4B 4GB 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.