Aviatrix Feature Modes

Aviatrix features are introduced through a structured lifecycle. The structured lifecycle lets you explore and provide feedback on new capabilities as they mature.

Every Aviatrix feature falls into one of three modes in the following table:

Feature Mode Aviatrix Support Stability Enable Method

GA

Full support:

  • Standard Aviatrix support channels

  • SLAs

  • Stable APIs

  • Stable behavior

  • Stable configuration

Breaking changes follow standard deprecation policy

Automatic

Preview

Standard Aviatrix support channels

Some APIs and capabilities may change between Preview and GA

  • From the CoPilot UI

  • From the feature flag toggle on the Settings page

EA

Best-effort support:

On approval, based on the feature, a support plan is created

Significant changes may occur on:

  • APIs

  • Capabilities

  • Configuration

No guarantee of a seamless upgrade from the EA build

Contact your Aviatrix account team

General Availability (GA) Features

GA features are fully tested, fully supported, and safe for deployment in production environments. All Aviatrix features are GA unless otherwise mentioned.

Preview Features

Preview features are functional, supported, and available to all Aviatrix customers. They are in the final stages of development and represent capabilities that have a high likelihood of becoming GA. Preview features are an opportunity for you to evaluate upcoming capabilities and share feedback that shapes the final product.

Early Access (EA) Features

EA features are in active development and available to a select group of Aviatrix customers upon request. They offer a unique opportunity to influence the direction of a feature in its earliest stages. EA features are not guaranteed to advance to Preview or GA.

Adopt Preview and EA Features Safely

Not all preview features carry the same scope of impact on your environment. Some are read-only visibility features that you can enable anywhere. Others modify traffic behavior and are best tried on a single Gateway first. The Feature Classification table classifies every Preview and EA feature so you can adopt each one with confidence.

Impact Scope Levels

Read and understand the following legends before going to the Feature Classification table.

Icon Level Meaning

🟒

Explore Freely

This feature provides visibility, analytics, or recommendations. It does not modify your network configuration or traffic. Enable it in any environment. If the data looks off, use your best judgment and provide feedback so that we can make it better.

🟑

Start Small

This feature can modify traffic behavior or configuration, but you control exactly where to modify. Enable it on a single non-critical Gateway or VPC, observe, then expand when you are comfortable. See the following feature notes for guidance.

🟠

Test First

This feature operates across a broader scopeβ€”a Transit domain, multiple Gateways, or a cloud-wide setting. We recommend trying it in a dedicated test environment or non-critical Transit domain before broader deployment.

πŸ”΄

Lab Recommended

This feature involves fundamental infrastructure changes that affect your network globally and cannot be scoped to individual Gateways. We want your feedbackβ€”please evaluate it in an isolated lab or test environment during the preview period.

Feature Classification

Transit Gateways carry traffic for multiple VPCs and Transit domains. Any inline feature enabled on a Transit Gateway carries a broader impact scope than the same feature on a Spoke.

The feature classifications assume that you follow the guidance to start on Spoke Gateways. If you enable a feature on a Transit Gateway, consider it as one level broader in scope.

Several DCF features can be configured with policies in logging-only mode (no enforcement action). While logging mode is lower risk than enforcement, DCF still inserts into the data path when enabled.

Logging mode is a good first step for observation, but it is not the same as no impact. The feature classifications account for this.

The following table classifies every Preview and EA feature so you can adopt each one with confidence.

Feature Stage Impact Scope Version Introduced GA Version Minimum Safe Scope

DCF IPS

Preview

🟑 Start Small

8.2

β€”

Single Spoke Gateway

DCF TLS Profiles

Preview

🟑 Start Small

8.2

β€”

Single Spoke Gateway

DCF on FireNet

Preview

🟠 Test First

8.1

β€”

Per Transit domain

DCF on Site2Cloud

Preview

🟑 Start Small

β€”

β€”

Single S2C connection

DCF on PSF

Preview

🟑 Start Small

β€”

β€”

Single PSF Gateway

DCF SNI Verification

Preview

🟑 Start Small

β€”

β€”

Single Spoke Gateway

DCF Enforcement on New Clouds

Preview

🟑 Start Small

β€”

β€”

Single Spoke Gateway on new CSP

Intra-VPC Distributed Firewall

Preview

🟑 Start Small

β€”

β€”

Single VPC

Edge Policy Based Routing

Preview

🟑 Start Small

β€”

β€”

Single Edge Gateway

ActiveMesh V4

Preview

πŸ”΄ Lab Recommended

9.0

β€”

Globalβ€”no scoping

Serverless Security

Early Access

🟑 Start Small

8.2

β€”

Single VPC

Hostname SmartGroups

GA

🟑 Start Small

7.2

8.1

Per SmartGroup / Per policy

Kubernetes SmartGroups

Preview

🟒 Explore Freely

β€”

β€”

Per SmartGroup

Kubernetes Node SmartGroups

Preview

🟒 Explore Freely

β€”

β€”

Per SmartGroup

External Groups

Preview

🟒 Explore Freely

β€”

β€”

Per SmartGroup

Egress VPC Score

Preview

🟒 Explore Freely

β€”

β€”

N/A

Topology Builder

Preview

🟒 Explore Freely

β€”

β€”

N/A

Geoblocking

Locked Preview

β€”

β€”

β€”

Coming Soon

Version Introduced is the first Controller version where the feature became available in its current stage.

GA Version is the target or actual version where the feature graduates to GA.

A dash indicates the value is not yet determined.

Feedback

We build preview features for you to try, and your feedback directly shapes what becomes GA. If you have questions, encounter unexpected behavior, or want to share suggestions:

  • Preview features: Supported through standard Aviatrix support channels

  • Early Access features: Contact your Aviatrix account team for dedicated support

  • In CoPilot: Use the feedback button on any preview feature page