Alation Release Support Lifecycle

Alation Cloud Service Applies to Alation Cloud Service instances of Alation

Customer Managed Applies to customer-managed instances of Alation

This page describes the product release lifecycle for the Alation software, specifying the active support and end-of-life timelines for both on-premise and cloud-deployed software. Alation adheres to a rolling support policy for its software versions.

Note

Alation reserves the right to end-of-life or deprecate any software release at its discretion.

End-of-Life (EOL) Policy for On-Premise Software Releases

Releases of Alation software intended for on-premise deployment will be designated as End-of-Life (EOL) at Alation’s sole discretion. A version reaches End-of-Life (EOL) one year after its general availability (GA) release date.

Active Support

For one year following the General Availability (GA) of a release, Alation provides the following as part of its active support:

• Minor Releases: Include features, bug fixes, and enhancements.

• Patch Releases: Include enhancements based on support escalations and code fixes raised by the internal engineering team.

End-of-Life (EOL)

One year after its General Availability (GA) release, a version reaches End-of-Life (EOL) and will no longer receive code fixes, patches, or updates. Customers utilizing EOL versions are strongly recommended to upgrade to a supported version to maintain access to assistance.

Alation does not provide fixes for issues in EOL software versions if those issues have already been resolved or no longer exist in newer versions. This policy helps ensure that fixes are made to the most current supported versions, allowing Alation to keep the software stable, consistent, and easier to maintain.

Example Scenario

Let’s assume it’s March 2025. As of March 2025, the current major GA version is 2025.1. Alation provides active support for all versions released within the past year.

For supported major versions like 2024.3, updates and fixes are delivered only through patch releases of the latest minor release in each version series. For example, updates would be applied to 2024.3.5, but not to earlier minor versions such as 2024.3.1.

This approach ensures that customers benefit from the most stable and up-to-date version within each supported major release.

Alation Cloud Service (ACS) Version Support

On Alation Cloud Service instances, software upgrades are performed once a new version becomes available. Major upgrades to the Core component, also referred to as “Backend” releases, occur monthly following the General Availability (GA) release of a newer version.

Because Alation manages and regularly updates its Cloud Service, the concept of End-of-Life (EOL) does not apply to Cloud deployments. Customers on Alation Cloud automatically benefit from ongoing updates, improvements, and fixes as part of their managed service experience.