# Product release lifecycle

This document describes Sonar’s product release lifecycle and standard definitions for alpha, beta, and general availability (GA) stages. The alpha and beta stages replace the previously used Early Access (deprecated) programs.

## Alpha <a href="#alpha" id="alpha"></a>

Products or features in the alpha stage have limited functionality and are subject to significant change or cancellation. Access is invitation-only. Products or features in alpha are not covered under SLA.

## Beta <a href="#beta" id="beta"></a>

Products or features in the beta stage have nearly complete functionality. Access is by request and requires approval. Products or features in beta are not covered under SLA.

## General availability (GA) <a href="#general-availability" id="general-availability"></a>

A public release of a product or feature. It includes all planned functionalities and is available to customers for purchase. A GA product is publicly announced by Sonar, fully functional, stable, documented, supported, and covered under SLA.

## About Early access features <a href="#about-early-access-features" id="about-early-access-features"></a>

{% hint style="warning" %}
**Deprecation notice:** The Early Access stage is deprecated in favor of the alpha, beta, and GA stages. If the feature you’re using is in Early Access, it is still functional, but new feature releases now follow the alpha > beta > GA configuration.
{% endhint %}

Sonar makes some features available as [Early Access](https://www.sonarsource.com/legal/early-access/) releases. They are excluded from service level agreements (SLAs) and support obligations.


---

# Agent Instructions: 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:

```
GET https://docs.sonarsource.com/sonarqube-server/2025.5/server-update-and-maintenance/product-release-lifecycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.