Policy Goals and Support Scope
Active Patching: Aviatrix actively develops patches (bug fixes, maintenance updates, security fixes) for the two (2) most recent Generally Available (GA) Major.Minor releases. Technical Support: Technical support is provided for releases that have not reached their End-of-Support date. This policy provides a defined period of technical support after routine patching ends.Definitions
General Availability (GA) Date: The date a specific Major.Minor software release is officially published and made available to customers. End-of-Life (EoL): The milestone after which Aviatrix Engineering ceases providing routine patches (bug fixes, maintenance updates) for a specific Major.Minor release (N). End-of-Support (EoS): The final date Aviatrix Technical Support provides technical assistance or accepts support requests for a specific Major.Minor release (N). Transitional Release: A Major.Minor release published outside the normal feature cadence to deliver platform or operating-system foundation work. See Supported and Patched Releases.Lifecycle Milestones and Timelines
End-of-Life (EoL) Date: The EoL date for a release (N) is generally expected to be after at least one patch is available for the next release (N+1), and before the General Availability (GA) Date of the second subsequent release (N+2). Example: the EoL date for release N falls on or after the first patch of N+1, and on or before the GA date of N+2. Impact: After a release reaches EoL, routine patching ceases and the release enters the support-only phase. End-of-Support (EoS) Date: The EoS date for a release (N) is no less than six (6) months after its End-of-Life (EoL) Date. Aviatrix frequently publishes a longer period where customer adoption patterns warrant it; the published schedule in this document is authoritative. Minimum Commitment: Regardless of release timelines, Aviatrix guarantees that every Major.Minor release made generally available, including transitional releases, will be supported for at least 12 months from its GA date. Impact: Provides customers with a guaranteed minimum support lifecycle, regardless of release cadence changes.Supported and Patched Releases
Active Patching Scope: Aviatrix actively patches the two most recent GA Major.Minor releases. Routine patching for release N ceases at the EoL date for that release, which falls after at least one patch is available for N+1 and before N+2 becomes GA. Transitional Releases: Aviatrix may occasionally publish a Major.Minor release outside the normal feature cadence to deliver platform or operating-system foundation work. A transitional release:- carries the same 12-month minimum support guarantee as any other GA release;
- does not advance the N+1 / N+2 sequence used to calculate EoL dates for earlier releases; and
- may be published in the schedule below as part of a combined major-version line together with the following release, since upgrading within that line does not require a platform migration.
Planning for Success
Customers are responsible for managing their software lifecycle and planning upgrades before a release reaches its EoS date. Staying current ensures access to patches, features, and support. Aviatrix recommends considering both EoL (end of patching) and EoS (end of support) dates in your planning cycles to ensure continuous support coverage. Upgrades within a major-version line are performed in place. Upgrading across certain major-version boundaries requires a platform migration rather than an in-place upgrade; the release notes for the target release identify when this applies. Account for the additional planning effort when selecting an upgrade target.Aviatrix CoPilot
Aviatrix CoPilot follows a continuous delivery model with automatic updates. Only the latest release of CoPilot is supported, and CoPilot may only work fully with actively supported Controller releases. For optimal performance and functionality, Aviatrix recommends using CoPilot with the most current Controller version. Refer to CoPilot release notes for specific compatibility requirements.EoL and EoS Schedule Publication
EoS and EoL dates are not announced when a release is first published, as they are relative to subsequent releases and release timing. These dates are confirmed and published as future releases become available. Aviatrix reviews and updates the schedule below at each Major.Minor GA.Policy Changes
Aviatrix reserves the right to update this End-of-Life Policy. Any changes to this policy will not shorten the support period for releases that have already been made Generally Available.Aviatrix EoL/EoS Schedule and Support Duration
Status as of September 17, 2026
Notes:
- “Supported: actively patched” means the release receives routine patches per Policy Goals and Support Scope. “Supported: support only” means the release has passed its EoL date: Aviatrix Technical Support continues to accept and work support requests until the EoS date, and patches remain available at the discretion of Aviatrix per Supported and Patched Releases, but routine patching has ended. Status values reflect the publication date above and are reviewed at each Major.Minor GA.
- Releases 10.0 and 10.1 form a combined line. 10.0 was a transitional release per Supported and Patched Releases. Customers on 10.0 should upgrade to 10.1, an in-place upgrade within the same line, to continue receiving routine patches. The 12-month minimum support guarantee for 10.0 runs from its GA date of Aug 13 2026.
- Estimated EoL dates are projections tied to future release timing and may shift. EoS dates shown as specific dates are committed and will not move earlier. The EoS date of Jun 30 2027 for 8.2 and the EoS date of Dec 31 2027 for 9.0 hold regardless of when the corresponding EoL dates land.
- The EoL date for 9.0 is set at the GA of release 10.2, currently expected in Q1 2027.
- Any release not listed above that predates the oldest release listed has reached End-of-Support.