ReleaseOpen Weights · ActionableX: @vllm_project→ original

vLLM supports ERNIE 5.5 Flash Base from day one: 280B parameters, 14B active

Baidu has released the open weights for ERNIE 5.5 Flash Base, and vLLM supported the model on launch day. It is a 280-billion-parameter MoE, but only 14 billion parameters are active for each token. The context window reaches 1 million tokens for inference and fine-tuning. For teams that want to adapt the model to their own domain, this is a ready-made foundation with no need to wait for inference-engine support.

AI-processed from X: @vllm_project; edited by Hamidun News
vLLM supports ERNIE 5.5 Flash Base from day one: 280B parameters, 14B active
Source: X: @vllm_project. Collage: Hamidun News.
Listen to article
Article Fact Sheet & Key Figures
ParameterDetails
Primary sourceX: @vllm_project ↗
Editor-in-Chief
Key metric #1280B total parameters, 14B active per token
Key metric #2Pretrained on 33.5 trillion tokens, with a 128K context window
Key metric #3Open Base weights for fine-tuning and instruction tuning

It is a familiar story: a high-profile open model comes out, you eagerly download the weights, and then spend weeks waiting for an inference engine to learn how to run it properly. This time, things are different. Baidu released ERNIE 5.5 Flash Base, and vLLM announced day-zero support. You can pick it up and test it with your usual stack.

What we know about the model

Here are the figures from the announcement. The model has 280 billion parameters in total, but only 14 billion are active for each token. This is a Mixture of Experts architecture: at every step, only a small subset of the "experts" runs rather than the entire network. Pretraining covered 33.5 trillion tokens. The training context length was 128,000 tokens, while up to 1 million is claimed for fine-tuning and inference.

One detail in the name matters: this is a Base model, meaning a foundation model after pretraining, without careful training to follow instructions. Baidu released the weights specifically for domain adaptation and instruction tuning. It is a starting point, not a ready-made chatbot.

Why this matters in practice

Imagine that you are building an assistant for legal documents or an internal codebase. A general-purpose chat model has already been "raised" in someone else's style, and retraining it can sometimes be harder than starting with a clean foundation. Base weights provide a more neutral starting point: you define the response format, tone, and constraints yourself.

The MoE design is also useful. In terms of computation per token, the model is closer to 14B than 280B, although all the weights still have to be kept in memory. This is the classic MoE trade-off: generation speed and per-token cost are better than those of a similarly sized dense model, but VRAM requirements remain high.

Support in vLLM removes the most frustrating barrier. There is no need to write custom kernels or wait for a patched fork. You get a familiar OpenAI-compatible server, batching, and standard deployment methods. For a prototype, that can save days or even weeks.

What to keep in mind

First, the announcement includes no benchmarks, competitor comparisons, or licensing details. For now, these are only the stated specifications. Before building a product, check the terms of use and test the model on your own data.

Second, the 1-million-token context is presented as the limit for fine-tuning and inference, not as something the model reliably uses out of the box. You need to measure long-input quality yourself: many models formally accept huge contexts but lose details in the middle. The base training length here is 128K, which is a more honest reference point.

Third, 280B parameters will require serious hardware even with only 14B active. You will almost certainly need a multi-GPU deployment, quantization, and tensor parallelism. Fine-tuning a model of this size will cost even more, so consider adapters such as LoRA instead of full fine-tuning.

Practical takeaway

If you are building a product on open models and need a foundation for your own specialization, ERNIE 5.5 Flash Base deserves a place on your shortlist. Start small: launch it in vLLM, measure speed and memory use on your hardware, and then evaluate quality on two or three real-world tasks. If the base model handles your domain better than your current model, investing in instruction tuning will make sense.

Overall, this is another sign that the open ecosystem is maturing. Launch-day inference-engine support is becoming the norm, and model selection increasingly comes down not to "will it run?" but to "does its quality and license fit the use case?" That is what should be checked first.

Story

Key Questions Answered

What we know about the model?

Here are the figures from the announcement. The model has 280 billion parameters in total, but only 14 billion are active for each token. This is a Mixture of Experts architecture: at every step, only a small subset of the "experts" runs rather than the entire network. Pretraining covered 33.5 trillion tokens. The training context length was 128,000 tokens, while up to 1 million is claimed for fine-tuning and inference.

Why this matters in practice?

Imagine that you are building an assistant for legal documents or an internal codebase. A general-purpose chat model has already been "raised" in someone else's style, and retraining it can sometimes be harder than starting with a clean foundation. Base weights provide a more neutral starting point: you define the response format, tone, and constraints yourself. The MoE design is also useful.

What to keep in mind?

First, the announcement includes no benchmarks, competitor comparisons, or licensing details. For now, these are only the stated specifications. Before building a product, check the terms of use and test the model on your own data. Second, the 1-million-token context is presented as the limit for fine-tuning and inference, not as something the model reliably uses out of the box. You need to measure long-input quality yourself: many models formally accept huge contexts but lose details in the middle.

ZK
Zhemal Khamidun — CPO at Alpina Digital, product manager of AlpinaGPT. Building AI products since 2019. Hamidun News is a pet project that grew into a production aggregator with 6,000+ readers.
✦ Unified AI Workspace · Nomad

Test Frontier LLMs & Autonomous Agents in One Workspace

Run Claude Opus 5.5, GPT-6, Gemini 3.1, and DeepSeek side-by-side in Nomad AI (nomadnet.ai) — unified model routing, deep research, and multimodal workflows under one subscription.

Try Nomad AI →Launch Nomad Agent
What do you think?
Loading comments…