Laya vs Jev: The Open-Source Answer to the Decision-Model Wave
Days after TypeSafe launched Jev, Convai Innovations shipped Laya: an Apache 2.0, 421M-parameter decision model claiming 33ms decisions across 100+ languages. How the two compare, honestly, including the fine-tuning caveat.

Laya vs Jev: The Open-Source Answer to the Decision-Model Wave
Last week the AI world met Jev, TypeSafe AI's non-chat "System One" model that returns typed decisions instead of prose. It took days for an open answer to appear: Laya, an Apache 2.0, open-weight decision model from Convai Innovations, a startup out of Kasaragod, Kerala, India. If Jev made the category interesting, Laya makes it accessible to everyone. Here is what it is, how the two compare, and what to watch out for.
What Laya is
Laya is a non-autoregressive decision model: it does not generate text at all. You hand it a piece of state (an email, a support ticket, an agent trace, a JSON object) plus typed questions with fixed answer sets, and it returns the chosen answers with calibrated probabilities in a single forward pass. No tokens, no prose, nothing to hallucinate, no JSON parsing failures.
The main English checkpoint is small by modern standards, roughly 421 million parameters on a ModernBERT-large backbone, which is exactly the point: it runs on modest local hardware, and a multilingual variant covers 100+ languages.
Laya vs Jev, honestly
| | Jev (TypeSafe AI) | Laya (Convai Innovations) |
|---|---|---|
| Access | Closed, hosted API | Apache 2.0 open weights, self-hostable |
| Latency (vendor-reported) | ~236-276 ms hosted | ~33 ms p50 on a single Tesla T4 |
| Cost | Per-call API pricing | $0 self-hosted |
| Languages | English-focused | 100+ |
| Out of the box | Tuned for decision tasks | Near-random until you fine-tune it |
Two big caveats keep this honest:
Why this category matters
Both models bet on the same idea, named after Kahneman's System 1: most production "AI" work is not open-ended writing, it is millions of fast, narrow decisions - is this fraud, which queue, does this violate policy, what is the next step. A tiny typed classifier answers those cheaper, faster and more reliably than a chat model asked to "respond only in JSON."
The emerging stack looks like this:
Which one should you try
Related Articles
- Laya vs. Jev: Die Open-Source-Antwort auf die Entscheidungsmodell-Welle
Sep 22, 2026 · 5 min read
- Laya contre Jev : La réponse open-source à la vague des modèles de décision
Sep 22, 2026 · 5 min read
- Laya vs Jev: La respuesta de código abierto a la ola de modelos de decisión
Sep 22, 2026 · 5 min read
- Laya vs Jev: 오픈소스로 답하는 의사결정 모델 물결
Sep 22, 2026 · 5 min read
- लाया बनाम जेव: निर्णय-मॉडल लहर का ओपन-सोर्स उत्तर
Sep 22, 2026 · 5 min read