Comparison · reviewed 2026-10-11
Jev vs Clef
Clef is Cloudflare's open-weight answer to Jev: the same state-plus-typed-questions request shape, downloadable under Apache 2.0 or callable serverless on Workers AI, with a 64k context and image input for a category whose origin model documents text-only input. On Cloudflare's own benchmark harness, Clef leads classification-style tasks (BANKING77 by ~14 points, tool routing, home appliances) and trails judgment-style ones (When2Call, retrieval, agent-trace evals) — at roughly 5.7× Jev's hosted input rate. Independent tests agree Clef matches Jev on easy picks but disagree on speed: one race measured Jev faster on every task. Pick by where the decision must run and which tasks you have, not by the scoreboard.
Clef and Clef-flash arrived on 1 October 2026, about two weeks after Jev opened the typed-decision category — and the family grew within days, with an audio-and-video variant, Clef-omni, reported on 9 October. Cloudflare describes the two originals as “fully Jev-API compatible”: same state, same noul / choice / score questions, probabilities back. The differences that decide are deployment shape, context, modalities, price, and whose benchmark numbers you believe.
The tables below are largely Cloudflare's own harness — the company chose the tasks and ran every model, including the Jev column. Where independent tests disagree with the launch numbers, both are reported, and the benchmark dispute between the two camps is laid out rather than settled. Nothing here is this site's own measurement.
Side by side
| Dimension | Jev (TypeSafe AI) | Clef (Cloudflare) |
|---|---|---|
| Released | 15 September 2026 (System One launch; Jev 1.13 is the build named in third-party tests) | 1 October 2026 (Clef and Clef-flash, launched during Cloudflare Birthday Week); Clef-omni audio/video variant reported 9 October 2026Clef shipped about two weeks after Jev. The omni variant followed within days and has no published audio or video benchmarks. |
| Who makes it | TypeSafe AI | Cloudflare — its first internally trained models, per launch coverage |
| Weights and license | Closed. Weights, architecture, and parameter count are not published | Open weights on Hugging Face under Apache 2.0 (Cloudflare/clef, Cloudflare/clef-flash, Cloudflare/clef-omni)Both are Apache 2.0 with no revenue threshold or user cap — but the training data and pipeline are unpublished, so “open” covers inspection and self-hosting, not replication. |
| How you run it | Hosted API only (the System One endpoint; also resold through gateways such as DigitalOcean Serverless Inference and OpenRouter). No self-hosting path. | Three ways: Workers AI serverless (@cf/cloudflare/clef and clef-flash), self-hosted weights (Clef-flash was tested on a single H200; Clef-omni needs roughly 64 GB of GPU memory in bfloat16), or community runners such as Ollama. |
| Model shape | Not disclosed. Vendor describes a non-autoregressive “parallel evaluation” of a candidate-answer space rather than token-by-token generation. | Post-trained from frozen backbones — Qwen3.8-27B (Clef), Qwen3.5-9B (Clef-flash), Qwen3-Omni-30B-A3B (Clef-omni) — with a routing head and rank-256 low-rank adapters optimized on top.The shared design idea: a decision is scored against a fixed answer space in one pass, so there is no generation step to parse or wait on. |
| API compatibility | Origin of the request shape: state plus typed questions (Choice, Score, Noul), returning per-option probabilities and confidence. | “Fully Jev-API compatible” with strictly typed outputs, per Cloudflare; same three question types (noul, choice, score — choice takes 2–255 options, score 2–10 levels).Swapping a model name is the advertised migration path — but field notes say test first: Workers AI requires a per-question instructions field that model cards call optional, and option IDs meaningfully affect behavior. |
| Context and input limits | A 64k-token total request limit with 32k reserved for state plus the longest question; requests over either limit are rejected (System One API docs). Cloudflare's launch post frames the contrast as 64k versus Jev's 32k. | A 65,536-token context on all three variants, framed by Cloudflare as twice the state budget Jev's docs allow.Long state is one of the genuine capability gaps; truncation behavior at the limit was flagged as only partly tested in field reviews — verify before feeding near-limit documents. |
| Modalities | Text and JSON-shaped state only — “does not accept image, audio, or video input” (System One API docs); no streaming. | Text plus up to 4 base64 images per request (PNG/JPEG/WebP) on Clef and Clef-flash; Clef-omni adds audio and video input, with video sampled at 2 frames per second.Media details differ between model cards and the hosted API schema — verify on your surface. No audio or video benchmark has been published, so the omni variant's multimodal accuracy is unquantified. |
| Latency, as published | Vendor range ~70–500ms end to end, many calls near ~100ms from the US West Coast. In Cloudflare's 43-benchmark harness: 524.1ms median, 536.0ms p95. | Cloudflare-measured medians: 209.3ms for Clef and 38.8ms for Clef-flash (p95 238.6ms / 122.4ms) — the ~2.5× headline versus Jev.Orderings flip across harnesses: an independent OpenRouter race found Jev faster on every task (Clef 1.7–2.4× slower, 3.4× on long inputs); a Japan-side hands-on measured Clef-flash ~166ms and Clef ~406ms round trips including network transit. None of these is like-for-like. |
| Cost | $0.042 per 1M input tokens, output free (vendor list price). | $0.24 per 1M input tokens for Clef and $0.09 for Clef-flash on Workers AI, output free — about 5.7× and 2.1× Jev's rate.A Hacker News cost model at ~300 tokens per decision put 1M decisions at ≈$12.6 on Jev versus ≈$72 on Clef; launch coverage called the price gap the first thing critics ran arithmetic on. Self-hosting trades the token bill for GPU time and operations you cost yourself. |
| Published accuracy — intent classification (BANKING77, 77 labels) | 79.74 macro-F1 | 94.20 (Clef) / 90.93 (Clef-flash) — same harnessBoth columns come from Cloudflare's launch measurements: it chose the tasks and ran every model, including Jev's. Discount every score in this block as vendor-measured. |
| Published accuracy — tool calling and out-of-scope routing | BFCL case exact 95.75; CLINC150+OOS macro-F1 89.27 — out-of-scope handling is a documented Jev strength. | BFCL 98.47 / 98.76 (Clef / Clef-flash); CLINC150+OOS 97.43 (Clef) but 66.77 (Clef-flash) — the fast model is a poor default when “none of the above” must be routable. |
| Published accuracy — judgment-style tasks | When2Call 80.97 accuracy — an 8.6-point lead; BRIGHT retrieval nDCG@10 47.52; agent-trace observability 71.6. | When2Call 72.37 / 65.58; BRIGHT 45.91 / 39.26; agent-trace 68.5 / 69.8.Third-party coverage summarized the whole table as: Clef wins routing, Jev wins judgment. |
| Published accuracy — reasoning benchmarks (secondary reporting) | GPQA Diamond 78.3; MMLU-Pro 82.7 | GPQA Diamond 48.0; MMLU-Pro 65.9Not in Cloudflare's launch table — carried by third-party coverage of further testing, shown here for completeness. |
| Workflow evals (four-workflow suite, Cloudflare-run) | Invoice processing 61.8 · customer service 76.0 · security incidents 61.7 · agent-trace observability 71.6 | Clef: 64.7 · 76.3 · 62.9 · 68.5; Clef-flash: 57.1 · 77.0 · 61.7 · 69.8 — Cloudflare reports winning three of the four workflows.Three of the four margins are 0.3–2.9 points; Jev's agent-trace win is the largest single margin at 3.1 points. |
| Calibration | Trained with RLCD (vendor materials); an independent race found a clear split — 0.99 confidence when right, 0.71 when wrong. | Brier loss plus RLCD training claimed (vendor materials); the same race found confidence nearly uninformative — 0.81 when right, 0.74 when wrong, and ~41% on a long task it answered correctly.The sharpest vendor-versus-field gap on this page. If you gate on confidence, measure calibration on your own data before trusting either model's number. |
| Fine-tuning and openness | No published fine-tuning path — weights are unavailable. | Cloudflare's new RL fine-tuning platform (forward-deployed engineers now, self-serve planned: AI Gateway captures traffic into a dataset, Containers sandbox rollouts, Trainer updates weights, redeploy on Workers AI). Self-hosted weights can also be fine-tuned locally.Cloudflare notes fine-tuning may trade general-purpose performance for domain accuracy — plan an evaluation before assuming gains. |
Pick Jev (TypeSafe AI) when
- →You do not want to operate model serving, GPUs, or an inference deployment of any kind.
- →Your decisions are judgment-flavored — should-I-act gates, retrieval ordering, agent-trace evaluation — where Jev holds the published leads.
- →Per-decision cost matters at volume: the published input rate is roughly a sixth of hosted Clef's, and the gap widens with state size.
- →Your inputs fit the budget: 32k of state plus the longest question, text-only, through a single vendor API.
Pick Clef (Cloudflare) when
- →Data residency or air-gapped operation: Apache-2.0 weights run inside your own perimeter, offline.
- →Your tasks are classification-shaped — intent mapping, tool-call routing, domain or content classification — where Clef posts its biggest numbers.
- →Your state is long (up to 64k) or includes images; audio and video go to Clef-omni.
- →You are on Cloudflare Workers already, or you want the RL fine-tuning toolchain on your own labels.
- →You need to inspect, modify, or self-serve the model artifact rather than call a vendor API.
How to read these numbers
This site does not run its own benchmarks. Where a figure comes from a vendor or from the project itself, the row or table entry says so.
- The accuracy and latency tables marked Cloudflare-run are just that: Cloudflare selected the tasks, ran all models including the Jev column, and reports that Clef currently leads the benchmark index it compares against, with a live demo. An independent run on a neutral harness has been publicly called for and, as of this review, is not published.
- Both camps are interested parties with opposing public positions. Community threads (a 614-point Hacker News discussion; r/LocalLLaMA) argued that public benchmarks are easy to game and that the Jev build tested may not be its strongest variant — Cloudflare has not responded. Jev's author dismisses benchmark-chasing outright (“benchmaxxed models”; the difference does not show up on benchmarks) and points to enterprise adoption instead — “a quarter of the Fortune 500” onboarded, as he claimed on 1 October.
- Latency orderings conflict across harnesses and should not be quoted without attribution: Cloudflare measured Clef ~2.5× faster than Jev; an independent OpenRouter race found Jev faster on every task; a Japan-side hands-on reported transit-inclusive numbers between the two. No controlled, like-for-like comparison is published.
- Compatibility claims are Cloudflare's (“fully Jev-API compatible”) and hold at the request-shape level in field tests, but surface details differ — required fields, option-ID handling, and end-of-state truncation on long input. Test schemas and score on your own labels before switching in either direction.
- Hosted-to-hosted pricing is the only clean cost comparison ($0.24 versus $0.042, output free on both). Self-hosting replaces the token bill with GPU time, electricity, and on-call you have to cost yourself; the launch price gap drew the loudest criticism of the release.
Frequently asked questions
What is Clef AI?
+
Clef is Cloudflare's family of open-weight decision models, released 1 October 2026: Clef (post-trained from Qwen3.8-27B), Clef-flash (Qwen3.5-9B), and the audio/video variant Clef-omni. Like Jev, they take a piece of state plus typed questions — noul, choice, score — and return constrained answers with probabilities instead of generated text. Cloudflare describes them as “fully Jev-API compatible”; the weights are Apache 2.0 on Hugging Face and the models are also callable serverless on Workers AI.
Is Clef a drop-in replacement for Jev?
+
At the request-shape level, largely yes — same state plus typed questions, same answer objects with probabilities, and compatibility was an explicit design goal. Operationally, no: Jev is a hosted call, while Clef is something you can also download and serve yourself. Field notes add migration cautions: Workers AI requires a per-question instructions field, option IDs influence results, and confidence thresholds should be re-baselined because the two models' calibration behaves differently.
Is Clef faster than Jev?
+
Depends on the harness — the published claims and independent tests point in opposite directions. Cloudflare's own measurements put Clef at 209.3ms and Clef-flash at 38.8ms median against Jev's 524.1ms (~2.5×). An independent race through OpenRouter found Jev fastest on every task, with Clef 1.7–3.4× slower. A Japan-side hands-on measured ~166ms for Clef-flash and ~406ms for Clef per round trip including network transit. The safe statement: Clef-flash is genuinely built for latency-critical paths; whether it beats Jev on your workload requires measuring your workload.
Is Clef cheaper than Jev?
+
No — on the hosted path it is the expensive side of this comparison: $0.24 per 1M input tokens for Clef and $0.09 for Clef-flash versus $0.042 for Jev, with output free on both sides (about 5.7× and 2.1×). A Hacker News cost model at ~300 tokens per decision put 1M decisions at ≈$12.6 on Jev versus ≈$72 on Clef. Self-hosting changes the ledger: you trade the token bill for GPU time and operations, which coverage argues is a residency-and-fine-tuning decision rather than a cost win at small volume.
Does Clef beat Jev on benchmarks?
+
On Cloudflare's own table it depends on the task shape: Clef leads classification-style benchmarks (BANKING77 by ~14 macro-F1 points, tool-call routing, home appliances, phishing detection) and the full model handles out-of-scope routing well; Jev leads judgment-style ones (When2Call by 8.6 points, retrieval, agent-trace observability) and reasoning benchmarks per secondary reporting. The table is vendor-run, the Jev author disputes the genre, and community threads dispute the build tested — discount every score accordingly and benchmark your own task.
Can I self-host Clef?
+
Yes. The weights are Apache 2.0 on Hugging Face, community runners such as Ollama list clef and clef-flash, and launch coverage describes Clef-flash running on a single H200. Clef-omni is heavier — roughly 64 GB of GPU memory in bfloat16 — and its model card listed SGLang support as coming soon. You own serving, updates, and evaluation when you go this route.
What is Clef-omni, and when should I use it?
+
Clef-omni is the third variant, reported on 9 October 2026: a mixture-of-experts decision model built on Qwen3-Omni-30B-A3B that accepts text, JSON, images, audio, and video (video sampled at 2 frames per second), under Apache 2.0. Use it when the evidence you are deciding on is itself audio or video — a call recording, a dashcam clip. Caveats: no audio or video benchmark has been published, and on text tasks it trades scores with the smaller dense model (worse hallucination-detection F1, better MMLU).
Sources
- Cloudflare — Introducing Clef: open-source decision models and a new RL fine-tuning platform ↗
- Cloudflare/clef on Hugging Face ↗
- Cloudflare/clef-flash on Hugging Face ↗
- Cloudflare/clef-omni on Hugging Face ↗
- Clef-omni model card summary and family comparison (explainx.ai) ↗
- Launch coverage: specs, pricing, and The Register's price comparison (Traictory) ↗
- Analysis: routing vs judgment, pricing math, criticism (THE D*AI*LY BRIEF) ↗
- Hands-on with Clef on Workers AI (DEV Community) ↗
- Independent race: Clef and Clef-flash vs Jev via OpenRouter (DEV Community) ↗
- Jev's author questions the benchmark framing (GIGAZINE) ↗
- System One API request limits and modalities (DigitalOcean docs) ↗
Reviewed 2026-10-11. Vendor- and project-reported figures are labelled as such; none were independently reproduced by this site.
Related pages
Jev vs Laya →
Jev (TypeSafe) and Laya (Convai Innovations) both answer typed Choice, Score and Noul questions instead of writing text. This page compares …
Decision models vs LLMs →
When a typed decision model (Jev, Laya) beats a general-purpose LLM with structured output — and when it does not. Compared on output shape,…
What is Jev AI? →
Primitives, published latency and pricing, and where the approach fits.