Analyzing Jev, a new AI model

TypeSafe launched Jev, which it calls "the first System One model," claiming it is 193x faster and 444x cheaper than large language models and cannot hallucinate. Jev is a classification model in the BERT family rather than a generative LLM, answering specific questions such as spam detection with a Yes/No, a continuous score, or a discrete choice, and is available only through an API. TypeSafe has published no papers on the system, and the "no hallucination" claim means Jev cannot produce output outside its specified structure, not that its answers are always correct.

Analyzing Jev, a new AI model A new AI model called Jev https://typesafe.ai/blog/introducing-system-one-models-and-jev launched last week and went viral. It's not an LLM. It doesn't generate text or pictures, but could be very useful for a number of use cases. The creators call it “the first System One model”, tout its performance 193x faster, 444x cheaper and promise it can't hallucinate. So, what is it? How it probably works Behind the impressive marketing is a very interesting model. Jev is a close relative of LLMs like GPT, Claude, or DeepSeek, but is actually more similar to the BERT <https://en.wikipedia.org/wiki/BERT language model series of models, which are used for classification, not generation. If you've ever wondered why someone calls out a difference between “AI” and “GenAI”, that's the distinction they mean . TypeSafe https://typesafe.ai/ the creators of Jev haven't actually published any papers on the system, but here's a reasonable guess and simplification, just to give you a sense of how it works. Imagine going back to 2022. GPT-3, the best LLM at the time, can autocomplete text you give it some text as an input and it continues it . Then InstructGPT https://arxiv.org/abs/2203.02155 shows how to make the LLM follow instructions from the user. Following the ChatGPT launch, the advances pile up, with reasoning, reinforcement learning, agentic use cases, and all the modern tech tricks LLMs now employ. BERTs, meanwhile, are almost stuck in time. There's ModernBERT https://huggingface.co/blog/modernbert , which modernizes it a lot, but you still need to fine-tune your model for the specific task. This is annoying, cumbersome, and more expensive than just asking an LLM. But these classification models are still much faster and cheaper than LLMs for suitable tasks, once you go through the trouble of training them. Now imagine someone going, “ OK, how can we modernize BERTs with all the cool tech LLMs have been getting? Like using instructions in the input instead of having to re-train, making it really large, and using reinforcement learning? ” That's basically what Jev is not exactly right, but it's a good analogy . Since it only ingests the input and provides a few probabilities as output, it's much faster and cheaper than LLMs. Jev's model size is not publicly known, but even if it's 100x larger than ModernBERT, it'd still be a paltry 40B params next to the humongous 2T-5T LLMs. The authors also mention performance improvements due to not needing to generate text tokens and other workflow simplification, as well as the fact that they can evaluate the questions in parallel. The “System One” moniker is a clever marketing trick that means “it's not a reasoning model”. They borrow the term from Thinking, Fast and Slow https://en.wikipedia.org/wiki/Thinking, Fast and Slow , where System 1 means intuitive, fast, automatic thinking and System 2 means deliberate, slower, effortful reasoning. What about the hallucination claim? In the context of Jev, no hallucination means it can't generate output outside of the specified structure i.e. it's “type-safe” , but that doesn't mean it can't generate incorrect output. Using Jev This brings me to the usage part: you'd use Jev and other classification models like BERTs to answer very specific questions, like “is this email spam?”, and it can answer with a Yes/No, a score from a continuous domain, like 0.0-10.0 , or a choice from a few discrete possibilities classification . Interestingly, the questions are independent and evaluated in parallel, which helps with performance. It also means you can just batch all the questions/classifications for a given piece of data at once, instead of going step by step. Since Jev doesn't need to be fine-tuned, it's easy to use it via an API and in fact, it's the only way to use it – don't expect the weights . Here's one official example, in Python: python from typesafe sdk import Choice, Noul, Score, TypeSafeClient client = TypeSafeClient ticket = """ Hi, I've been trying to connect my Stripe account for 3 days and the integration keeps failing. I'm losing sales. Please help ASAP. """ response = client.system one state=ticket, questions={ "department": Choice instructions="Which team should handle this", criteria={ "billing": "Payment or subscription issues", "technical": "Bugs or integration problems", "sales": "Pricing or account questions", }, , "frustration": Score instructions="How frustrated the customer appears", criteria= "Calm, just stating facts", "Frustrated but civil", "Very angry, strong language", , , "is urgent": Noul instructions="The message conveys urgency or time-sensitivity", , }, print response.answers "department" .choice "technical" print response.answers "frustration" .score 1.0 print response.answers "is urgent" .noul 1.0 Here you describe the input i.e. the “state” of the system and ask a number of questions. The instructions on how to classify/decide are actually part of each question, not the input state. How about prompt injection? If this is not a quirk of the API but actually how the model was trained, with state and instructions being separate, this might mean Jev is much harder to prompt-inject. I tried a few times to convince the above example to route the query to a different department but was unsuccessful. While I might have had more success had I tried harder, it does seem like Jev is a bit more resilient to these kinds of attacks. The authors are coy about this aspect, saying the adversarial examples for Jev are different from those of LLMs so that they work even better together https://news.ycombinator.com/item?id=49718450 . Is it useful? Yes. If your use case is something that fits how Jev works, it could be much better than LLMs. Of course, if you already have a locally tuned BERT, the gains may not be much, if any – should be easy to test What I'm most excited about is the combination of technical excellence and marketing excellence that raised the profile for this type of AI system, which has fallen by the wayside compared to the hype and capabilities of LLMs. That led people to use them in cases where they really aren't the best fit. Jev and all the copycats that are sure to appear will bring a breath of fresh air and some extra breathing room to many orgs' wallets :