Zeitleiste der Freigabestufen eines Produkts von links nach rechts: interner Test, Private Preview mit Zugangsbeschränkung, Public Preview mit offenem Zugang aber ohne Verfügbarkeitszusage, und General Availability mit Support und Verfügbarkeitsgarantie.

Preview (Public Preview)

A public preview is a publicly accessible pre-release version of a product that is not yet finished and may change without warning. Providers use it to gather feedback from real users before making binding commitments regarding stability and availability.

A preview is a pre-release version of a product or feature. The provider already makes it available even though work on it is not yet complete. “Public” means that, in principle, anyone can try it out, not just a hand-picked group of testers. In doing so, the provider explicitly reserves the right to change everything further: the feature set, the pricing, even the names of the individual components. It also makes no promise that the service will run permanently or be developed further at all. You can think of a preview like the advance proof of a book that a publisher sends to critics: readable, but with typos and no guarantee that the final version will look exactly the same.

What preview status means for users

The difference from the finished version is not a marketing detail but a legal boundary. For a fully released service, the provider usually commits to a certain availability, say 99.9 percent of the time. If that is violated, there is a refund. For previews, such commitments almost never apply. If the service goes down for a day, you have no claim.

Support is just as important. Previews often come with no priority assistance for problems and no commitment as to how quickly a bug will be fixed. Some providers even contractually exclude the use of previews for sensitive data. For a school project, that doesn’t matter. For a hospital or a bank, it’s a disqualifying factor.

The biggest risk, however, is the end of a preview. Not every pre-release version reaches completion. Some are quietly discontinued after months because too few people used them. Anyone who has built their own software on top of it then has to rebuild everything. That’s why experienced developers treat previews as interesting, but not as a reliable foundation.

From internal test round to general availability

Most large providers use a fixed sequence of stages. It starts with an internal test, followed by a closed round that you have to apply for. This stage is often called Private Preview or Closed Beta. Only after that comes the Public Preview, which anyone can try out. The final stage is called, at cloud providers, General Availability, or GA for short.

During the preview phase, the provider primarily gathers experience from real-world use. Thousands of users try things that no one on the development team thought of. They run into bugs, complain about confusing usability, and wish for features. These feedback loops then lead to changes, often on a weekly cadence. That’s precisely why previews are deliberately unstable: stability would mean that no one is allowed to change anything anymore.

A common misconception is that preview and beta are the same thing. The terms overlap significantly, but “beta” comes from classic software development and refers to a version shortly before completion. “Preview” is often used much earlier for cloud and AI services. What a provider actually commits to is therefore not stated in the name, but in its terms of use.

Previews in AI announcements and stock prices

The term comes up especially often in the context of AI models. New language models frequently appear first as a preview, sometimes with the label directly in the name. A well-known example is OpenAI’s model “o1-preview,” which ran under this name for months. Google, Microsoft, and Amazon also regularly release AI features first in this form. The reason is speed: whoever has something presentable first shapes the debate.

For financial news, this status is therefore an important piece of context. When a company announces a feature as a preview, no revenue is yet associated with it. Often, usage is even free or heavily discounted to attract users. Only with general availability does the regular business begin. Anyone evaluating an announcement should therefore check which stage the product is at.

In everyday life, you also encounter previews outside of AI. A new menu in an app, a feature in a game, or a payment service can be marked as a preview, often with a small notice in the interface. This label is an invitation to try it out and, at the same time, a warning. Anyone who sees it knows: this might look different tomorrow, or disappear entirely.

Subscribe free. Unsubscribe the second it sucks.

High-signal news across AI, business, UX, and tech. Every morning.