Clef-omni adds audio/video input; Clef-flash now cheaper than Jev

Small teams can test a single multimodal model instead of stitching separate audio/video/text tools, and may lower model spend if Clef‑flash replaces Jev — but Cloudflare hasn't published exact prices.

What actually changed

Cloudflare added a new model, Clef‑omni, that accepts audio, video, image and text inputs. The blog post presents this as an expansion of their existing Clef family and follows last week’s launches of Clef and Clef‑flash. The company also reports that the base Clef model has been made faster, and that Clef‑flash’s price has been reduced so it is now cheaper than Jev. The announcement describes the Clef family as "open-weight decision models," signalling the weights are publicly available for community use.

Who it affects

• Small agencies and product teams that process multiple input types (audio, video, images, text) can try a single model instead of combining specialised pipelines.
• Teams that currently pay for Jev or similar models should re-evaluate unit costs, because Clef‑flash is now positioned below Jev on price according to the announcement.
• Developers and researchers who rely on open model weights gain access to another openly released option for experimentation and deployment.

What it costs or what it replaces

The announcement states that Clef‑flash is now cheaper than Jev, but it does not publish specific prices or billing terms. Because the Clef family accepts multiple modalities, Clef‑omni can replace setups that route audio and video through separate services into a text or image model for downstream decisions, potentially reducing integration and inference overhead. Clef and Clef‑flash are presented as alternatives to the newly referenced Jev model on price and as additional open‑weight options for teams that prefer community‑accessible models.

What we don't know

• The announcement does not state exact prices, billing units, or quota limits for Clef‑omni, Clef or Clef‑flash.
• Performance benchmarks versus Jev or other commercially hosted models are not provided for accuracy, latency or cost per inference.
• Licensing or usage restrictions attached to the "open‑weight" release are not detailed in the post.
• Supported deployment options (Cloudflare integration, self‑hosting requirements, or managed endpoints) are not specified.

What to do next

1. Run a rapid pilot: request access to Clef‑omni and Clef‑flash, run representative multimodal workloads and measure latency, accuracy and end‑to‑end engineering effort against your current pipeline. Focus on the exact inputs you rely on (audio codecs, video resolution, image formats).
2. Recheck commercial terms: ask Cloudflare for billing details and quotas for Clef‑flash and Clef‑omni before migrating anything that affects production costs; the announcement does not include prices.
3. Validate licence and deployment: confirm the weight licence and deployment routes (self‑host vs Cloudflare managed) so legal and ops teams can assess risk before replacing existing models.