← All articles

Local AI Gets a Big Boost: How Ollama's New Jev-Style Decision Models Change Everything

2026-10-01 — Michael Leung

Part 3 of 7 · Local AI on an 8GB GPU

Useful already? ☕ Buy me a coffee and keep these articles free and ad-free.

Local AI Gets a Big Boost: How Ollama

If you use local AI workflows, like setting up terminal assistants or building custom systems, you'll want to check out Ollama's latest update. Starting with version 0.35, Ollama now supports Jev-style decision models, which means you can use TypeSafe's fast, typed decision API right on your own machine.

This update isn't just a small improvement. It's a major shift for local deployment and automated workflows.

What Are Jev-Style Models?

Jev-style models don't create long conversations or creative content. They focus on making quick, structured decisions.

With the new /v1/systemone endpoint, you give the model a block of text, called the "state," and a set of typed questions. The model reviews the state and answers each question in a clear, predictable format, like choices, scores, or booleans. This means you no longer need complicated prompt engineering to get a clean JSON response from your AI.

Small, Fast, and Incredibly Effective

What makes these models stand out is how small and efficient they are. They don't use many resources or make your computer work overtime. Ollama now offers three optimized choices:

Since these models are small and run on your own computer, there's almost no delay. For example, Nimble 9B takes only about 91 milliseconds per decision on a modern machine. With no network lag and a lightweight setup, you get real-time results without any API fees.

Small local decision models answer in milliseconds

Why This Changes the Game for Local Architecture

If you're a developer working on automated systems, custom NoSQL databases, or tools like price comparers, this opens up new possibilities:

  1. Intelligent Model Routing: Use a small 0.8B model to quickly check an incoming query and decide if it should go to a larger local model (like Kimi or Gemma 4), a cloud API, or just be handled by a script.
  2. Fast Data Classification: Classify incoming data, error logs, or scraping results with high accuracy and zero cloud dependencies.
  3. Frictionless Integration: Since it uses a simple REST endpoint, adding this to a C# .NET project, a custom WPF app, or a terminal tool is very easy. You send a JSON payload and get a typed JSON decision in return.
A tiny router model decides where each query should go

The Bottom Line

Running fast, structured AI models locally is the future of resilient software architecture. Jev-style decision models in Ollama prove you don't need a massive cloud budget to build highly intelligent, rapid-response systems. It's effective, it's small, and it runs right on your local box.

Series: Local AI on an 8GB GPU

Running real AI models on an ordinary 8GB graphics card, and when the cloud is the better deal.

  1. The Death of Local LLMs? How Xiaomi's MiMo V2.6 Just Flipped the AI Economics in Australia
  2. Unlocking Local AI: Running Qwen-Image-2.1 on an 8GB GPU
  3. Local AI Gets a Big Boost: How Ollama's New Jev-Style Decision Models Change Everything
  4. Run Qwen3.8-Flash-Next on an 8 GB RTX 4060 Ti (Here's How)
  5. The Great LLM Debate 2026: Local Hardware vs. Cloud APIs (An Australian Dev's Guide)
  6. EmbeddingGemma 2 Makes On-Device Multimodal Search Work
  7. Underdog Saluki 27B on an 8GB GPU: Why I Got 4.7 Tokens/s
Next in the series: Run Qwen3.8-Flash-Next on an 8 GB RTX 4060 Ti (Here's How) →

← All articles