vLLM Releases d3-ultra: A 27B Open-Source Multimodal Decision Model

vLLM team releases d3-ultra, a 27B open-source multimodal decision model, scoring 87.2 on its in-house benchmark.
The vLLM Semantic Router team released d3-ultra, a 27B open-weight multimodal decision model that uses a discriminative scoring paradigm—reading text, images, and video in one pass and outputting probability scores for each candidate answer rather than generating text. It scored 87.2 on the team's in-house SR-Text benchmark, though evaluation details and baselines are undisclosed, limiting the score's reference value. Open weights facilitate private deployment and fine-tuning, fitting enterprise semantic routing scenarios. Before deployment, teams should verify video processing granularity, probability calibration quality, and integration with the vLLM inference stack. d3-ultra represents a new direction of multimodal capabilities serving decision-making rather than generation.
The vLLM Semantic Router team has released a 27B open-weight multimodal decision model called d3-ultra. Unlike conventional generative models, its purpose is "decision-making"—it reads text, images, and video in a single pass, then returns probability scores for each candidate answer. According to official disclosures, the model achieved a score of 87.2 on the team's in-house SR-Text benchmark.

Decision Models: A Different Path from Generative Models
The LLM race has long been dominated by the generative paradigm: given an input, output natural language token by token. d3-ultra takes another route—discriminative scoring. On the input side, it performs a single forward read; on the output side, it directly produces a probability distribution over each answer without generating explanatory text.
The engineering value of this design lies in determinism. Scenarios like routers, classifiers, and answer selection don't need "a passage that looks reasonable"—they need a comparable score and a stable ranking. Probability outputs are naturally suited for threshold judgments and load distribution, and are easier to embed into existing systems without introducing extra parsing costs.
Multimodality is another main thread of d3-ultra. Text, images, and video are processed uniformly within a single inference pass, meaning it can be directly used for cross-modal decision tasks such as determining "which model should handle this request" or "does this video content match a certain label"—without maintaining a separate pipeline for each modality.
The difference between discriminative scoring and the generative paradigm: Generative models (such as the GPT series) predict the next word token by token in an autoregressive manner, producing natural language sequences as output; discriminative models directly model the degree of match between an input and candidate answers, outputting a scalar score or probability. d3-ultra belongs to the latter, with a typical structure of an encoder (or fusion encoder) followed by a scoring head that independently computes a logit for each candidate answer, then applies softmax to obtain a probability distribution. This design avoids uncertainties in the generation process (such as sampling temperature, repetition penalty, etc.), and the output can be directly used for ranking and threshold judgments, making it more stable and efficient in tasks like routing, classification, and answer selection.
Unified multimodal inference: Traditional multimodal systems often design separate encoders and fusion logic for each modality, resulting in complex pipelines and compounded latency. d3-ultra claims to process text, images, and video uniformly in a single forward pass, which typically means using a unified tokenizer to map different modalities into a shared representation space (e.g., splitting images into patches, sampling video into frame sequences, then concatenating with text tokens), with the same Transformer backbone performing cross-attention computation. This "early fusion" strategy can capture fine-grained cross-modal interactions, but also places higher demands on input length and computational resources; in actual deployment, attention should be paid to video frame sampling strategies and context window limitations.
What 87.2 Means—and What It Doesn't
87.2 is the figure officially reported on the SR-Text benchmark. SR most likely stands for Semantic Router, i.e., the team's in-house evaluation set for routing scenarios. This score can indicate the model's basic usability on its target task, but it should also be viewed calmly.
There are often discrepancies in methodology between in-house evaluation sets and public benchmarks; details such as the difficulty distribution of the test set, the number of answer candidates, and whether ties are allowed can significantly affect absolute scores. The original text does not disclose the size, construction method, or comparison baselines of SR-Text, so 87.2 is better treated as a signal that "the team's internal acceptance passed" rather than a basis for horizontal comparison with other models. On the multimodal dimension, public quantitative results are also currently lacking.
Limitations of the in-house SR-Text benchmark: SR-Text is most likely a text evaluation set built by the Semantic Router team for routing scenarios, where the task format may involve given queries and several candidate answers (or routing targets), requiring the model to select the correct one. The advantage of an in-house evaluation set is that it closely matches the real business distribution, but it lacks the transparency of public benchmarks: the test set size, negative sample construction method, whether adversarial samples are included, and the number of answer candidates are all undisclosed, making the score difficult to reproduce or compare horizontally. In addition, the specific metric behind 87.2 (accuracy, AUC, or something else) is not specified, further limiting its reference value.
Open Weights and Their Fit with Routing Scenarios
With 27B parameters, the model sits in the upper-middle range among open-source models, balancing capability and deployment cost. Open weights allow teams to fine-tune, quantize, or run inference in private environments—crucial for enterprise routing scenarios, where request distribution logic is often tightly coupled with business data and closed-source APIs can hardly cover.
Judging from the naming, d3-ultra is a component under the vLLM Semantic Router project rather than a standalone foundation model. This suggests its usage is embedded in the semantic routing chain: it first determines the intent or modality attribution of a request, then decides which model or inference path to take next. The format of a single read with multi-answer scoring is precisely designed for such low-latency distribution.
Issues to Watch During Deployment
For teams planning to try it out, several issues need to be verified in advance. First, the actual processing granularity of video input—number of sampled frames, maximum duration, whether audio is supported—is not specified in the original text, directly affecting the scope of usability. Second, the calibration quality of probability scores: routing scenarios rely on stable thresholds, and uncalibrated softmax outputs tend to drift across different distributions. Third, the integration method with the vLLM inference stack, including whether batch processing and quantized deployment are supported.
Overall, d3-ultra represents a noteworthy direction: multimodal capabilities need not only serve generation but can also serve decision-making. It offers an open-source option in the niche routing scenario, but real-world effectiveness still requires independent validation on business data.
Probability calibration and threshold stability: Routing scenarios typically rely on probability scores for hard-threshold decisions (e.g., "if confidence is below 0.7, escalate to a human"), but softmax probabilities output by neural networks often suffer from overconfidence or underconfidence—i.e., poor calibration. An uncalibrated model's scores drift across different data distributions, potentially causing routing strategies to fail. In practice, post-calibration methods such as Temperature Scaling and Histogram Binning are needed, along with evaluation of Expected Calibration Error (ECE) on a validation set. The original d3-ultra text does not mention a calibration scheme, so this should be a key focus during trials.
Related articles

A New Paradigm for Text Editing in Compose: TextFieldState Replaces the Old API
Jetpack Compose introduces the TextFieldState API to fix dropped characters and cursor jumps from async input. The old value/onValueChange callbacks will be deprecated in 1.13. This article covers InputTransformation, OutputTransformation, four state hoisting patterns, and new formatted text editing capabilities.

Remote Compose: A New Document-Driven Paradigm for Cross-Platform UI on Android
Remote Compose transmits compact binary documents instead of screen pixels, enabling efficient UI rendering on remote surfaces like Wear OS and widgets. This article covers its document creation API, expression animations, size optimization techniques, and Wear OS progress.

How Crashlytics Eliminates Android Memory and Responsiveness Issues
Through the Chroma Clip case study, this article explains how Firebase Crashlytics uses Application Exit Info, Profiling Manager, GWP ASAN, and ARM MTE to pinpoint ANRs, OOMs, memory limit terminations, and native memory corruption—solving the challenge of stack traces that don't point to the real culprit.