> For the complete documentation index, see [llms.txt](https://docs.soda.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soda.io/reference/documentation-access-and-licensing/release-stages.md).

# Release stages

What do "private preview", "public beta", and "general availability" mean for a Soda feature? Learn what to expect at each stage.

Soda releases each feature in stages to guarantee your organization has access to stable, supported functionalities.

Currently, a feature can be in one of three stages:

| [**Private preview**](#private-preview)           |
| ------------------------------------------------- |
| [**Public beta**](#public-beta)                   |
| [**General availability**](#general-availability) |

### Private preview

A private preview is an **early release** to a **limited group** of users. A private preview feature does not appear in Soda Cloud until it has received feedback from our design partners.

* The feature is under active development.
* Functionality, configuration, and interface can change.
* Documentation covers the main workflow and may not be complete.

> To ask about access, contact <support@soda.io>.

### Public beta

{% hint style="info" %}
Public beta features are available at **no additional cost during the beta**.
{% endhint %}

A public beta is available to every eligible organization. **You do not need to request access**. If the feature applies to your plan, it will be available in Soda Cloud automatically.

{% hint style="info" %}
Your organization can **opt out of public beta features**. To do so, please contact <support@soda.io>.
{% endhint %}

**Soda will keep refining the feature** based on user feedback.

* Functionality and documentation can change before general availability.
* Configuration you create during the beta continues to work as the feature develops.
* You may encounter edge cases that have not been documented yet.

**Send questions**, **problems**, and **feedback** to <support@soda.io>. Feedback during a public beta directly shapes what changes before the feature becomes generally available.

### General availability

A generally available feature is **fully released and stable**. It is available to all eligible organizations, documented in full, covered by standard support, and carries no stage label.

{% hint style="info" %}
A public beta feature that becomes generally available will be **priced according to your organization's plan**.
{% endhint %}

## Identify the stage of a feature

* Each feature's documentation states its stage at the top of the page.
* In Soda Cloud, look for the **Preview** or **Beta** label next to the feature.

<figure><img src="https://1123167021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA2PmHkO5cBgeRPdiPPOG%2Fuploads%2FicOlIWwtpF0JtycG0p1q%2Fimage.png?alt=media&amp;token=5045fb47-b6d3-48b9-8fd4-324e0bf278ff" alt="" width="435"><figcaption></figcaption></figure>

* Generally available features do not carry a label.

***

{% hint style="info" %}
You are **not logged in to Soda** and are viewing the default public documentation. Learn more about [Licensing & documentation access](/reference/documentation-access-and-licensing.md).

If you do have a Soda license, make sure to **log in to Soda Cloud in this same browser**.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.soda.io/reference/documentation-access-and-licensing/release-stages.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.