Check the repo, not the calendar

October 15 was the date StepFun gave for the Step-5 BF16 weights, and the date arrived with two different observations. Forkast reported in the early hours that the expected Hugging Face repository returned a 404 at 01:55 UTC, that third-party copies were unendorsed, and that no license had been published. Read later the same day, the official repository is public and ungated, with the full checkpoint, the tokenizer, inference code and a license file all present. Hugging Face's API gives the repo a last-modified time of 01:31 UTC on October 15 — earlier than the reported 404 check, but a last-modified stamp is not a public-at timestamp, and a repository's availability can change. The two observations do not by themselves settle the precise moment the repo became public, and from the outside there is no clean way to resolve it. What a reader can verify now is the current state, and the current state is a live, public repo on the promised date.

That sequence is the useful part. A promised date is not a release, and a missed-date headline has a shelf life measured in hours. The repo is the only version of this story that updates itself.

The license is the release

The weights arrive under the StepFun Model License 1.0. The grant is broad: royalty-free use, copying, modification and distribution, with a patent license alongside. The conditions sit further down. Section 2(b) is an attribution condition measured by calendar month: if, in any calendar month, a commercial product or service built on the model has more than 100 million active users, or generates more than US$20 million in revenue, its operator must thereafter prominently display "Powered by StepFun AI". Section 2(c) names two situations in which a separate commercial license must be agreed with StepFun in advance: a hardware manufacturer or brand owner first making the model's capabilities commercially available as a feature of a phone, car, glasses, robot or similar device, or of its accompanying services; and any commercial use by an operator that runs a model-as-a-service business, once the combined revenue of that operator and its affiliates from all sources — not just the hosted-model business — exceeds US$20 million over any consecutive twelve months. The requirement is not unconditional: Section 2(c) does not apply to internal use that makes nothing available to third parties, or to use obtained through a distribution channel certified by StepFun, within the scope of that certification. A model trained to a material extent on Step-5 outputs counts as a derivative work under the license. None of this blocks a research lab or a company serving the model inside its own product at modest scale. It does mean "open weights" and "Apache" are not synonyms here, whatever the launch coverage implied.

What it takes to run

Six hundred billion parameters in BF16 is about 1.2 terabytes before a single token of KV cache, and the card's configurations reflect that. BF16 serving is documented on eight B300s in one node or sixteen H200s across two. The FP8 checkpoint, published alongside, halves the hardware to four B300s or eight H200s on a single node. The 1M-token context is a maximum covering input and output combined, and the deployment notes are explicit that the documented configurations do not guarantee enough memory for a request of that length. The card also carries a caveat that deserves more attention than the parameter count: the reference implementation's full BF16 convert-then-generate file-shard workflow has not yet been validated end to end, even though checkpoint names and shapes, small-model conversion, loading and generation, and full-model streaming-weight inference have been. That caveat belongs to the reference workflow; it is not a claim that every BF16 serving route is unvalidated. Teams planning around this release should still budget for being early testers of the reference BF16 path, not just for the GPUs.

Sources

  1. [1] Official model repo and model card, Hugging Face (stepfun-ai/Step-5-Preview-BF16; checked 15 October 2026, public and ungated)Read source
  2. [2] License text in the same repo (LICENSE.txt, StepFun Model License 1.0)Read source
  3. [3] Hugging Face API record for the repo (last-modified time, storage size, file list)Read source
  4. [4] Forkast, 15 October 2026, 02:27 UTC: report that the repo returned a 404 at 01:55 UTC and no license had been publishedRead source
  5. [5] Forkast, 14 October 2026: the October 15 date was the only vendor-announced date on the near frontier calendarRead source
  6. [6] MarkTechPost, 20 September 2026: Step 5 Preview launch, 600B/27B specs and the October 15 open-weights commitmentRead source