There is no drop-in replacement for Jev. What exists splits three ways: open reproductions of its API built on frozen or fine-tuned open models, zero-shot classifiers and NER models that decide over labels you supply, and structured-output libraries that make any LLM return a typed answer. None of them is trained the way Jev is.
Jev alternatives at a glance
Jev is the first row, since it is what the rest are copying. Star counts were read from the GitHub API on 30 September 2026 and move daily. Every project below was published within a month of Jev's launch on 15 September 2026, so treat all of it as young code rather than as a settled field. For a verdict on the hosted and open options, read theJev alternatives guide.
Is Jev open source?
No. Jev is a closed model served from one hosted endpoint, and nothing about how it works has been released.
What is public: the HTTP API, the documentation, the SDKs, the prices and the jaggedness page listing the tasks the model is bad at. What is not public: the weights, the parameter count, the base architecture and the RLCD recipe. TypeSafe's docs describe Jev only as an endpoint, and say "the same weights serve every account," with behaviour shaped through the request rather than through per-account fine-tuning. The architecture guide collects the whole public record, which runs to five statements.
Can you run Jev locally?
No. There is no weight download, no self-hosted build and no announced VPC option as of 30 September 2026, so running a System One model on your own hardware means running a different model.
How much hardware that takes depends on how close to Jev you want to get. An encoder-sized classification model needs no GPU at all: OpenDecision pulls a 400M ModernBERT checkpoint from Hugging Face on first use, and Laya reports 193ms to 464ms per question on CPU against 32.8ms to 39.5ms on a Tesla T4. Apple Silicon covers the MLX projects, among them jevmlx, jev-visual and mini-jev, which wants about 8.5 GB of memory. Kev runs there too through MLX, and its 4B and 9B models fit a 32 GB Mac. A single consumer GPU runs SemIf on an RTX 3090, NanoJev on CUDA and CLM on Linux with an NVIDIA card. Only openjev-sglang asks for a datacenter card, since it serves a 35B model on SGLang and expects a B200.
Open-source reproductions of Jev's API
You send a state and a list of typed questions, and one forward pass comes back with a probability for every option you supplied. Several of them go further and speak TypeSafe's own wire format, so existing client code keeps working: openjev-sglang implements POST /v1/systemone along with /v1/models and /v1/limits, while Decider, litjev, Kev, CLM and Von serve the same schema, which means repointing TYPESAFE_BASE_URL is the whole migration.
What they do not reproduce is the training. RLCD has never been described in enough detail to copy, so a frozen Qwen reading its own option logits approximates the interface while the method stays out of reach. Most of the authors say as much in their own READMEs. openjev-sglang states that its probabilities "are not calibrated estimates of correctness," and jevfire that "relative label probabilities are not probabilities that an answer is correct." The nearest thing to a calibration claim comes from projects that fit temperature scaling afterwards: open-alternative-jev reports calibration error dropping from 5.4% to 2.1% on MMLU that way, and Laya from 0.466 to 0.081 on its English checkpoint. The RLCD guide covers what is actually known about the original method.
Zero-shot classifiers and NER models
A zero-shot classification model takes labels at request time, the same as Jev does, and it has been doing that for years. ModernBERT is the encoder underneath much of this, including Laya's English checkpoint and OpenDecision's NLI head, and it is the baseline Jev's cost and speed get measured against. OpenDecision names its three operations Choice, Noul and Score, which is Jev's vocabulary applied to natural-language criteria rather than to structured question objects.
GLiNER is the odd one out. It finds spans in text rather than deciding between options you supply, so it answers a different question and is only an alternative when what you wanted was extraction. For that job there is now also Clairic, Cloudflare's extraction model, which is a System One model but not a decision model, so it is not in this table. SetFit sits between the two, fitting a classifier from a few dozen labelled examples on CPU. For the detail, see Jev vs BERT, Jev vs GLiNER and the zero-shot classifier definition.
Structured-output libraries
Outlines, Instructor and DSPy already guarantee that an LLM cannot return a type error, which is one of the two things Jev sells. They do it by constraining or validating the output of a model you are already paying for, so the latency and the bill stay the underlying model's. They give you no probability you can threshold on, which is the other half. Structured outputs explains where the line falls, and is Jev just a classifier? asks whether the line is worth a new category.
How to choose
- You have code calling the Jev API and want it off TypeSafe. Point it at openjev-sglang or Decider and change the base URL. You lose the calibration claim, and you pick up a GPU bill.
- You want it on a laptop. jevmlx, jev-visual and mini-jev run on Apple Silicon today. Read the last commit date before you build on any of them.
- You want a hosted API that is not TypeSafe. Tev1 runs on Together's serverless API. It answers Choice questions only, with no Score or Noul.Kev-4B on OpenRouter answers all three at the same price as Jev.Solar Decide from Upstage, in beta, d1from Liquid AI and Mercury Decide from Inception also answer all three, as do Clef from Cloudflare, which runs on Workers AI, and pplx-decider from Perplexity. Clef, pplx-decider and Celeris-1 Decision from Celeris read images. Kai from Hanzo AI answers all three, text only, and so do Microsoft-Decision-1 on Microsoft Foundry and OpenRouter and Drex from Nace.AI. Cloudflare's Clef-omni also reads audio and video. Span-01 from Respan scores behaviors in agent traces instead.
- You want weights you can keep and retrain. Laya, Kev, CLM, Tev1, Cloudflare's Clef, Perplexity's pplx-decider, Liquid AI's open d1 models and NanoJev all ship theirs. Laya publishes benchmark and calibration numbers you can try to reproduce, and Kev ships its training code and the eval sets it compares against Jev.
- You already have labelled data. A fine-tuned encoder will be cheaper and probably more accurate on your own labels. Jev vs BERT works through when that flips.
FAQ
Is Jev open source?
No. Jev is served only as a hosted API, from TypeSafe AI directly or through OpenRouter. The weights, the parameter count, the architecture and the RLCD training recipe are all unpublished as of 30 September 2026, and there is no announced self-hosting path. What is public is the HTTP API, the documentation and the SDKs, which is what every alternative on this page was built against.
Can I run Jev locally?
No. There is no weight download and no self-hosted or VPC option, so running a System One model on your own hardware means running something else. The nearest options are the open reproductions: NanoJev and SemIf on a consumer GPU, mini-jev on Apple Silicon or CUDA with about 8.5 GB of memory, Kev on CUDA, ROCm or a 32 GB Mac, CLM on Linux with an NVIDIA GPU, and the encoder-sized models Laya and OpenDecision, which also run on CPU.
What is the closest open-source alternative to Jev?
That depends on which part you want. For the interface, ekzhang/openjev-sglang implements TypeSafe's POST /v1/systemone endpoints, and Decider and CLM serve the same wire format, so the TypeSafe SDKs work by repointing TYPESAFE_BASE_URL. For a model you can hold and retrain, Laya, Kev, CLM and NanoJev ship their own weights. For a hosted API from another vendor, Together AI serves Tev1, which answers Choice questions only, OpenRouter serves Kev-4B, which answers all three question types, and Upstage, Liquid AI, Inception, Cloudflare and Perplexity serve Solar Decide, d1, Mercury Decide, Clef and pplx-decider, which also answer all three. Laya publishes calibration error figures, and Kev publishes accuracy and Brier scores against Jev on shared eval sets, with its training code. Full comparison: Jev alternatives: hosted, open-source and local options compared.
Do any alternatives reproduce RLCD or calibration?
Not the training method. RLCD has never been described in enough detail to copy, so nothing here reproduces it. Several projects fit temperature scaling afterwards instead: Laya reports expected calibration error falling from 0.466 to 0.081 on its English checkpoint. Others disclaim calibration outright, and the Hugging Face Space named Qwen2.5-1B-RLCD documents no reinforcement learning at all.
Is Laya on OpenRouter?
No. A check of the OpenRouter models API on 30 September 2026 found no Laya and nothing from Convai Innovations, either among its 464 models or in its separate list of seven decision models, which holds Jev, Kev-4B, Solar Decide and Span-01. Laya is distributed as Apache-2.0 weights on Hugging Face and code on GitHub, and it is meant to be self-hosted. Community ports exist for Node.js and Rust.