Reflection released Beam's weights—what can outsiders verify?
The 501-billion-parameter model can now be downloaded under Apache 2.0, but its strongest performance and safety claims still come from the developer. The published safety report is unusually detailed and also exposes important unresolved risks.
The short version
3 key points
- What changed
- Reflection AI released Beam's instruction-tuned weights in BF16, FP8 and NVFP4 formats on 16 October under Apache 2.0; the earlier 5 October announcement had only promised a later release.
- Why it matters
- Software teams gain another model they can run under their own controls, but workers and customers should not be promised faster or safer outcomes until errors, oversight and operating costs are measured on real tasks.
- What to watch
- Independent benchmark reruns with matched budgets and published traces; release of the promised Iris evaluation artefacts; multilingual and deployment-specific testing; and measured evidence on latency, energy, cost, security incidents and human correction burden.
The material change is access, not another launch promise
Reflection AI made Beam's instruction-tuned weights downloadable on 16 October, turning its 5 October preview into a verifiable release. The model card lists a sparse mixture-of-experts system with 501.3 billion total parameters, 23.4 billion active per token, 52 layers and a one-million-token context window. BF16, FP8 and NVFP4 versions carry an Apache 2.0 licence. That gives researchers and organisations permission to inspect, modify and self-host the model instead of relying only on a vendor API. Access is not the same as accessibility: AWS says even the reduced-precision versions require substantial multi-GPU infrastructure, specialist serving software and workload-specific testing.[1][2][4]
Who it affects
Software teams gain another model they can run under their own controls, but workers and customers should not be promised faster or safer outcomes until errors, oversight and operating costs are measured on real tasks.[1][2][3][4]
Keep in mind
There is no peer-reviewed paper or independent replication for Beam. Capability scores are developer-run; several safety tests use small samples, simulated environments or model judges, and the overall systemic-risk label is self-assessed.
Multi-source analysis · 4 linked sources. Original source date: 16 October 2026.
Read the full report · 4 min The evidence, methods, implications and limitations
The material change is access, not another launch promise
Reflection AI made Beam's instruction-tuned weights downloadable on 16 October, turning its 5 October preview into a verifiable release. The model card lists a sparse mixture-of-experts system with 501.3 billion total parameters, 23.4 billion active per token, 52 layers and a one-million-token context window. BF16, FP8 and NVFP4 versions carry an Apache 2.0 licence. That gives researchers and organisations permission to inspect, modify and self-host the model instead of relying only on a vendor API. Access is not the same as accessibility: AWS says even the reduced-precision versions require substantial multi-GPU infrastructure, specialist serving software and workload-specific testing.[1][2][4]
The benchmark evidence is broad, but still company-run
Reflection reports 81.6% for the BF16 model on SWE-bench Verified, 80.1% on Terminal-Bench 2.1, 51.1% on Humanity's Last Exam with tools and 80.8% on MCP Atlas. The card says evaluations used temperature 0.7 and top-p 0.99 and publishes results for all three numerical formats. It does not provide uncertainty intervals, complete run traces or an independently controlled comparison with rivals. The release blog's claim of roughly three-times-fewer reasoning tokens therefore remains a developer estimate. The model card describes public, licensed and commercially obtained training data, with filtering and benchmark decontamination, but does not publish a source-by-source dataset inventory. Its one-million-token context is a supported technical limit, not evidence that every fact remains reliable across a document of that length. Teams should test representative repositories, tool permissions, failure recovery, latency and human correction time before treating benchmark scores as workplace productivity evidence.[2]
The distinction that matters
What the release lets outsiders inspect—and what it does not prove
The same publication package contains verifiable access facts, developer-run performance evidence and a self-assessed safety conclusion. They should not be given equal weight.
Weights and licence
Three checkpoint formats are downloadable under Apache 2.0
Access and reuse permissions can be checked directly
Capability table
Scores span coding, reasoning and tool-use benchmarks
Useful test targets, but not independent replication or workplace outcomes
Safety report
Methods and denominators are published for several risk evaluations
More auditable evidence, while the risk classification remains the developer's
The safety report adds denominators—and a reason for scrutiny
The separate safety report is more informative than a generic assurance. For automated systemic-risk benchmarks, Reflection says it ran each model three times and pooled the attempts. It tested all 100 text-only questions in the Human Pathogen Capabilities Test: Beam reached 61% exact-match accuracy, first among 13 compared models and 30 percentage points above the cited expert reference. That test measures knowledge, not successful laboratory work. On a ten-target DNA fragment-design task, Beam passed 23 of 28 completed attempts, while two more timed out; the tiny task set limits generalisation. These results matter because open weights can be adapted without the developer's hosted safeguards.[3]
Published methods improve accountability, not certainty
Reflection classifies Beam as having a limited effect across biological, chemical, cyber and loss-of-control risk categories. That is the developer's conclusion under its chosen framework, not a regulator's or peer-reviewed finding. Some safety evaluations used model judges, small samples or simulated environments; planned Iris evaluation artefacts were not yet available when checked. The useful next step is independent reproduction using the released weights, especially for multilingual use, prompt injection, cyber offence and biological uplift. For developers, the release creates a real option for local control. For organisations handling sensitive code or public services, it also transfers more responsibility for security, monitoring and incident response to the deployer.[2][3][4]
Watch the background, then check the evidence
Illustrative photo · not a video frame
The Royal Society · 2 min 31 sec · Background explainer
What is artificial intelligence? | The Royal Society
YouTube loads only when you choose; playback starts when you press play.
A short introduction to artificial intelligence from the Royal Society. Start here for basic concepts, then use current reporting to explore what has changed.
Evidence check: Published in 2018, before today’s generative AI tools. Useful for basic concepts, rather than an overview of current capabilities.
Published 2018-11-28. Source checked 14 October 2026. Check captions on the publisher’s video page.
Explore current AI technologyPhoto: ThisisEngineering / Unsplash · Licence
Evidence check
There is no peer-reviewed paper or independent replication for Beam. Capability scores are developer-run; several safety tests use small samples, simulated environments or model judges, and the overall systemic-risk label is self-assessed.
Reporting basis: Multi-source analysis. Original source date: 16 October 2026.
Continue the story
Read next
Also about open-weight models
DeepSeek’s open AI update: what its agent benchmarks show
DeepSeek reports stronger agent and coding benchmarks. Its own model card supplies the results; independent checks and real-work performance remain open questions.
Read the 5 min reportAlso about ai safety
Can small AI models replicate across ordinary devices?
Anthropic's controlled evaluation shows that advanced models can assemble inference on varied hardware and that GLM-5.2 completed a simplified eight-node replication chain. It did not demonstrate an autonomous worm escaping onto the internet: access was deliberately easy, the agent model ran elsewhere, and the near-term timeline is a projection.
Read the 7 min reportExplore the full source and evidence record
What this means for people
- Software teams gain another model they can run under their own controls, but workers and customers should not be promised faster or safer outcomes until errors, oversight and operating costs are measured on real tasks.
Global context
A US developer has released a very large model under a permissive licence while many leading systems remain API-controlled. The licence broadens technical access globally, but the hardware and engineering needed to run 501 billion parameters concentrate practical access among well-resourced organisations.
What the evidence does not yet show
- There is no peer-reviewed paper or independent replication for Beam. Capability scores are developer-run; several safety tests use small samples, simulated environments or model judges, and the overall systemic-risk label is self-assessed.
What to watch next
- Independent benchmark reruns with matched budgets and published traces; release of the promised Iris evaluation artefacts; multilingual and deployment-specific testing; and measured evidence on latency, energy, cost, security incidents and human correction burden.
Living evidence record
Impact record IAI-0FGIA2F
Evidence stage
Announced
Confidence
Supported
Reporting basis
Multi-source analysis
Independent or research support
Not yet
Record status
Monitoring
Last checked
18 October 2026
Source trail
4 direct sources across 2 source types.
People impact
Documented in this record.
Uncertainty
Limits and next checks are explicit.
Stages describe the evidence available—not whether a technology is good or bad. See the public method.
Evidence trail
Sources used for this report
Links checked 18 October 2026
Research question, topics and regions
Topics: Open-weight models · Agentic coding · Model evaluation · AI safety · Biosecurity · Self-hosting
Regions: United States · North America · Global
This report is labelled multi-source analysis. We summarise and analyse source material in our own words; company statements remain attributed claims until independently supported. Translated summaries preserve the meaning of the original source and link back to it. Read our editorial standards.
The Impact Brief · Free
Keep following the stories that matter to you.
Get our weekday briefing on what changed and why it matters. Choose your topics below.
Reader commentary
What does this mean where you are?
Tell us what you have seen at work, in your community or in everyday life. A question is welcome too. No account is needed; we review notes before publishing them.
Explore commentary across the portal →Published reader notes
0No published reader notes yet. You can start the evidence-led discussion above.
Prefer a private correction or response? Contact the newsroom.