Resources Infrastructure

AWX Release Status: Is AWX Still Maintained in 2026?

AWX releases have been paused since July 2024 for a major refactor. Here is a factual overview of the project's current status, what it means for users, and available options.

TL;DR — AWX is still developed, but it no longer ships releases. The last one is 24.6.1, from July 2, 2024. Red Hat paused releases to refactor AWX into a service-oriented architecture, and the refactor is merged into the devel branch. On November 16, 2026, the maintainers removed the release pipeline from the repository, noting that AWX releases are no longer published. As of November 2026 there is no release date and no supported install path for the new version.

Engineers and platform administrators managing Ansible environments frequently ask whether AWX is still viable for production operations. While commits continue to land in source control, the absence of packaged builds for over two years has forced infrastructure teams to evaluate their ongoing operational posture.

This guide summarizes the current project status, documents the refactoring timeline since mid-2024, explains the operational implications of remaining on legacy builds, and outlines the primary migration options.


AWX status at a glance

The following table summarizes the verified state of AWX and its related projects as of November 2026.

Component / InitiativeCurrent Status (November 2026)Primary Source
Latest AWX releaseVersion 24.6.1, published July 2, 2024GitHub Releases (ansible/awx)
Latest AWX Operator releaseVersion 2.19.1, published July 2, 2024GitHub Releases (ansible/awx-operator)
Active developmentActive commits on devel branch (November 2026)GitHub Commit Log (ansible/awx)
Next release timelineNone planned: release pipeline removed on November 16, 2026Pull request ansible/awx#16803
Web interfaceRemoved from AWX during the refactor; development resumed in ansible/ansible-uiAnsible Forum Announcement (April 2026)
Jewel proxy layerSource code and dev container available; no releases plannedAnsible Forum Announcement (May 2026)
Red Hat AAPActively developed and supported commerciallyRed Hat Documentation
Ascender (CIQ fork)Regular releases, latest version 25.6.3 (October 28, 2026)GitHub Releases (ctrliq/ascender)

Why AWX releases are paused

In July 2024, Red Hat engineering placed the AWX release cycle on hold. The maintainers added a prominent banner to the project repository: “Releases of this project are now paused during a large scale refactoring.”

The rationale behind this pause centers on architectural debt. AWX historically operated as a monolithic Django application containing the user interface, API endpoints, task dispatcher, database models, and operational tooling within a single codebase. Over several years, managing dependencies across these components became increasingly difficult.

Red Hat initiated a modernization program aimed at restructuring AWX into a pluggable, service-oriented architecture. Under this vision, individual components run as decoupled microservices rather than a single monolithic container:

  1. Separation of the web interface: The front-end UI was extracted from the backend repository so it could iterate independently.
  2. Pluggable service integration: The core engine was reworked to interact with adjacent automation components (such as Event-Driven Ansible and Galaxy) via dedicated service contracts.
  3. Container-first execution: Changes were made to align the internal task lifecycle with containerized execution environments.

Because these changes altered internal APIs, database schemas, and packaging formats, the maintainers elected to suspend stable releases until the underlying architecture reached functional parity.


What’s changed since the last release (timeline)

The following chronological timeline records the major milestones, community updates, and repository changes that have occurred since stable packaging stopped:

  • July 2, 2024: Red Hat publishes AWX 24.6.1 and AWX Operator 2.19.1. These remain the final stable builds distributed by the upstream maintainers.
  • July 2024: Maintainers officially announce the release pause and publish technical notes detailing plans to break AWX into modular services.
  • September 22, 2025: A thread titled “Is there a future for AWX?” opens on the official Ansible forum. Community members ask for a status update and a timeline. In October and November 2025, a member of the Red Hat community team acknowledges the communication gap and announces a plan to provide more regular updates.
  • January 20, 2026: Red Hat posts an update titled “AWX modernization: Moving forward”. The post confirms that the architectural refactoring work is merged into the devel branch and nearing completion. The update does not provide a release target or a documented installation procedure.
  • April 30, 2026: Red Hat announces that development of the web interface, removed from AWX during the refactor, has resumed in the public ansible/ansible-ui repository. The post describes the UI as in active development and warns that “not everything is going to work out of the box” when running AWX from the devel branch.
  • May 6, 2026: Maintainers publish the source code for Jewel, a lightweight reverse proxy and authentication routing layer designed to connect AWX with peripheral pluggable services. The post explicitly clarifies that Jewel is an upstream development project with no planned standalone packaged releases.
  • August 11, 2026: Asked on the forum whether a release is possible in 2026, an Ansible Steering Committee member replies that they are not involved in AWX and do not know of any plans or ETAs.
  • November 16, 2026: The maintainers merge a pull request that removes the release staging and publishing workflows from ansible/awx. Its description states that “AWX releases are no longer published, so the release pipeline in this repo is dead code.” Commits continue to land on the devel branch.

What this means if you run AWX today

Teams currently operating AWX in production face specific maintenance, security, and planning trade-offs.

1. Version 24.6.1 is frozen

AWX 24.6.1 still executes Ansible playbooks as expected on compatible Kubernetes clusters, but this version receives no maintenance. CVEs identified in underlying Python libraries, Django components, or base operating system packages will not receive backported patches.

A related indicator is the companion awx.awx collection on Ansible Galaxy. The collection has not received an update since version 24.6.1 on July 2, 2024. Automation scripts that configure AWX via this collection cannot access modern capabilities without running into compatibility warnings.

2. Running the devel branch is not production-ready

While developers can build container images directly from the Git devel branch, doing so in production introduces substantial stability risks. The upstream maintainers explicitly acknowledge that documentation, migration scripts, and component glue remain incomplete. Pulling development commits risks encountering breaking schema changes, missing UI screens, and unverified API contracts.

3. There is no release to wait for

With the release pipeline removed in November 2026, there is no packaged version of the new architecture to upgrade to, and no announcement says one is coming. Based on Red Hat’s forum posts, running the refactored AWX would in any case mean a new deployment rather than an in-place upgrade: the user interface is now a separate project, Jewel adds a routing layer, and the installation methods have changed.

Either way, staying on AWX means owning a control plane that no longer ships releases, which gives infrastructure teams a natural moment to evaluate whether AWX still fits their operational requirements.


Ready to orchestrate your infrastructure?

Your options

Platform engineers running AWX have five distinct operational paths. For a wider comparison of tools, see our guides to AWX alternatives and Ansible Tower alternatives.

OptionOperational EffortLicensing / CostSupport ModelArchitecture & Portability
1. Stay on AWX 24.6.1None initially; grows as base packages ageFree (Apache 2.0)None (community forum only)Frozen legacy deployment; unpatched CVEs
2. Wait for AWX releases to resumeUnknown: no release plannedFree (Apache 2.0)CommunityMicroservice-based; breaking deployment changes
3. Migrate to Ascender (CIQ)Low to moderate (direct AWX fork)Free (Apache 2.0) or paid ProCommunity or commercial SLA from CIQAWX-compatible controller; regular upstream releases
4. Red Hat AAPModerate (migration tooling provided)Commercial (per managed node)Enterprise SLA from Red HatOfficial commercial platform; automated installation
5. Decouple orchestration from playbooksModerate (reconfigure jobs as workflows)Open source or enterpriseCommunity or enterprise SLAStandard ansible-core execution; multi-tool control plane

Option 1: Stay on AWX 24.6.1

For teams with isolated network boundaries, low change frequency, and strict change freezes, continuing to run AWX 24.6.1 is technically possible, as long as platform engineers accept that security vulnerabilities in the web interface and API will remain unpatched.

Option 2: Wait for AWX releases to resume

Teams with deep investments in AWX-specific workflows can wait in case packaged releases return. Since the release pipeline was removed in November 2026, nothing indicates when or whether that will happen. If a build is tagged again, expect a full redeployment of the control plane: playbook code will remain compatible, but existing Helm charts, operator manifests, and integration configurations will need to be rebuilt.

Option 3: Ascender by CIQ

Ascender is an open-source project maintained by CIQ that derives directly from upstream AWX. It maintains an Apache 2.0 codebase while continuing to ship regular packaged releases, including version 25.6.3 in late October 2026.

Ascender provides an attractive bridge for organizations that require an actively maintained web console and REST API that mirrors AWX conventions. For regulated environments, CIQ offers commercial support under the Ascender Pro subscription.

Option 4: Red Hat Ansible Automation Platform

Organizations seeking an enterprise-backed product can migrate to Red Hat Ansible Automation Platform (AAP). AAP includes the commercial automation controller (the enterprise successor to Ansible Tower), Event-Driven Ansible, private automation hubs, and Red Hat technical support. AAP is licensed via annual commercial subscriptions based on the number of managed nodes in your inventory.

Option 5: Decouple orchestration from playbooks

A growing number of platform teams choose to separate the scheduling and orchestration layer from raw playbook execution. Because Ansible playbooks execute independently via ansible-core, teams do not need a dedicated Ansible-specific server to run their automation.

Modern declarative orchestrators coordinate ansible-playbook CLI executions inside isolated containers, while extending the workflow to include adjacent infrastructure systems. For example, declarative workflow engines like Kestra orchestrate Ansible with the Ansible plugin, running playbooks natively alongside Terraform scripts, database updates, HTTP webhooks, and manual approval gates.

This architectural pattern offers several practical benefits:

  • No playbook rewrites: Playbooks run without modification inside containerized task runners.
  • Unified control plane: Teams coordinate end-to-end operational pipelines that combine Ansible configuration with cloud provisioning, incident alerting, and container deployments across their infrastructure automation resources.
  • Predictable maintenance: Unlike specialized tools with stalled release cycles, general-purpose workflow engines adhere to scheduled release cadences and LTS policies.
  • Self-service workflows: Teams can expose automated runbooks with parameter forms, access control, and audit logs without managing a dedicated Django application stack through a unified infrastructure orchestration control plane.

What is AWX?

AWX is an open-source web application, REST API, and task engine designed to centralize and manage Ansible automation across teams. It provides role-based access control, visual inventory management, credential storage, graphical playbook execution logs, and scheduling mechanisms.

The project traces its lineage to Ansible Tower, a proprietary commercial management tool introduced in 2013. In September 2017, Red Hat open-sourced the underlying codebase under the Apache 2.0 license as AWX, positioning it as the rapid-release upstream project for Ansible Tower. When Red Hat later transitioned Tower into the automation controller component of Ansible Automation Platform, AWX remained the open-source community foundation until releases paused in 2024.


Sources

The factual assertions in this guide are drawn directly from the following public primary sources:

Terraform, Ansible and Kubernetes, orchestrated from one place.

Frequently asked questions

Find answers to your questions right here, and don't hesitate to Contact Us if you couldn't find what you're looking for.