Jev AI

Jev comparison · JevBench v1.6.1 · updated October 9, 2026

Jev vs OpenJev

One name, ten projects. Here is every one, and how the drop-in compares.

On this site

Jev 1.13.0

TypeSafe · System One model

The original, and the model every project on this page is rebuilding.

71.5JevBench v1.6.1 rank #5 · Capability #5

vs

Alternative

OpenJev

razorback16 / Codiv · Jev-compatible server on DiffusionGemma 26B-A4B

Built as a drop-in for TypeSafe’s SDKs, and it can read images.

Not measured in JevBench v1.6.1

  1. JevHosted API, generally availableWhere it runsOpenJevSelf-host on a 24GB GPU or Apple silicon, or use Codiv’s hosted endpoint
  2. JevThe original /v1/systemoneRequest formatOpenJevWire-compatible — TypeSafe’s own SDKs work against it unchanged
  3. JevText onlySupported inputsOpenJevText, plus up to 8 images per request
  4. JevUp to 255Options per choiceOpenJevUp to 128
  5. JevCalibrated — 90.6 on JevBenchProbabilitiesOpenJevConfidence derived from output entropy, with no published calibration check
  6. JevNo thinking modeIn thinking modeOpenJevIntelligence 70.3 in JevBench v1.6.1, above Jev’s 63.6
  7. JevYes, #5 of 135Measured in JevBench v1.6.1OpenJevOnly in thinking mode, #75

Which openJev do you mean?

Every project below has been called openJev or Open-Jev by its author or by someone writing about it. They share a name and an idea, and nothing else — different base models, different sizes, different licences, different quality. Find the one you actually meant before you compare anything.

  1. OpenJevby razorback16 / Codiv

    Jev-compatible decision server on DiffusionGemma 26B-A4B (NVFP4, ~18GB). Accepts jev-latest, so TypeSafe SDKs work unchanged. Reads images. Hosted by Codiv, or self-host on a 24GB GPU or Apple silicon.

    Default not measured · #75 of 135 at 17.3 in thinking mode

  2. openjev-sglangby ekzhang

    Qwen3.6-35B-A3B served on SGLang, also implementing the /v1/systemone wire format. Its documentation states that its probabilities are not calibrated estimates of correctness.

    Not measured in JevBench v1.6.1

  3. Open-Jev 9B and 2Bby Zefan Cai

    LoRA adapters plus a trained scalar decision head and calibration temperature over a Qwen backbone. Not merged checkpoints — they need the pinned upstream weights and the Open-Jev loader.

    #76 at 17.0 and #99 at 3.2

  4. openJev Verdictby heman10x

    A 151M ModernBERT-base encoder with a GLiClass head, post-trained with RLCD and temperature-calibrated. Near-perfect on the data it was fitted to, weak on anything else. Runs on CPU or in a browser tab.

    #115 at 0.2 (version 1.4) and #120 at 0.1

  5. open-jev-deberta-v3-largeby Kotoba Labs

    A DeBERTa-v3 encoder run as a local CPU decision model.

    #124 of 135 at 0.0

  6. SemIfby TheoLeeCJ

    Was called OpenJev until it was renamed. Reads typed option logits out of a frozen Qwen3.5-4B. Old benchmark tables and blog posts still use the old name, which is where much of the confusion comes from.

    #80 of 135 at 15.5 — see the Jev vs SemIf page

  7. OpenSourceJevby sabeel111

    A Qwen3.5-4B rebuild quantised to Q4_K_M and served with llama.cpp. MIT code over Apache-2.0 weights.

    #87 of 135 at 10.3

  8. Open Jev JSON Canvasby JoshuaSP

    DiffusionGemma 26B-A4B filling a JSON answer canvas in one denoising step. It returns a label rather than a probability distribution, so it has no calibration score.

    #135 of 135 at 0.0 — intelligence 61.2, but it returns labels without probabilities, so calibration counts as zero

  9. OpenJevby zhangcy122

    A separate typed decision API over open LLMs using constrained logprob calibration. Same name as razorback16’s, unrelated codebase.

    Not in JevBench v1.6.1

  10. open-jev-typed-decision-engineby eightman999

    A 150M typed decision engine that trains on a Colab T4 in about 30 minutes. The author reports 0.697 against Jev’s 0.727 on their own set.

    Not in JevBench v1.6.1

  11. open-alternative-jevby IkerMoel

    Not an openJev, but constantly mistaken for one: a Qwen3.5-4B rebuild with a similar name and a similar goal.

    #88 of 135 at 9.4

  12. Open Spark Jev (spark-s1)by abhishek085

    Not an openJev either, though the name is close: local Qwen3.5-4B decision models built for NVIDIA DGX Spark, Apache-2.0. The measured model is spark-s1-4b-v6.

    #33 of 135 at 44.9

  13. verdict-smallby Manavarya09

    Unrelated to openJev Verdict despite the name: a 118M multilingual bi-encoder that scores each option by cosine similarity, runs on CPU and speaks the /v1/systemone wire format.

    #125 of 135 at 0.0

JevBench v1.6.1, measured the same way

One benchmark measured all 173 systems under one method and ranked 135, 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

#1 Sage 1.3.074.0
#2 H2O-Lightning-4B72.5
#3 Mercury Decide72.4
#4 decisio 31B71.7
#5 Jev71.5
#6 Quyet-1.0-Large71.4
#7 decider-12b v270.9
#8 wity-170.8
#9 decider-12b v170.4
#10 torchcast-12b69.9
#11 Winnow68.9
#12 deck-31B68.7
#13 Cygnet68.6
#14 decisio v0.8.068.2
#16 Jev-Omni67.7
#17 Xor 26B-A4B67.4
#30 Plumb-4B48.3
#39 decider-4b41.2
#41 JevK5 v0.337.4
#52 Hopper28.9
#53 Imajev-4B28.7
#80 SemIf15.5
#127 Laya0.0

The top four ranked systems finish within 2.3 points of each other. 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.

OpenJev was not measured in JevBench v1.6.1, so there is nothing to chart against Jev here. The analysis below uses the figures its authors publish.

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 OpenJev are highlighted.

ModelRankScoreMeasured latencyRuns on
Sage 1.3.0 (Levanto Labs, hosted API)#174.00.15s median / 0.29s p95Hosted API
H2O-Lightning-4B v1.1 (H2O.ai, Qwen3.5-4B)#272.50.03s raw, 0.21s adjustedSelf-hosted GPU
Mercury Decide (Inception, diffusion decision API)#372.40.33s median / 0.85s p95Hosted API
decisio v0.8.0 on Gemma 4 31B (Amin Roudaki, frozen base)#471.70.05s raw, 0.24s adjustedSelf-hosted, H100
Jev 1.13.0 (TypeSafe)#571.50.24s median / 0.30s p95Hosted API
Quyet-1.0-Large (Chinh Nguyen, Gemma 4 31B decoder)#671.40.12s raw, 0.38s adjustedSelf-hosted, H100
decider-12b v2 (Mapika, Gemma 4 12B)#770.90.05s raw, 0.26s adjustedSelf-hosted, RTX PRO 6000
wity-1 (Wity, closed API, reasoning auto)#870.81.57s median / 4.21s p95Hosted API
decider-12b v1 (Mapika, stock Gemma 4 12B)#970.40.05s raw, 0.26s adjustedSelf-hosted, RTX PRO 6000
torchcast-decision-12b (Torchcast AI, Gemma 4 12B)#1069.90.04s raw, 0.22s adjustedSelf-hosted, H100
Winnow-12B Q8 (EldanRing, Gemma 4 12B)#1168.90.12s raw, 0.38s adjustedSelf-hosted, RTX 6000
deck-31B (krishna765, frozen Gemma 4 31B)#1268.70.13s raw, 0.40s adjustedSelf-hosted GPU
Cygnet (blockbrain, frozen Gemma 4 12B)#1368.60.04s raw, 0.22s adjustedSelf-hosted, RTX PRO 6000
decisio v0.8.0 on Gemma 4 12B (Amin Roudaki, frozen base)#1468.20.10s raw, 0.35s adjustedSelf-hosted GPU
Jev-Omni (akhilaaa3, Gemma 4 12B)#1667.70.15s raw, 0.46s adjustedSelf-hosted, RTX 6000
Xor 26B-A4B (Juspay, Gemma 4 26B-A4B)#1767.40.06s raw, 0.27s adjustedSelf-hosted GPU
Plumb-4B (crh225, JevK5 v0.2 + LoRA)#3048.30.02s raw, 0.19s adjustedSelf-hosted, H100
decider-4b v2 (Mapika, Qwen3.5-4B)#3941.20.02s raw, 0.20s adjustedSelf-hosted, RTX 5090
JevK5 v0.3 (allebee, Qwen3.5-4B)#4137.40.02s raw, 0.19s adjustedSelf-hosted, H100
Hopper (HopitAI, Qwen3.5-4B LoRA)#5228.90.06s raw, 0.26s adjustedSelf-hosted, RTX A6000
Imajev-4B (Mohit Garg, Qwen3.5-4B LoRA)#5328.70.07s raw, 0.29s adjustedSelf-hosted, RTX 5090
SemIf (Qwen3.5-4B)#8015.50.05s raw, 0.25s adjustedSelf-hosted, RTX 5090
Laya (ModernBERT-large)#1270.00.83s raw, 1.80s adjustedSelf-hosted, CPU

JevBench v1.6 is a full re-measure on a new decision pool, not an update of v1.5. Every system answers 1,500 decisions: 300 open decisions from public sources and 1,200 sealed decisions whose text stays private, one request at a time. v1.6.1 put the hosted APIs on that same full set instead of the 600-item subset v1.6.0 gave them, so their accuracy axes are no longer equated onto the self-hosted scale. The official score is a harmonic mean of four equally weighted axes (intelligence, calibration, speed and cost), so one weak axis pulls it down hard; an axis below chance counts as zero, which zeroes the score. The sealed decisions make up half of intelligence, and a system whose open-minus-sealed gap exceeds the field median loses intelligence in proportion. Choice, noul and score requests carry equal weight. v1.6.1 also prices every token-priced system on one common item set — all 1,500 decisions except the 23 that fall outside Jev’s accepted input range — so a system that answered those long items no longer pays for their tokens while one that refused them does not. Refusals still count against intelligence. Benchmark Heaven also leads its page with a Capability ranking: the mean of intelligence and calibration among Jev-class systems, those inside a budget frozen at twice Jev’s v1.5 cost and median latency. v1.6.1 lists 173 systems and ranks 135; the rest were not re-measured, and 13 of them keep a separately dated v1.5.x score. Self-hosted latency is adjusted by x2 plus 0.15s to approximate production load, so it is not comparable with the raw latency authors publish. Scores are not comparable with any v1.5 or v1.4 release.

Jev and OpenJev feature by feature

AttributeJev 1.13.0OpenJev
What it isHosted System One model from TypeSafe, version jev-1.13.0Self-hosted decision server on DiffusionGemma 26B-A4B-it, NVFP4
LicenceProprietary, hostedApache-2.0, weights from NVIDIA and Google, about 18GB
Request formatPOST /v1/systemoneThe same, deliberately: accepts openjev-latest, jev-latest and jev-preview
Question typesNoul, choice, score — many per call, answered in parallelNoul, choice up to 128 options, score over 2–10 ranked levels
InputsText only: string, JSON object or arrayText, plus up to 8 images per request
Off-schema answersTyped answers onlyStructurally impossible — the model never writes the answer slots
Uncertainty handlingCalibrated probability per answerRe-reads up to 4 times with fresh noise above 0.1 entropy, then averages
HardwareNone — it is an API call24GB NVIDIA GPU under vLLM, or Apple silicon with 16GB free under MLX

What each one is better at

Where Jev wins

  • Calibration: Jev scores 90.6 in JevBench v1.6.1 against the thinking build’s 81.4, while OpenJev derives confidence from output entropy and publishes no independent calibration check.
  • Measured and ranked #5 in JevBench v1.6.1; OpenJev’s default configuration was not measured.
  • Up to 255 options per choice against 128, and no incompatibility between images and reasoning, because there are no images.
  • Nothing to run: no 24GB GPU, no vLLM, no quantised 18GB checkpoint to keep serving.
  • One configuration to reason about. OpenJev\u2019s accuracy, cost and latency all move with denoising steps, sample count and thinking budget.

Where OpenJev wins

  • A true drop-in: the same wire format and model aliases, so TypeSafe\u2019s SDKs point at it with a URL change and nothing else.
  • Reads images \u2014 up to eight per request. Jev is text only.
  • In thinking mode it beats Jev on intelligence in JevBench v1.6.1, 70.3 against 63.6.
  • Off-schema answers are structurally impossible, because the model reads the answer slots rather than writing them.
  • Apache-2.0, self-hostable on one 24GB GPU or an Apple silicon machine, and also hosted by Codiv.

The analysis

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

Of everything called openJev, razorback16’s is the one built to replace Jev directly. It is a genuine drop-in: it answers on the /v1/systemone wire format and accepts the model name jev-latest, so TypeSafe’s own SDKs work against it without a code change. JevBench v1.6.1 still does not measure its default configuration; the last release that did put it well below Jev on intelligence and calibration.

Its thinking mode was measured, and on the answers it beats Jev: intelligence 70.3 against 63.6, though calibration is 81.4 against Jev’s 90.6. It ranks only #75 of 135 at 17.3 because thinking needs far more compute per decision: its cost score is 28.5 and its speed 72.6, and the harmonic mean punishes weak axes hard. If accuracy on genuinely ambiguous inputs is what you are buying, that configuration is more accurate than Jev and you should know it.

What razorback16’s OpenJev actually is

OpenJev, the Jev-compatible decision server on DiffusionGemma, by razorback16 / Codiv.

It runs DiffusionGemma 26B-A4B-it, quantised to NVFP4, about 18GB of weights, under an Apache-2.0 licence from NVIDIA and Google. A diffusion model denoises many tokens at once rather than writing them one after another, and OpenJev turns that into a decision engine: it builds a masked canvas in which only the answer slots are uncertain, then takes one read-only forward pass and reads the probability distribution over the label tokens.

The model never writes into those slots, which is a real structural guarantee rather than a prompt instruction — an answer cannot go off-schema. When the distribution is too uncertain, above 0.1 entropy, it re-reads up to four times with fresh noise and averages the results.

It supports the same three primitives as Jev: noul, choice with up to 128 options, and score over 2 to 10 ranked levels with an expected value. It adds things Jev does not have: up to eight images per request, a tunable 1–8 denoising steps, 1–32 samples per read, and a thinking budget of up to 4,096 tokens.

On hardware, vLLM on a 24GB NVIDIA GPU handles up to 64 in-flight reads at about 94ms p50 at concurrency 1; the MLX backend runs on Apple silicon with 16GB free at 0.2–0.4s on an M3 Ultra, one read at a time. Codiv also hosts it at api.codiv.ai/v1/systemone.

Where its confidence number comes from

OpenJev computes confidence as 1 − H(p)/ln K: one when the model is certain, zero when the distribution is flat. That is a measure of how concentrated the answer is, not a measure of how often it is right. The documentation publishes no independent calibration check, and the last JevBench release to measure it, v1.4.2.2, scored its calibration well below Jev’s.

The practical consequence is the same as with every uncalibrated system on this site: a high number tells you the model was not torn between options, which is not the same as telling you it was correct. Validate the threshold on your own labelled data before you let it auto-approve anything.

The author is straightforward about the rest, too: answer quality is the quality of DiffusionGemma 26B-A4B used this way, choices cap at 128 against Jev’s 255, images cannot be combined with thinking mode, and the Apple silicon backend does not return reasoning content separately.

openJev Verdict: the cautionary one

Verdict is the openJev most likely to mislead you, because its published numbers are excellent and completely honest at the same time. On its own held-out set of 1,000 examples it reports 95.00% top-1 accuracy, a Brier score of 0.0756 and an expected calibration error of 1.13%. In-domain on Banking77 it reaches 95.2%.

On data it was not fitted to, it collapses. Its own author measures 48.07% on TypeSafe’s 337-case benchmark against 90.80% for Jev, and in JevBench v1.6.1 both Verdict builds answer the sealed decisions barely above chance, so their intelligence axis is near zero and they rank #115 and #120 of 135. Version 1.3.0 of the benchmark, which began measuring intelligence above chance and penalising anything below 50, had already dropped it from #4 to #36 without the model changing at all.

That is not dishonesty and it is barely even a flaw — it is what a 151M encoder is. Verdict was trained on contexts under 71 tokens and runs a 512-token budget with at most 25 candidates. Its README is unusually candid about the failure modes: abstention recall falls from 75.5% to 18.0% against hard-negative siblings, accuracy from 96.0% to 84.75% when distractors are confusable rather than random, and reordering the options flips 4.5% of choices. Fit it to your distribution and it is excellent. Point it at open-ended production text and you get the numbers above.

So which should you use?

Pick Jev if

  • You branch on the probability and want it to mean something without fitting it yourself first.
  • You would rather not operate a 26B diffusion model, or tune denoising steps and sample counts to trade accuracy against latency.
  • Your inputs are text, and you want one stable configuration behind a version you can pin.

Pick OpenJev if

  • Your decision involves an image, or you want the option of a reasoning budget on the hard cases.
  • You already run GPUs, or the data cannot leave your network, and you want something TypeSafe’s SDKs already speak to.
  • You are willing to validate confidence thresholds on your own labelled data rather than trusting them out of the box.

Try Jev on the cases you are actually arguing about

Whichever openJev you landed on, the only comparison that settles it is on your own awkward cases. Running Jev here takes a minute with no setup, and the answers come back with the full probability distribution — which is exactly the thing most of the projects above tell you not to trust yet.

Jev vs OpenJev FAQ

Which project is the real openJev?

None of them is official, and there are at least ten. JevBench v1.6.1 ranks seven: razorback16’s DiffusionGemma server, in thinking mode only, is highest at #75; Zefan Cai’s Open-Jev 9B and 2B are #76 and #99; SemIf, which used to carry the name, is #80; OpenSourceJev is #87; heman10x’s Verdict builds are #115 and #120; Kotoba Labs’ DeBERTa build is #124; and JoshuaSP’s JSON canvas is #135. openjev-sglang, ranked in v1.5.6, was not measured on the v1.6 pool.

Can I point the TypeSafe SDK at OpenJev?

At razorback16’s, yes — it implements the /v1/systemone wire format and accepts jev-latest and jev-preview as model names, so changing the base URL is enough. openjev-sglang does the same, though JevBench did not measure it in v1.6.1. The others have their own interfaces.

Is OpenJev as accurate as Jev?

Its default configuration was not measured in JevBench v1.6.1; the last release that measured it put it well below Jev on intelligence and calibration. In thinking mode it is more accurate than Jev, 70.3 against 63.6 on intelligence, but it needs far more compute per decision and ranks #75.

Why did openJev Verdict fall from #4 to the bottom of the board?

The model did not change. JevBench v1.3.0 began measuring intelligence above chance, v1.4.0 added a sealed set, and v1.5.0 made the sealed half count for half of intelligence. Verdict barely clears chance on the sealed decisions, so its intelligence axis is near zero and in v1.6.1 it ranks #120 of 135 at 0.1. The earlier ranking had been rewarding a system that was small and fast but, on this task mix, not far enough above guessing.

What hardware does OpenJev need?

About 18GB of NVFP4 weights: a 24GB NVIDIA GPU under vLLM, which handles up to 64 in-flight reads at roughly 94ms p50, or Apple silicon with 16GB free under MLX at 0.2–0.4s per read on an M3 Ultra. Codiv also hosts it.

Other Jev comparisons

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

Sources

OpenJev 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 9, 2026 and can change.