Key details

  1. October 16, 2026: Beam weights released on Hugging Face under Apache 2.0.
  2. 501.3B total parameters, 23.4B active per token; 1M-token context; text-only.
  3. BF16, FP8 and NVFP4 checkpoints are listed.
  4. Hosted Reflection API and self-hosting/integration paths announced.
  5. Vendor model-card benchmark: 81.6% SWE-bench Verified (BF16), 80.1% Terminal Bench v2.1 (BF16).
  6. Benchmark numbers are vendor-run and may differ from independent real-workload results.

What builders should take away

  1. Test released checkpoint quality against your coding-agent tasks rather than extrapolating from a single leaderboard.
  2. Budget storage, VRAM, network and inference operations before choosing self-hosting.
  3. Review Apache 2.0 attribution and notice obligations alongside the provider's recommended use policy.
  4. Compare the hosted API with self-hosting on end-to-end task cost, latency and operational complexity.
  5. Maintain sandboxing, tool permissions and evaluation even when the model publishes a safety report.

What changed

On October 16, 2026 Reflection released Beam 1.0 model weights on Hugging Face under Apache 2.0, with BF16, FP8 and NVFP4 variants. Its model card specifies 501.3 billion total parameters, 23.4 billion active per token, a one-million-token context window and text-only input/output. Reflection also launched hosted API access and reference agent/inference integrations. The vendor publishes benchmark tables and a safety technical report, but independent evaluations of released checkpoints remain limited at launch.

Why it matters

The licence allows commercial self-hosting, fine-tuning and integration without the separate model-as-a-service restrictions found in some other recent large-model releases. Open checkpoints allow teams to inspect and benchmark their own agent workloads and avoid an exclusive hosted provider, although hundreds of billions of stored parameters and long-context serving remain beyond ordinary developer hardware. Model usefulness depends on real task quality, latency, memory and cost, not advertised benchmark rank alone.

Open weights, not a small desktop model

Beam is a sparse mixture-of-experts text model with 501.3B total and 23.4B active parameters, 52 layers, 256 experts and a 1M context window. Hugging Face hosts BF16, FP8 and NVFP4 weights. Sparsity reduces active computation per token but does not eliminate the memory needed to store or distribute a very large checkpoint. Self-hosting requires serious GPU resources and validated serving configuration.

Apache 2.0 changes the commercial options

Reflection explicitly releases the weights under Apache 2.0 and says developers may customise, quantise, fine-tune and use outputs for model training. That contrasts with restricted licences on some other large open-weight models. Apache 2.0 obligations still apply, and teams must assess privacy, model-use policy and jurisdictional constraints for their own deployment.

Benchmark claims need independent repetition

Reflection's model card reports 81.6% on SWE-bench Verified for BF16, 80.1% on Terminal Bench v2.1 and 76.5% on SWE Bench Pro v2-Hard, with temperature 0.7 and top_p 0.99. Those are vendor-reported results, not independently established cross-provider rankings. Harness configuration, data contamination controls, inference cost and actual tool reliability may change the comparison.

Agent ecosystem and safety boundaries

Reflection advertises more than 40 partner integrations, hosted access and published safety methodology. The model is text-only, not multimodal. A model card and safety report improve inspectability but do not prove agent sandbox safety or immunity to prompt injection; operators should run their own evaluations and permission controls.

What to watch next

  • Independent evaluation and quantisation quality comparisons.
  • Measured inference cost and supported deployment hardware for each checkpoint.
  • Actual adoption and interoperability of the announced partner integrations.
  • Future model revisions, licences and safety disclosures.

Still unclear

  • Vendor benchmark results have not been independently reproduced for all released variants.
  • Hardware memory and total cost depend on quantisation, serving strategy and context length.
  • Partner integrations may vary in maturity and availability.

Sources

Direct reading behind this dossier.

4 sources
Beam Model Card
Reflection primary

Architecture, benchmarks, data and safety methodology.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment