A preview is not a product
An open-weight preview appeared on Monday, ahead of a larger release later in the year. The distinction matters more than the model does.
On 9 March 2026 DeepSeek published an open-weight preview model, smaller than the full version expected later and released mainly to show the architecture it is built on. It is a preview, and the company describes it as one.
That word is doing real work, and it is worth separating from the surrounding noise.
What a preview is for
Researchers and developers, to try an approach before it is finished. Not for a company to build a process on.
A preview can change without notice, be withdrawn, behave differently from the eventual release, or simply be abandoned. None of those is a defect — it is what preview means — but each is disqualifying for anything your Tuesday depends on.
The distinction this blog keeps returning to
On 18 June we separated a preview from a version under a stability commitment. On 13 August a product changed under millions of users and they had to argue it back. The pattern is the same each time: what matters for a business is not how good something is today but whether it will be the same next month.
A preview offers no such assurance and does not pretend to. The mistake is not in the release; it is in reading coverage that omits the word.
How to read announcements over the next two months
Three words change what an announcement means to you. Preview or beta: interesting, not buildable. Generally available: usable, and ask about version pinning. Deprecated: you have a deadline, find out what it is.
Most coverage treats all three identically. Sorting them takes a second and removes most of the urgency you would otherwise feel.
And the forecast from three weeks ago
On 20 February this blog suggested a spring cluster of major releases was likelier in the following two months than later. A preview is consistent with that and does not confirm it. We will report in due course whether the forecast held, including if it did not.