Benchmarks
More
OverviewBenchmaxxingCompareChartsCost vs CapabilityProviders per ModelProvider explorerGatewaysEU & SovereignJev-class modelsImage JevBenchAbout

JevBench by Benchmark Heaven · released v1.4.2.2

Jev vs JevK5: published benchmark comparison

A side-by-side view of Jev 1.13.0 and JevK5 v0.2.0 from the same hash-checked v1.4.2.2 aggregate. The overall score is a composite; compare the separate measures against your use case.

Four-radar comparison: Jev and JevK5

Four radars compare this fixed pair across the score axes, accuracy per tier, and accuracy by family on the hard tier and sealed set. Further out is better on every spoke.

  • A: Jev 1.13.0 — Jev (TypeSafe, closed) · Score 63.3 (#4)
  • B: JevK5 v0.2.0 — Jev rebuild · Score 62.0 (#5)

The four score axes

Radar: the four score axes, two systemsThe four score axes, Jev 1.13.0 vs JevK5 v0.2.0. Intelligence: 53.1 vs 48.9; Calibration: 76.3 vs 74.5; Speed: 83.3 vs 91.1; Cost: 52.0 vs 59.5.50100Intelligence53.1 · 48.9Calibration76.3 · 74.5Speed83.3 · 91.1Cost52.0 · 59.5
0–100, the values in the table. A label-only system has no calibration (counted as 0).

Accuracy per tier, incl. sealed

Radar: accuracy per tier, incl. sealed, two systemsAccuracy per tier, incl. sealed, Jev 1.13.0 vs JevK5 v0.2.0. Easy: 100% vs 100%; Standard: 99% vs 96%; Judge: 95% vs 95%; Hard: 74% vs 70%; Sealed: 37% vs 33%.50100Easy100% · 100%Standard99% · 96%Judge95% · 95%Hard74% · 70%Sealed37% · 33%
Share correct per tier; Sealed = the 308 private decisions, aggregate only.

Hard tier by family (v1.2 topics)

Radar: hard tier by family (v1.2 topics), two systemsHard tier by family (v1.2 topics), Jev 1.13.0 vs JevK5 v0.2.0. Adversarial: 100% vs 92%; Ambiguous: 79% vs 79%; Judge: 79% vs 82%; Long policy: 61% vs 50%; Multi-hop: 86% vs 77%; Probability: 80% vs 60%; Routing: 100% vs 100%; Temporal / numeric: 27% vs 37%; Trade-off: 92% vs 83%; Trap: 100% vs 100%.50100Adversarial100% · 92%Ambiguous79% · 79%Judge79% · 82%Long policy61% · 50%Multi-hop86% · 77%Probability80% · 60%Routing100% · 100%Temporal /numeric27% · 37%Trade-off92% · 83%Trap100% · 100%
Share correct within each family of the 220 v1.2 hard-tier decisions (public and held-out).

Sealed set by family

Radar: sealed set by family, two systemsSealed set by family, Jev 1.13.0 vs JevK5 v0.2.0. Ambiguous / abstain: 30% vs 43%; Judge: 34% vs 37%; Long policy: 28% vs 23%; Multi-hop: 45% vs 39%; Paraphrase: 64% vs 14%; Probability: 50% vs 39%; Safety judge: 38% vs 38%; Temporal / numeric: 29% vs 27%; Trade-off: 38% vs 23%; Trap / adversarial: 42% vs 58%.50100Ambiguous /abstain30% · 43%Judge34% · 37%Long policy28% · 23%Multi-hop45% · 39%Paraphrase64% · 14%Probability50% · 39%Safety judge38% · 38%Temporal /numeric29% · 27%Trade-off38% · 23%Trap /adversarial42% · 58%
Share correct within each sealed family — system-level aggregates; the items stay private.

Published values

Jev 1.13.0 (TypeSafe AI) has the higher published JevBench Score. The displayed score uses one decimal place; the comparison above uses the same published release.

All values as a table
MeasureJev 1.13.0 (TypeSafe AI)JevK5 v0.2.0
Published rank#4#5
JevBench Score63.362.0
Sealed-set accuracy36.7%33.1%
Intelligence axis53.148.9
Calibration axis76.374.5
Speed axis83.391.1
Cost axis52.059.5
Cost evidencemeasuredestimated
Cost per 1,000 decisions$0.040 per 1,000 decisions$0.022 per 1,000 decisions

Intelligence, Calibration, Speed and Cost — equal-weight harmonic mean, with generalization and Jev-class gates. Cost evidence is labeled per row. Speed is a benchmark axis; deployment latency depends on the endpoint and conditions.

Jev 1.13.0 (TypeSafe AI)

Marked closed in the published row. License note: proprietary API.

Published source

Measured on
production API (api.typesafe.ai)
Speed adjustment
none (production API)
Cost basis
public tariff x measured tokens (https://docs.typesafe.ai/models (output tokens not billed)) [corrected in v1.2.3: the price now averages each of the 314 v1.1 decisions once; see results/v1.2/cost-correction-v1.2.3.json] | public tariff x measured tokens (hard-tier run)

JevK5 v0.2.0

Unknown in the published row. License note: Apache-2.0 (code/adapter); Apache-2.0 (Qwen3.5-4B base).

Published source

Measured on
re-run on a throwaway RunPod pod with the original recipe; deviations in its manifest
Speed adjustment
See original v1.3 measurement
Cost basis
Reconstructed from the frozen v1.3 Cost axis; same speed/cost measurement, not a new price observation

Compare more JevBench pairs: Jev vs Imajev-4B · Jev vs Plumb-4B · Jev vs decider-4b v2 · Jev vs Cygnet · Jev vs Hopper · Jev vs Winnow-12B Q8 · Jev vs reflex 4B · Jev vs Laya

See Jev alternatives · Choose by use case

Frequently asked questions

What does JevBench show for Jev and JevK5?
In v1.4.2.2, Jev is rank 4 with a JevBench Score of 63.3; JevK5 v0.2.0 is rank 5 with a score of 62.0. The table shows their published axes and sealed-set accuracy separately.
Which system has higher sealed-set accuracy?
Jev 1.13.0 (TypeSafe AI) has the higher published sealed-set accuracy (36.7% versus 33.1%). This is separate from the composite JevBench Score.
Can I compare the cost values as actual bills?
Jev 1.13.0 (TypeSafe AI): measured at $0.040 per 1,000 decisions. JevK5 v0.2.0: estimated at $0.022 per 1,000 decisions. Estimated and announced bases are not measured charges; inspect the board’s full row disclosure.
Is JevK5 open source, and is Jev?
The published row lists JevK5 v0.2.0 with license note “Apache-2.0 (code/adapter); Apache-2.0 (Qwen3.5-4B base)”. Jev 1.13.0 is listed as “proprietary API”: TypeSafe AI serves it through its own API and has not published its weights. Check each linked source for the exact terms.