> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/appendix/feature-states.md).

# Feature States

## Feature States

Features can be in of the several states of release as noted below.​

| State                     | Description                                                                                                                                                                                                                                                          | User Type          |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------ |
| Generally Available or GA | This is the status of all features unless otherwise noted. The feature is ready for everyone to use and fully supported under normal SLA's.                                                                                                                          | Everyone           |
| Preview                   | This type of feature has supporting underlying API's, but is a new feature which is best for early adopters and those who need the feature. There may be known issues, limitations, and support may take longer. This feature will become GA after a period of time. | Early Adopter      |
| Private Preview           | A limited-access program where a select group of users are invited to test and provide feedback on a new feature. These features are not recommended to be used in production. Please reach out to your account executive for more information.                      | Bleeding Edge User |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cc.docs.landis.cloud/appendix/feature-states.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.