Model release

Reflection releases Beam 1.0 open weights for agentic coding

Event time 1 independent sourceUpdated here

The short version

Reflection released Apache-2.0 Beam 1.0 weights, a 501B-total, 23B-active MoE for coding and long-horizon tool workflows.

What changed

Beam 1.0 weights are available through Reflection's official Hugging Face organization; AWS documented SageMaker JumpStart plus self-managed vLLM and SGLang paths.

What it means for you

Teams can evaluate open weights for coding agents on managed or self-controlled infrastructure, but must plan for the complete checkpoint, parallelism, and region availability.

Reflection released the open weights for Beam 1.0, a sparse MoE positioned for software engineering and long-horizon agent tasks. Official material describes 501 billion total parameters, 23 billion active parameters per token, and an effective one-million-token context window. The weights are published under Apache-2.0 in BF16, FP8, and NVFP4 variants through Reflection's Hugging Face organization.

AWS documented a managed SageMaker JumpStart route at launch in US East (N. Virginia) and US East (Ohio). Teams that need more runtime control can instead deploy with vLLM or SGLang. Neither option changes the planning constraint that the complete checkpoint, memory sharding, and serving topology must accommodate the 501B model, not only the active parameter count.

For coding-agent teams, this creates an open-weight option with a self-controlled deployment boundary. Evaluate it first against a contained issue-reproduction suite with read-only tools, logging context use, latency, tool calls, and recovery from failures. Confirm region, quota, retention, and networking before sending proprietary repositories to a managed endpoint. A one-million-token limit and open weights are not guarantees of low cost, modest hardware requirements, or reliability.

Related catalog entry

Fact check

  • VerifiedBeam 1.0 is an Apache-2.0 open-weight sparse MoE with 501B total parameters, 23B active parameters per token, and an effective 1M-token context window.Evidence
  • VerifiedAt launch AWS listed SageMaker JumpStart availability in US East (N. Virginia) and US East (Ohio), and described self-managed vLLM and SGLang paths.Evidence

Coverage timeline

  1. Primary sourceAWS
    AWS