> This is the Markdown version of the page. For the complete Lattice Developers documentation index, fetch https://developer.anduril.com/llms.txt. Append .md to any page URL for its clean Markdown.

# API lifecycle

Lattice APIs move through a lifecycle as they mature: **preview**, **beta**, **generally available (GA)**,
and eventually **deprecated**. This page describes what each stage means and how to identify it.

## Preview

A preview API is functionally stable, and you can build against it the same way you would a GA API, but it
isn't yet available in every Lattice environment.

Because environment availability is still expanding, confirm with your Anduril representative whether an API is
available in your specific deployment before depending on it in production.

## Beta

Beta APIs are not denoted with a separate label. Instead, the API package and path indicate the stability.

For [REST](/reference/rest), beta APIs are marked with a stability marker in their path, for example `/api/v2beta/service`.

For [gRPC](/reference/grpc), beta APIs are marked with a stability marker in the protobuf namespace, for
example `anduril.service.v2beta`.

## Generally available (GA)

Any API not marked **preview** or **beta** is generally available: stable, and available across all Lattice
environments.

## Deprecated

Deprecated APIs are on a path to be removed. Where a replacement exists, the reference documentation for the
deprecated API links to a migration guide.