The Introducing Mistral Large 4 page has said the same thing since October 6: “Weights drop end of this month,” and, more fully, “We will release the weights by the end of the month, along with more details on the architecture, additional benchmarks, and our post-training methodology.” That is the whole of the vendor’s written commitment – no day, no hour. On Day 26 of 31 in Mistral’s own month-end window, three clocks are running anyway. The first is October 27: the date Reuters reported on October 6, carried here after its own URL returned a 401 at fetch and the date was confirmed through search extraction and secondary coverage explicitly citing the wire – reported, and never put on the record by Mistral. The second is that undated sentence. The third is the Hugging Face card, fetch-verified October 26: an “Upcoming release” badge, a countdown reading 05 days, 00 hours, 13 minutes to October 31 at 15:00Z, and a Current ETA stamp whose tooltip says “The release date may still change.” This desk mapped the same pegs two days ago; the compression has only tightened since.
The wait list is the one measurable moving part: 813 people waiting on October 14, 939 on October 24, 951 by the October 26 fetch. Interest is compounding into the final week while the artifacts stay put. The repository still lists a single planned artifact, and both the open weights and the LICENSE file are absent from the first-party surface – absence certified at the surface we checked, not inferred. Mistral is spending the window red-teaming the model “with cybersecurity leaders, vetted partners, and state authorities, who will access the same model with reduced moderation and expanded cyber capabilities.” That work proceeds on a schedule the public calendar cannot see, which is precisely the problem a countdown is supposed to solve and does not.
Planning around that invisibility already has a price tag this month. StepFun’s September 20 promise targeted an October 15 release; when the date arrived, the expected repository returned a 404 and the license was still unpublished – the vendor-promise class’s first exhibit. Teams that had pre-allocated clusters and engineering time ate the slip as idle hardware. Mistral’s signal is stronger than StepFun’s was: a dated card plus a month-end sentence, not a bare day. But a reliability class is a reliability class. Reported and projected are not committed, and the card says so in its own tooltip.
The calendar is the half of this release that expires. The decision that outlives it is the license. Mistral Large 3 shipped under permissive Apache 2.0; this desk’s own license countdown reported the industry expectation that Mistral Large 4 arrives under a custom framework instead – which would place the new weights inside the convention already documented across the four-lab revenue gate. Mistral’s existing Modified MIT terms, in place since August, already push companies with monthly revenue above $20 million into a commercial license or through Mistral Studio. What is unknown is narrower and more consequential than the date: whether the new model’s LICENSE repeats that gate, moves it, or does something the precedent does not prepare builders for. The file does not exist yet, so no claim about its terms is available to make. The absence is the fact.
That gives deployers a cleaner rule than the countdown offers. Gate migration scheduling, procurement review, and compliance work on the fetch of a LICENSE file, not on a timer the vendor has explicitly reserved the right to move. Weights landing without terms would repeat the StepFun shape: a repository you cannot deploy from. Terms landing without the weights would matter more than the weights themselves. When the artifact finally appears, the first question is not whether the countdown reached zero. It is what the document says your revenue obligates you to do.