Supporting case
Reflection actually releases Beam’s weights, moving beyond its preview
What happened
On October 16, Reflection released its first model, Beam, for public download under Apache 2.0. The release includes versions stored at different numerical precision, documentation and integrations for several inference systems. Developers can possess the model, modify it and run it on infrastructure they choose, rather than obtain every response through Reflection’s service. The public repository and model card ↗ identify the checkpoint and licence; the compressed version ↗ is also listed.
Beam contains approximately 501 billion parameters, of which about 23 billion participate in processing each token. The smaller active number reduces computation; it does not make the entire model small enough for an ordinary laptop. Storage, memory, engineering and hosting costs remain substantial. Provider claims about performance and the breadth of partner availability have not been independently tested here. Different serving software is a choice of implementation, not proof that every listed partner has an operating endpoint.
This release supplies the missing ownership/deployment option.
November 3, 2026 — evidence update
An October 27 VulcanBench report tested Reflection Beam on 23 software-reconstruction tasks at five reasoning settings—115 runs through Reflection's API and Mirror CLI. It reports no fully solved tasks at the first three settings, four at extra-high and six at maximum effort. More reasoning generally improved functional performance, while increasing time and token use. Two other models judged code quality; hidden tests measured behavior. These are this evaluator's results, not a representative survey of production work.
Crucially, this was not a self-hosted deployment test. It supplies an external performance check but does not resolve the hardware floor, independent serving cost or practical autonomy of a smaller institution. The current D1006-07a already has a +1 for the October 16 weight release; this evaluation neither repeats that award nor establishes that possession alone delivers usable capability.
Dates and implementation stage
Action/stage 2026-10-27; publication 2026-10-27
