Jev AI

Jev comparison · JevBench v1.7.48 · updated October 31, 2026

Jev vs Winnow

One local model for decisions, chat and images, against a hosted decision model.

On this site

Jev 1.13.0

TypeSafe · System One model

A 71.4 reference score within a point of Winnow’s, better calibrated, and nothing to run.

71.4JevBench v1.7.48 · Open-weights reference row · #15 of 48 on the API board · Capability #12

vs

Alternative

Winnow

EldanRing · Gemma 4 12B decision fine-tune

#39 of 235 open-weights systems, with typed decisions, chat and vision on a 16 GB GPU.

72.2JevBench v1.7.48 · #39 of 235 on the open-weights board · Capability #53

  1. JevHosted API, generally availableWhere it runsWinnowSelf-hosted GGUF; Q8 tested on a 16 GB RTX 5070 Ti
  2. JevTyped decisions onlyWhat it doesWinnowTyped decisions, chat and image input from one server
  3. Jev63.6 on JevBenchIntelligenceWinnow59.5 on JevBench
  4. Jev61.6Sealed decisionsWinnow59.2
  5. Jev77.4 above chanceChoice questionsWinnow70.1 above chance
  6. JevCalibrated — 90.6 on JevBenchProbabilitiesWinnowNormalised logits, no fitted calibration — 83.0

Try it on this page

Run Jev 1.14 right here

Edit the example or paste your own text, then run it. Sign in to run: new accounts get 20 welcome credits, and a failed run costs nothing.

Open the full playground

Support ticket triage · Jev 1.14

1 Input

Hi, this is the third time I am writing. Our payouts have failed every day since Monday and my team cannot pay suppliers. I already re-entered the bank details twice. If this is not fixed today we will have to move to another provider.

2 Questions

  • Choice Which team should handle this ticket?
  • Yes / No Does the customer need a response today?
  • Score How frustrated is the customer?
  • Yes / No Does the customer threaten to leave or switch providers?

JevBench v1.7.48, measured the same way

One benchmark measured every system under one method — it ranks 235 open-weights systems on one board and 48 hosted API offerings on another, with the same scores in both — so these bars are comparable with each other in a way that vendor-published figures are not. The full board and how to read it are on the JevBench results page.

Composite score

#2 H2O-Lightning-4B77.9
#21 Xor 26B-A4B74.0
#23 Arcbright Elf 1 31B74.0
#25 Quyet-1.0-Large73.8
API #11 Sage 1.3.073.7
#27 decider-12b v273.7
#32 decisio 31B73.2
#33 decider-12b v173.2
API #14 Mercury Decide72.2
#39 Winnow72.2
#45 deck-31B71.9
#46 Cygnet71.9
API #15 Jev71.4
#52 Jev-Omni71.0
#54 decisio v0.8.070.6
#62 torchcast-12b69.8
API #20 wity-169.0
#96 Plumb-4B50.4
#111 decider-4b43.1
#119 JevK5 v0.339.2
#133 Imajev-4B30.0
#136 Hopper27.7
#160 SemIf16.1
#227 Laya0.0

Plain numbers are ranks on the open-weights board; “API” marks a rank on the separate board for hosted API offerings. Jev, a hosted API, is ranked there, and appears on the open-weights board only as an unranked reference row, where its score falls between #49 and #50. The composite hides where systems actually differ, so the charts below break it apart. Benchmark Heaven’s headline Capability ranking, shown next to each score above, averages intelligence and calibration among Jev-class systems.

Capability, higher is better

IntelligenceHow often it picks the right answer, half from sealed decisions

Jev63.6
Winnow59.5

CalibrationWhether 0.8 really means about 80%

Jev90.6
Winnow83.0

SpeedMeasured response time

Jev91.2
Winnow86.2

Intelligence on open and sealed decisions

Open300 decisions from public sources

Jev65.6
Winnow59.8

Sealed1,200 private decisions nobody could tune for

Jev61.6
Winnow59.2

By request type, chance-corrected

ChoicePick one of the options

Jev77.4
Winnow70.1

NoulProbability that a statement is true

Jev50.3
Winnow51.5

ScorePlace the case on a graded scale

Jev63.2
Winnow57.0

The sealed half, highlighted, is where results cannot have been tuned: nobody outside the benchmark has seen those decisions. Request types are scored above chance, so 0 means guessing and a value below 0 means worse than guessing.

One thing these charts leave out: the composite score above also weighs a fourth axis, cost. We do not reproduce it here; the full table is at the source below.

Every system on the board

The capability scores are charted above; this is the ranking and the deployment detail behind them. Jev and Winnow are highlighted.

ModelRankScoreMeasured latencyRuns on
H2O-Lightning-4B v1.1 (H2O.ai, Qwen3.5-4B)#277.90.03s raw, 0.21s adjustedSelf-hosted GPU
Xor 26B-A4B (Juspay, Gemma 4 26B-A4B)#2174.00.06s raw, 0.27s adjustedSelf-hosted GPU
Arcbright Elf 1 31B#2374.00.06s raw, 0.27s adjustedSelf-hosted GPU
Quyet-1.0-Large (Chinh Nguyen, Gemma 4 31B decoder)#2573.80.12s raw, 0.39s adjustedSelf-hosted, H100
Sage 1.3.0 (Levanto Labs, hosted API)API #1173.70.17s median / 0.41s p95Hosted API
decider-12b v2 (Mapika, Gemma 4 12B)#2773.70.05s raw, 0.26s adjustedSelf-hosted, RTX PRO 6000
decisio v0.8.0 on Gemma 4 31B (Amin Roudaki, frozen base)#3273.20.05s raw, 0.24s adjustedSelf-hosted, H100
decider-12b v1 (Mapika, stock Gemma 4 12B)#3373.20.05s raw, 0.26s adjustedSelf-hosted, RTX PRO 6000
Mercury Decide (Inception, diffusion decision API)API #1472.20.34s median / 0.96s p95Hosted API
Winnow-12B Q8 (EldanRing, Gemma 4 12B)#3972.20.12s raw, 0.40s adjustedSelf-hosted, RTX 6000
deck-31B (krishna765, frozen Gemma 4 31B)#4571.90.13s raw, 0.41s adjustedSelf-hosted GPU
Cygnet (blockbrain, frozen Gemma 4 12B)#4671.90.04s raw, 0.24s adjustedSelf-hosted, RTX PRO 6000
Jev 1.13.0 (TypeSafe)API #1571.40.24s median / 0.31s p95Hosted API
Jev-Omni (akhilaaa3, Gemma 4 12B)#5271.00.16s raw, 0.47s adjustedSelf-hosted, RTX 6000
decisio v0.8.0 on Gemma 4 12B (Amin Roudaki, frozen base)#5470.60.12s raw, 0.38s adjustedSelf-hosted GPU
torchcast-decision-12b (Torchcast AI, Gemma 4 12B)#6269.80.04s raw, 0.24s adjustedSelf-hosted, H100
wity-1 (Wity, closed API, reasoning auto)API #2069.01.85s median / 7.97s p95Hosted API
Plumb-4B (crh225, JevK5 v0.2 + LoRA)#9650.40.02s raw, 0.19s adjustedSelf-hosted, H100
decider-4b v2 (Mapika, Qwen3.5-4B)#11143.10.03s raw, 0.21s adjustedSelf-hosted, RTX 5090
JevK5 v0.3 (allebee, Qwen3.5-4B)#11939.20.02s raw, 0.19s adjustedSelf-hosted, H100
Imajev-4B (Mohit Garg, Qwen3.5-4B LoRA)#13330.00.07s raw, 0.29s adjustedSelf-hosted, RTX 5090
Hopper (HopitAI, Qwen3.5-4B LoRA)#13627.70.06s raw, 0.26s adjustedSelf-hosted, RTX A6000
SemIf (Qwen3.5-4B)#16016.10.06s raw, 0.27s adjustedSelf-hosted, RTX 5090
Laya (ModernBERT-large)#2270.00.93s raw, 2.01s adjustedSelf-hosted, CPU

JevBench method v1.7 applies a 10-second limit per decision: a response taking longer than 10 seconds counts as wrong and contributes zero calibration for that item. Speed uses all decisions, including failures. Benchmark Heaven re-scored recorded per-decision times; it did not run every model again. Tokens, draws and raw outputs are unchanged. Since method v1.8.0 (29 October 2026), self-hosted open-weights rows are costed by GPU time on a monthly-rented RTX PRO 6000 with an efficient inference engine instead of base-model list prices; encoders, architectures outside the six calibrated Gemma/Qwen classes and rows without a verified token basis keep their old costs, and API costs and both caps are unchanged. Intelligence, calibration and latency did not move, but most open-weights cost scores rose, so their composites rose and the Jev-class pool grew. Four rows recorded on a loaded CPU host await re-measurement and remain unranked with their dated v1.6 values; five CPU rows were measured again on GPU and replaced in full. The official composite combines intelligence, calibration, speed and cost using the frozen scorer. Each full-set system answers 1,500 decisions, 300 open and 1,200 sealed; most hosted APIs use an equated 600-item set. Half of intelligence comes from sealed decisions. The open-weights and API boards compare the same measurements within separate hosting groups. Board v1.7.48 ranks 235 open-weights systems and 48 API offerings; an additional API result is preliminary and unranked. There are 110 newer ranked open-weights rows tagged with their draw. Jev 1.13.0 remains an unranked reference on the open-weights board and is ranked on the API board. Capability averages intelligence and calibration among systems inside caps frozen at twice Jev’s v1.5 reference: 217 open-weights systems and 33 APIs qualify. The caps do not track current Jev latency. Self-hosted latency uses an estimated 2× measured latency plus 0.15s; API times include the network. Scores and splits on this site use method v1.8 (v1.7 scoring with the v1.8 cost basis); historical v1.6, v1.5 and v1.4 results are not current standings.

Jev and Winnow feature by feature

AttributeJev 1.13.0Winnow
What it isHosted System One model from TypeSafe, version jev-1.13.0Gemma 4 12B with a merged LoRA fine-tune, released as GGUF
LicenceProprietary, hostedApache-2.0, with the Gemma 4 terms that apply to derivatives
Request formatPOST /v1/systemone/v1/systemone for decisions and /v1/chat/completions for chat, from one server
Question typesNoul, choice, score — many per call, answered in parallelNoul, choice, score — one branch per question over shared state
InputsText only: string, JSON object or arrayText, plus images with the optional vision projector
Context64k tokens per request65,536 positions tested with vision on a 16 GB GPU
CalibrationPost-trained with RLCD; JevBench 90.6Entropy-based confidence, no fitted calibration map; JevBench 83.0
Training dataUndisclosedPrivate; categories described in the model card
HardwareNone — it is an API callA 16 GB GPU for the Q8 build; the BF16 build needs more memory or offloading

What each one is better at

Where Jev wins

  • Calibration 90.6 against 83.0; Winnow’s confidence is documented as entropy-based rather than a probability of being right.
  • Intelligence 63.6 against 59.5, 61.6 against 59.2 on the sealed half, and ahead on choice and score questions.
  • Nothing to download, serve or tune: no 12.7 GB model file, no GPU scheduling between chat and decision contexts.
  • A hosted, versioned model with published rate limits.

Where Winnow wins

  • #39 of 235 open-weights systems in JevBench v1.7.48 at 72.2, and the strongest system on the board that also chats and reads images.
  • #53 on the Capability ranking at 71.2, and a better cost score than Jev, 67.0 against 54.7.
  • One model for typed decisions, chat and image input, served from the same process.
  • Runs locally on one 16 GB consumer GPU with a 64K context.
  • Apache-2.0 GGUF weights you can run offline or inside your own network.

The analysis

Where Jev and Winnow really differ, and why the bars above land where they do.

Winnow is the strongest system on the board that also chats and reads images, and in v1.5.6 it finished ahead of Jev. The full re-measure in v1.6 reversed that: it is #39 of 235 open-weights systems at 72.2, against 71.4 for Jev, which the board shows as an unranked reference, and its intelligence lead has gone — 59.5 against Jev’s 63.6, and 59.2 against 61.6 on the sealed half. Its small edge on the composite comes from the cost axis since Benchmark Heaven’s 29 October GPU-time cost basis, 67.0 against 54.7; on Capability, which leaves cost out, Jev’s reference score is well above it.

Jev keeps a wide edge on calibration, 90.6 against 83.0; Winnow’s own model card says its confidence is entropy-based and not a guaranteed probability of correctness. By request type Jev leads on choice, 77.4 against 70.1 above chance, and on score questions, 63.2 against 57.0, while Winnow edges it on yes/no, 51.5 against 50.3. Jev is also the faster of the two on the benchmark’s measure, 91.2 against 86.2. On Benchmark Heaven’s headline Capability ranking, which averages intelligence and calibration, Jev scores 77.1 and Winnow is #53 at 71.2.

Winnow’s case is breadth on your own hardware. The same loaded model serves /v1/systemone for decisions and /v1/chat/completions for chat, takes images through an optional vision projector, and was tested with a 64K context on a single consumer GPU. If you want one local model to decide, explain and look at a screenshot, nothing else on this site does all three.

What Winnow actually is

Winnow-12B, the Gemma 4 decision fine-tune from EldanRing, by EldanRing.

Winnow-12B is a LoRA fine-tune of google/gemma-4-12B-it, merged into the weights and released under Apache-2.0 as two GGUF files: an 8-bit Q8_0 build of about 12.7 GB, recommended for 16 GB GPUs, and a 16-bit BF16 build of about 23.8 GB. A separate 175 MB projector adds image input. It runs in the author’s llama.cpp-based inference server; no conversion step or separate adapter is needed.

For decisions, the server fills in the shared state once, forks one branch per question, and reads the logits of the answer tokens without generating any text, the same idea as Jev’s typed questions. It supports noul, choice and score. It states that it is not affiliated with or endorsed by TypeSafe.

The training data is private. The model card describes curated typed-decision examples covering routing, policy and rule application, evidence selection, workflow decisions, ordinal judgments, entailment, paraphrase and answerability, followed by a refinement pass. It makes no claim that public benchmarks were excluded from the base model’s pretraining data.

On the author’s RTX 5070 Ti test, a four-question request at near-full 64K context took 25 seconds cold and a median of 143ms once the context was cached, with peak GPU memory of 15.01 GiB including the desktop. JevBench v1.6.1 measured it on an RTX 6000 at a 0.12s median per decision before its self-hosting adjustment.

A second benchmark from the author

Winnow’s model card also reports a second suite, Kev-v9 clean, with 1,046 items, run by its author with Jev called through a hosted API aggregator on the same inputs and scoring rules. There Jev scores 87.00% against 81.55% for Winnow Q8. On the 231-item public JevBench subset the author reports a tie at 85.71%. These are the author’s measurements, not JevBench’s official composite.

So which should you use?

Pick Jev if

  • You branch on the probability and need it to mean something without fitting a calibration map yourself.
  • Accuracy and calibration matter most: Jev leads on both, and on every request type.
  • You want a hosted, versioned model with published rate limits rather than a GPU to operate.

Pick Winnow if

  • You want a single local model that decides, chats and reads screenshots or photos.
  • Your data cannot leave your network and you have a 16 GB GPU to spare.
  • You want strong decisions from weights you control, and can run the model yourself.

Try Jev on the cases you are actually arguing about

Winnow does more on one GPU than anything else on this site, so the useful comparison is on your own cases and your own constraints. Run them on Jev here with no setup and keep the answers; if Winnow agrees on the decisions you care about and you can run it, a local model that also chats and reads images may still be the better fit.

Jev vs Winnow FAQ

Is Winnow as accurate as Jev?

Not on the answers in JevBench v1.7.48: it is #39 of 235 open-weights systems at 72.2, a little above the 71.4 of Jev, shown there as an unranked reference, thanks to its cost score, but with intelligence 59.5 against 63.6 and 59.2 against 61.6 on the sealed half. It was ahead in v1.5.6, on the old pool. Jev is also better calibrated, 90.6 against 83.0.

Can Winnow read images?

Yes. With the optional 175 MB vision projector it accepts images through the same server. Jev accepts text only.

What GPU do I need for Winnow?

The author tested the 8-bit Q8_0 build, about 12.7 GB, with full offload on a 16 GB RTX 5070 Ti at a 64K context, peaking at 15.01 GiB. The 16-bit build is about 23.8 GB and needs more GPU memory or offloading.

Are Winnow’s probabilities calibrated?

Not in the way Jev’s are. Its model card says the server normalises logits over the options you supply and that its entropy-based confidence is not a guaranteed probability of correctness, with no separately fitted calibration map. JevBench v1.7.48 scores its calibration at 83.0 against Jev’s 90.6.

Is Winnow affiliated with TypeSafe?

No. It is an independent fine-tune of Gemma 4 12B by EldanRing, and its model card states it is not affiliated with or endorsed by TypeSafe or Google.

Other Jev comparisons

Every number on these pages is quoted from a published source and was read on October 31, 2026.

Sources

Winnow and every other product named on this page belongs to its respective owner and is not affiliated with Jev AI. Figures are quoted from the sources above as they read on October 31, 2026 and can change.