Editor’s note (Oct 29, 2026): This article has been corrected. The original version carried present-tense claims about the Mistral Large 4 repository and LICENSE file that are now historical, since both the weights and the LICENSE were published on October 29. Those passages have been restated as observations from the October 27-28 window, and the closing paragraph now reflects the resolved outcome.
October 27 arrived, and Mistral Large 4’s weights did not come with it. On Tuesday afternoon, the primary surfaces carrying this release – the Hugging Face placeholder and Mistral’s own blog index – showed the same state they had held the day before: an upcoming-release page, a countdown to October 31, one planned artifact, and no weights.
The Hugging Face card still read “Upcoming release.” Its countdown at that time stood at 04 days, 00 hours, 13 minutes to October 31 at 15:00Z, stamped as a Current ETA whose tooltip says “The release date may still change” – an approximateEta field, not a commitment. As of that read the repository listed a single planned artifact and served no model files. The wait list stood at 969 people waiting on October 27 – up from 813 on October 14 and 939 on October 24 – while the artifacts stayed absent.
The countdown piece this desk published the day before closed on the claim that would outlive the calendar: the LICENSE. That claim was settled at this read: no LICENSE file had been published for Mistral Large 4, so no statement about what the model permits or forbids was available to make. What that piece posed as open was narrower still: does the file repeat the $20M revenue gate that Mistral’s existing Modified MIT terms impose, move it, or do something the precedent does not prepare builders for. Absence was the reportable fact, and it stayed that way.
Update, October 29: the file published with the weights. Mistral’s release page arrived alongside the Mistral Ecosystem Open-Weight License – a modified MIT whose single added condition requires any business operating a Model-as-a-Service offering to obtain a separate commercial license from Mistral before commercial use. The text answers the question this piece and the countdown piece both posed: no revenue threshold appears in the file at all. The gate it does impose turns on what you operate, not what you earn.
Two dates were in conflict, and neither resolved in Mistral’s own words. October 27 is the day Reuters reported for the weights drop; the peg rests on secondary coverage citing the wire. October 31 is what the Hugging Face card carried. Mistral’s own October 6 announcement, unchanged since October 7, committed to nothing narrower than “Weights drop end of this month” and “We will release the weights by the end of the month.” Mistral’s blog index held 92 results with the newest entry still dated October 6 and the most recent post of any kind dated October 21. The separate newsroom path this desk has cited in earlier coverage is now retired – not treated as a missing announcement.
The shape has a precedent inside our own archive. StepFun promised October 15 on September 20; when the date arrived, no repository had appeared and the license was still unpublished – the vendor-promise class’s first exhibit. Mistral’s signal was stronger: a dated card plus a month-end sentence rather than a bare day. It was still not a dated commitment, which is why the three pegs sitting in the last four days of October were mapped as expectations, never as a schedule.
What that leaves deployers is the rule this beat has been building toward for a month: gate migration scheduling, procurement review, and compliance work on the fetch of a LICENSE file, not on a timer or a wire story. The timer said October 27. The document did not exist that day. The gate stayed shut at the reported date itself, and it opened when the file exists – which, for Mistral Large 4, it did on October 29.
