Ripple-65B: US startup trains an open coding model for just $32 million

US company Ricursive Intelligence has released Ripple-65B Preview, a 65-billion-parameter language model trained from scratch and licensed under the permissive Apache 2.0 license. The company claims it beats US models up to 15 times its size at agentic coding, and says the whole effort cost only $32 million.

Model releases Try it yourself Nov 4, 2026 7 min read Source: Reddit r/SillyTavernAI
Illustrative image, AI-generated

What's going on

US company Ricursive Intelligence released Ripple-65B Preview on November 4, 2026. The language model has 65 billion parameters, and the company says it trained it entirely in-house. In other words, it isn't built on top of a model from Meta, Alibaba or anyone else. The weights are freely available on Hugging Face at ricursiveAI/Ripple-65B-Preview under the Apache 2.0 license, one of the most permissive licenses around: you can use the model commercially, modify it and redistribute it. Ripple is also available via API from Together AI, GMI Cloud and OpenRouter. According to startup portal ecosistemastartup.com, Fireworks added it the same day.

Ricursive doesn't see itself as a typical model lab. It calls itself a "full-stack lab" that co-optimizes hardware, software and models, with the goal of building self-improving systems. Ricursive says Ripple is the general-purpose version of an unreleased in-house model that powers the company's chip design platform.

The claim: small beats big at agentic coding

Ricursive is pitching Ripple as the new leader among open US models for agentic coding. That means the AI works on its own in a terminal: it runs commands, edits files and handles multi-step tasks. The main yardstick here is TerminalBench 2.1. Here's the table the company published:

Model Parameters TerminalBench 2.1
Ripple-65B Preview 65B (dense) 80.52
Reflection Beam 501B 80.1
Meta Muse Spark Open 816B 76.4
Thinking Machines Inkling 975B 63.8
NVIDIA Nemotron 3 Ultra 550B 56.4

The Model Card lists more results: 79.1 on SWE-bench Pro v2.0 Hard, 76.5 on SWE-bench Verified and 44.3 on DeepSWE 1.1. Every one of these numbers comes from Ricursive. According to OrcaRouter, the Model Card quietly notes that the benchmark scores were "hard to reproduce." They were measured at maximum effort and full BF16 precision. Nobody has independently verified them yet.

How the model is built

Most labs use Mixture-of-Experts (MoE). In an MoE model, only a small part of the network does the work for each token, a bit like a big hospital where a patient only sees the relevant specialists. Ricursive deliberately went the other way. Ripple is a dense model, so all 65 billion parameters are active for every token. The company says this makes training and serving simpler. It claims it sustained 40 percent model FLOPs utilization (MFU) with straightforward sharding across chips, no custom GPU kernels and no quantization.

The architecture is "thin and deep": 80 layers with a width of 5,120. Ricursive describes the design as a move away from the Allen Institute for AI's open Olmo 3 and toward a layout similar to Google's Gemma 3N. It includes:

  • more attention heads than usual. Attention is the mechanism the model uses to decide which earlier parts of the text matter right now.
  • a higher share of sliding-window attention. These layers only look at a limited stretch of text, like a reader who only remembers the last few pages. That makes them much cheaper than global attention, which looks at the whole text.
  • "gated attention," global NoPE (layers without positional encoding), value residuals and clamping of extreme values in the feed-forward layers.

Pretraining ran for 877,500 steps on 8,000-token sequences, 12 trillion tokens in total. The data is almost entirely English text and code. Then came mid-training, a long-context phase and a light round of reinforcement learning (RL), where the model learns by getting rewarded for solving tasks. That phase focused on agentic coding. The model is text-only and doesn't understand images.

Cheap and efficient to train, according to the company

The second big headline is the price. Ricursive says the entire project cost about $32 million. That figure supposedly covers early experiments, data mixing, evaluation, debugging, synthetic training data and the final training runs. The company says that's roughly a tenth of what the previous leader cost. For comparison, it points to Sam Altman, who said in 2023 that GPT-4 cost more than $100 million. Of rival Reflection, Ricursive writes that it reportedly committed $150 million a month to compute. TNW also reported compute deals worth $6.3 billion with SpaceX and $1 billion with Nebius.

For RL, Ripple reportedly needed only 1.4 million rollouts, practice runs where the model attempts a task and gets scored. The company says that's about 70 times fewer than Reflection Beam. Instead of buying training data, Ricursive generated and filtered synthetic data with its own pipelines. It started from Olmo 3's experiment series (the "ladder"). Over six iterations (v1.0 to v1.6), Ricursive says it improved compute efficiency for code training by up to 16x, measured on a smaller 4-billion-parameter model. Ecosistemastartup.com sees this as the part of the story others can actually copy: run cheap tests at small scale first, and only then train big.

Pricing, context and contradictions

According to OrcaRouter, third-party providers charge around $0.20 per million input tokens and $0.60 per million output tokens for Ripple. For comparison, Kimi K3.1 Pro, released the same day, costs $2 and $10. Ricursive hasn't published its own price list, though. And the first hosted endpoint offers only 16,384 tokens of context instead of the advertised 1 million. OrcaRouter also notes that at least one tracker wrongly lists the model as proprietary.

OrcaRouter also warns about a popular apples-to-oranges comparison. On forums, Ripple's 80.5 on TerminalBench 2.1 often gets put next to Kimi's 65.7 on TerminalBench 4.0. But version 4.0 is a later, harder test, so the two numbers can't be compared. Even for the same model on the same test, results can swing by several points depending on the test harness.

What you need to try it

At full BF16 precision, the model weighs about 130 GB. That won't fit on any single consumer GPU, and despite what some reports suggest, it won't easily fit on a MacBook either. Ricursive names NVIDIA DGX Spark as the target device, a compact AI machine with lots of unified memory. On two B200 data center GPUs, the company says the model hits 250 tokens per second with 8 concurrent requests. The repository also includes an NVFP4 variant, a 4-bit format for Nvidia's newer Blackwell generation that makes running it on smaller machines possible in the first place.

As a rough rule of thumb, a 4-bit version needs about 40 GB of VRAM (video memory). That means two 24 GB cards, a workstation card, or a Mac with 64 GB or more of unified memory. The sources don't mention ready-made GGUF files for llama.cpp or Ollama yet. If you don't have the hardware, you can try the model cheaply on OpenRouter or Together AI. The longer the context, the more memory you'll need on top.

The bigger picture

Ripple is interesting for two reasons. First, according to CNET, the strongest open models currently come from China: DeepSeek, Kimi K3 and Qwen3.8 top the Artificial Analysis leaderboards. A fully home-grown, relatively small US model under a genuine open-source license is a statement. Second, if the numbers hold up, Ricursive shows that strong agentic performance doesn't necessarily require billion-dollar budgets and trillion-parameter models.

Still, be careful. Almost all the numbers come from the company. The Model Card admits reproducibility problems, and this is a "preview" release. The model is focused on English and code, so expect weaker results in other languages. But if you want to run a local coding agent on your own hardware or fine-tune a model, a dense 65B model under Apache 2.0 is a far more accessible starting point than a trillion-parameter MoE.

Sources

#ripple-65b#ricursive#open-weights#coding-agents#apache-2.0
Read the original source

Try it yourself: Ripple-65B Preview

Explained step by step, no prior knowledge needed – on your own computer or free in your browser.

What can I do with it?

Ripple-65B is built first and foremost as a coding agent. It can run commands in a terminal on its own, fix code over multiple steps and work through software tasks. The company says it beats open US models with 500 to almost 1,000 billion parameters on TerminalBench 2.1 (80.52 points), but those numbers haven't been independently confirmed. The model is text-only and can't read images. It was trained mostly on English and code, so don't expect top quality in other languages. It doesn't have adjustable reasoning levels like big reasoning models do, which keeps its answers shorter and cheaper. Since it's licensed under Apache 2.0, it also makes a good base for your own fine-tuning.

Who is it worth it for?

Ripple is worth it for developers and tinkerers with serious hardware (around 40 GB of VRAM or more) who want to run a local coding agent with no ongoing API costs, or fine-tune a model for commercial use. If you only have a regular gaming GPU with 8 to 16 GB, or mainly want to write text in languages other than English, smaller or multilingual models will serve you better. You can test it cheaply on OpenRouter or Together AI.

Ideas: What you can do with it

Local coding assistant

Hook Ripple up to an agentic editor or terminal tool through a local API. It can then hunt down bugs in your project, write tests and suggest fixes, all without your code ever leaving your machine.

Scripts for your home server

Have it write Bash or Python scripts for backups, file sorting or system monitoring, and refine them step by step. You can test the result right away and feed the error message back to the model so it can fix it.

Code reviews at work

Because it's licensed under Apache 2.0, you can run the model commercially on your own network. It can pre-screen pull requests and flag potential bugs without sending sensitive data to a cloud provider.

Base for your own fine-tuning

Use the base variant to further train the model on your own codebase or internal tools. The result is a specialized assistant that knows your project's conventions.

Understanding legacy code

Paste in old, poorly documented code and have it explained and commented. That helps you get up to speed on projects you've inherited.

Size64.8 B parameters
Download130 GB (about 2.9 hr at 100 Mbit/s)
Licenseapache-2.0
TypeAI model

What your computer needs

Graphics card (NVIDIA) at least 157 GB VRAMCalculated, not measured: the BF16 weights (16 files) total 129.6 GB. 129.6 × 1.2 + 1 comes to about 157 GB. The company's test system is 2× NVIDIA B200 (384 GB combined). For a single box like the DGX Spark (128 GB), it recommends the smaller NVFP4 version. More memory lets you fit longer texts (context) and multiple requests at once.
Mac (Apple Silicon M1–M5) from 256 GB unified memoryThe GPU and CPU share the memory – the model can use about 70% of it
Storage approx. 132 GB freeModel download plus programs

The repository contains a BF16 checkpoint (about 130 GB, only for data center GPUs or machines with huge amounts of memory), an NVFP4 variant (4-bit, for Nvidia's Blackwell generation such as DGX Spark or RTX 50 cards) and an unpolished base variant meant for your own training. For home use, a 4-bit version makes sense; it needs roughly 40 GB of memory. The sources don't mention ready-made GGUF files yet, and it's unclear whether the community will provide them.

  • At full BF16 precision, the model takes up about 130 GB. That won't fit on a single consumer GPU, or on a MacBook without quantization.
  • Ricursive explicitly names NVIDIA DGX Spark as the target device for running it locally.
  • On two B200 GPUs, the company says the model reaches about 250 tokens per second with 8 concurrent requests.
  • The NVFP4 variant is designed for Nvidia's Blackwell generation. Older cards don't support this format natively.
  • With 4-bit quantization, you'll need roughly 40 GB of VRAM or unified memory (e.g. 2×24 GB or a Mac with 64 GB+).
  • The advertised 1-million-token context window eats up a lot of extra memory. Locally, start with a much shorter context.

Groß (64,8 Mrd. Parameter): braucht auch quantisiert ~40.4 GB VRAM/RAM. Colab Free (T4, 15 GB) isn't enough.

How do I find out what my computer has?
  • Windows: Press Ctrl + Shift + Esc → Task Manager → Performance tab → click GPU on the left. At the bottom you'll see Dedicated GPU memory (that's your VRAM). You'll find system memory under Memory.
  • Mac: Apple menu at the top left → About This Mac. You'll see your chip (e.g. M2) and memory (e.g. 16 GB). On Apple chips, graphics and processor share this memory.
  • Linux: Type nvidia-smi in the terminal (shows your graphics card and its memory) and free -h for system memory.

Guide

This model runs with its developers' own program (allenai/olmes on GitHub). The commands below come from the Model Card and the developers' instructions.

Windows 10 / 11

Windows 10 / 11: not officially tested. There's no information for Windows, and vLLM usually doesn't run natively on Windows. You're better off using WSL2 (Linux built into Windows) and following the Linux guide there. For most people, a rented cloud machine or the company's Colab notebook for the NVFP4 version is the more realistic option.

  1. Check the prerequisites. You'll need Python 3 (use a recent version like 3.11), Git for Windows and an up-to-date NVIDIA driver. Plan for about 140 GB of free disk space. Open PowerShell and use the commands below to check that everything is installed.
    python --version
    git --version
    nvidia-smi
  2. Download OLMES. This fetches the OLMES evaluation tool from GitHub and switches into its folder.
    git clone https://github.com/allenai/olmes.git
    cd olmes
  3. Create a virtual environment. A virtual environment keeps the Python packages separate from the rest of your system. If PowerShell says scripts are blocked, run "Set-ExecutionPolicy -Scope CurrentUser RemoteSigned" once first. When the environment is active, you'll see "(.venv)" at the start of the line.
    python -m venv .venv
    .venv\Scripts\Activate.ps1
  4. Install OLMES. This installs OLMES. The "[gpu]" extra for vLLM will probably fail on Windows. If it does, just skip it and OLMES will use the standard Hugging Face backend.
    pip install -e .
    pip install -e ".[gpu]"
  5. Quick test of the installation. A trial run with a tiny test model. If you see a sample question and some numbers at the end, OLMES is working.
    olmes --task arc_challenge:mc::olmes --inspect
  6. Download the model. This downloads the roughly 130 GB of model files. It takes a long time. If it gets interrupted, just run the command again.
    pip install huggingface_hub
    hf download ricursiveAI/Ripple-65B-Preview
  7. Run your first test. Ripple-65B now answers the ARC Challenge questions. If the program reports an unknown architecture, add --model-args '{"trust_remote_code": true}'. The results end up in the "workspace" folder.
    olmes --model ricursiveAI/Ripple-65B-Preview --task arc_challenge::olmes --output-dir workspace
  8. Result. The "workspace" folder contains the result files from an ARC Challenge run. They show how many knowledge questions Ripple-65B answered correctly.

macOS

macOS: not officially tested. According to the company, the model is built for NVIDIA hardware. vLLM isn't supported on the Mac. Only Macs with a huge amount of unified memory (well over 160 GB) could even load the BF16 model, and even that is untested. A cloud machine or the company's Colab notebook for the NVFP4 version is more realistic.

  1. Check the prerequisites. You'll need the Xcode Command Line Tools (which include Git), Python 3 and about 140 GB of free disk space. Open Terminal. The first command installs the Xcode tools if they're missing.
    xcode-select --install
    python3 --version
    git --version
  2. Download OLMES. This fetches the OLMES evaluation tool and switches into its folder.
    git clone https://github.com/allenai/olmes.git
    cd olmes
  3. Create a virtual environment. This sets up an isolated space for the Python packages. When it's active, you'll see "(.venv)" at the start of the line.
    python3 -m venv .venv
    source .venv/bin/activate
  4. Install OLMES. Install only the base package. The "[gpu]" extra with vLLM is meant for NVIDIA GPUs and won't run on the Mac.
    pip install -e .
  5. Quick test of the installation. A trial run with a tiny test model. If you see a sample question and some numbers at the end, OLMES is working.
    olmes --task arc_challenge:mc::olmes --inspect
  6. Download the model. This downloads the roughly 130 GB of model files. It takes a long time. If it gets interrupted, just run the command again.
    pip install huggingface_hub
    hf download ricursiveAI/Ripple-65B-Preview
  7. Run your first test. Ripple-65B now answers the ARC Challenge questions. On a Mac, this can be extremely slow or run out of memory. If you get a message about an unknown architecture, add --model-args '{"trust_remote_code": true}'. The results end up in the "workspace" folder.
    olmes --model ricursiveAI/Ripple-65B-Preview --task arc_challenge::olmes --output-dir workspace
  8. Result. The "workspace" folder contains the result files from an ARC Challenge run. They show how many knowledge questions Ripple-65B answered correctly.

Linux

Linux: not officially tested. The model itself has no official quick-start guide. The only program the source points to is OLMES, an evaluation tool that scores language models on test questions. It's not a chat app. Linux with NVIDIA GPUs is the most obvious route, but it hasn't been explicitly tested. You'll need about 157 GB of VRAM, which in practice means several data center GPUs.

  1. Check the prerequisites. You'll need Python 3 (the source doesn't specify a version, so use a recent one like 3.11), Git and an up-to-date NVIDIA driver with CUDA. CUDA is NVIDIA's compute interface for the GPU. Plan for about 140 GB of free disk space for the model. Use the commands below to check that everything is installed. nvidia-smi should list your GPUs along with their memory.
    python3 --version
    git --version
    nvidia-smi
  2. Download OLMES. This fetches the OLMES evaluation tool from GitHub and switches into its folder. You'll end up with a new "olmes" folder.
    git clone https://github.com/allenai/olmes.git
    cd olmes
  3. Create a virtual environment. A virtual environment (venv) is an isolated space for Python packages that keeps the rest of your system clean. When it's active, you'll see "(.venv)" at the start of the line.
    python3 -m venv .venv
    source .venv/bin/activate
  4. Install OLMES. The first command installs OLMES. The second adds vLLM, a fast engine for running large models on NVIDIA GPUs. This takes a few minutes. Red error messages at the end mean something went wrong.
    pip install -e .
    pip install -e ".[gpu]"
  5. Quick test of the installation. This trial run shows a sample question and runs five tasks with a tiny test model (pythia). If you see a question with answer choices and some numbers at the end, OLMES is working.
    olmes --task arc_challenge:mc::olmes --inspect
  6. Download the model. Now grab the roughly 130 GB of model files from Hugging Face, a platform for AI models. Depending on your connection, this can take many hours. If the download breaks off, just run the same command again and it'll pick up where it left off.
    pip install huggingface_hub
    hf download ricursiveAI/Ripple-65B-Preview
  7. Check the launch command. With --dry-run, OLMES only shows what it would do without computing anything. That way you catch typos before the long run starts.
    olmes --model ricursiveAI/Ripple-65B-Preview --task arc_challenge::olmes --output-dir workspace --dry-run
  8. Run your first test. Ripple-65B now answers the ARC Challenge questions, which are grade-school science exam questions. With --model-type vllm, OLMES uses vLLM to run on your GPUs. If the program reports an unknown model architecture, add --model-args '{"trust_remote_code": true}'. Afterwards, the results are in the "workspace" folder.
    olmes --model ricursiveAI/Ripple-65B-Preview --model-type vllm --task arc_challenge::olmes --output-dir workspace
  9. Result. The "workspace" folder contains the result files from an ARC Challenge run. They show how many knowledge questions Ripple-65B answered correctly.

What to do after your first result

  • Instead of ARC Challenge, you can run other tests, for example --task arc_challenge::olmes hellaswag::olmes for two tests at once, or --task mmlu::olmes for the big MMLU knowledge quiz.
  • "oe-eval --list-tasks" shows all available tests, and "olmes --help" shows all options.
  • If you only have a DGX Spark or less memory, use the smaller ricursiveAI/Ripple-65B-Preview-NVFP4 version. The company has announced a Colab notebook to help you get started with it.
  • Important: OLMES only scores the model on test questions. It's not a chat window. For conversations, you need a separate program, and the source doesn't name one.

Try it

Write a Python script that renames all .jpg files in a folder by the date they were taken.
Here's an error message from my Node.js project: [paste error message]. Explain the cause and suggest a fix.
Create a Bash script that makes a daily tar.gz backup of my home directory and deletes backups older than 14 days.
Refactor this Python class to make it testable, and write matching pytest tests: [paste code]
Plan step by step how to package a small Flask app in a Docker container, and provide a Dockerfile and docker-compose.yml.

Tips for better results

  • Write coding tasks in English or at least use English technical terms, since the training data was almost entirely English and code.
  • For agentic tasks, give the model clear goals and stopping criteria, such as "Run the tests until they all pass."
  • Start locally with a small context (e.g. 8,000–32,000 tokens) and only raise it when you need to, to save memory.
  • Try the model on OpenRouter or Together AI before downloading it. At around $0.20/$0.60 per million tokens, that's very cheap.
  • For your own fine-tuning, the base variant is a better starting point than the fully trained version.

If something goes wrong

This is a preview release: expect bugs and behavior changes in later versions.

The Model Card itself warns that the benchmark scores were hard to reproduce. Test the model on your own tasks.

The NVFP4 format only runs on newer Nvidia cards (Blackwell). On older GPUs, you'll need other quantizations.

Some hosted endpoints offer only 16,384 tokens of context instead of the advertised 1 million.

The model is text-only. It can't analyze images or screenshots.

“out of memory,” a crash, or your computer freezes

The model is too big for your VRAM (video memory). Pick a smaller variant from the table above and close other programs, especially games and browsers with lots of tabs.

It runs, but extremely slowly

Your CPU is probably doing the work instead of your graphics card. In Ollama, the PROCESSOR column of ollama ps shows how much runs on the GPU. If it says "100% CPU", update your graphics driver or pick a smaller variant that fits entirely into VRAM (video memory).

“ollama” or “python” is not found

Close the terminal window and open it again so it recognizes the newly installed program. For Python on Windows: reinstall it and check Add python.exe to PATH.

Windows: "Running scripts is disabled on this system"

Run the script with exactly the command above: powershell -ExecutionPolicy Bypass -File try_windows.ps1. This allows execution for this one time only.

Error message when loading the model (version, "trust_remote_code", unknown architecture)

Brand-new models often need the latest software version. With Ollama: update Ollama. With Python: pip install -U transformers in the activated environment. The Model Card usually lists the exact version.

Tokenstrom generates the scripts and notebook automatically. Please take a quick look before running them – they're plain, readable text. Mind the model's license: apache-2.0.

Ask the AI assistant

Questions about this article, installation or background? Our assistant knows this page and runs on our own machine, not in someone else's cloud.

Connecting …

The Assistant is an AI (Gemma 4) and can make mistakes – please check important details against the source. Questions are used only to generate an answer and are deleted after one hour. Please don't enter any personal data.

Comments

What do you think? Already tried it? Write it here, no sign-up needed.

  1. Loading comments …

Comments are public. Links aren't allowed, and we delete abusive posts. You can delete your own comment at any time in this browser. Learn more in the Privacy Policy.