Hosting = where inference runs; company = where the provider or lab is registered.
EU hosting means the route's inference runs inside the EU: an EU region, AWS Bedrock's EU cross-region (geo) profiles, Azure's Europe Data Zone, or a provider whose entire public fleet is documented as EU-hosted, each checked per model against the provider's documentation. Global deployments do not count, and neither does an EU billing region, an EU company or an EU control plane on its own. One disclosed company-policy exception stays in, marked “EU equivalent”.
Data confidentialitywhat the provider may do with your prompts
More settings
Evidence requirements (benchmark evidence, priced provider, measured task tokens) sit above the table they apply to.
Applies to price views & model offers; benchmark evidence stays unfiltered.
JevBench by Benchmark Heaven · released v1.4.2
Jev vs decider-4b v2: published benchmark comparison
A side-by-side view of Jev 1.13.0 and decider-4b v2 (Mapika) from the same hash-checked v1.4.2 aggregate. The overall score is a composite; compare the separate measures against your use case.
Jev 1.13.0 out-reasons decider-4b v2 (Intelligence 53.1 vs 49.4) and is better calibrated; decider-4b v2 leads on speed and cost. JevBench weighs the four axes equally; sort by Intelligence for raw reasoning.
Four-radar comparison: Jev and decider-4b v2
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.
0–100, the values in the table. A label-only system has no calibration (counted as 0).
Accuracy per tier, incl. sealed
Share correct per tier; Sealed = the 308 private decisions, aggregate only.
Hard tier by family (v1.2 topics)
decider-4b v2 has no published v1.2 hard-tier family breakdown.
Share correct within each family of the 220 v1.2 hard-tier decisions (public and held-out).
Sealed set by family
Share correct within each sealed family — system-level aggregates; the items stay private.
Published values
decider-4b v2 (Mapika) 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
Measure
Jev 1.13.0 (TypeSafe AI)
decider-4b v2 (Mapika)
Published rank
#2
#1
JevBench Score
63.3
64.1
Sealed-set accuracy
36.7%
34.7%
Intelligence axis
53.1
49.4
Calibration axis
76.3
75.0
Speed axis
83.3
92.9
Cost axis
52.0
60.9
Cost evidence
measured
estimated
Cost per 1,000 decisions
$0.040 per 1,000 decisions
$0.020 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.
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)
RTX PRO 6000 (evaluator-owned Lium pod) · our evaluator-owned Lium GPU pod (RTX PRO 6000), offline read-only container, author's server on loopback
Speed adjustment
x2 + 0.15 s (assumption, not measured)
Cost basis
ESTIMATE: DeepInfra Qwen/Qwen3.5-4B list price $0.03/M input (4B dense size class, as decider-2b), read 2026-09-24; the server's own usage.input_tokens; nothing generated; estimated, not charged
What does JevBench show for Jev and decider-4b v2?
In v1.4.2, Jev is rank 2 with a JevBench Score of 63.3; decider-4b v2 (Mapika) is rank 1 with a score of 64.1. 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 34.7%). 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. decider-4b v2 (Mapika): estimated at $0.020 per 1,000 decisions. Estimated and announced bases are not measured charges; inspect the board’s full row disclosure.
Is decider-4b v2 open source, and is Jev?
The published row lists decider-4b v2 (Mapika) with license note “Apache-2.0 (package and weights)”. 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.