qwen3guard vs Cloudflare clef-flash
qwen3guard and Cloudflare clef-flash have no measured difference in accuracy, calibration or cost in our data yet.
| Spec | qwen3guard | Cloudflare clef-flash |
|---|---|---|
| Provider | ollaya-dev | Cloudflare |
| Decision Index score | — | 47.6 |
| Calibration error (ECE) | — | 0.025 |
| Median latency (p50) | — | 53 ms |
| Cost per 1,000 decisions | — | — |
| Parameters | — | 10B |
| Open weights | Yes | Yes |
| Question types | Choice (one of N options), Score (ordered rubric), Yes / no | Choice (one of N options), Score (ordered rubric), Yes / no |
| Mechanism | Decoder LM with a decision readout | Decoder LM with a decision readout |
| License | apache-2.0 | apache-2.0 |
FAQ
Is qwen3guard or Cloudflare clef-flash more accurate?
At least one of the two has no Jev Decision Index score yet, so their accuracy cannot be compared here.
Which is better calibrated, qwen3guard or Cloudflare clef-flash?
No calibration difference between qwen3guard and Cloudflare clef-flash is recorded yet.
Is qwen3guard or Cloudflare clef-flash cheaper per 1,000 decisions?
A hosted price is not recorded for both models; open-weight models cost the compute you run them on.
Cost per 1,000 decisions assumes 200 input tokens per decision. Pricing is indicative — confirm with the provider before production use. Highlighted values indicate the better figure for that row.