# Any news on AWX Development **URL:** \ **Category:** Get Help\ **Tags:** awx, ee\ **Created:** [April 6, 2026, 8:14pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639 "2026-04-06T20:14:48Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![rbooyer](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rbooyer/32/10629_2.png) [@rbooyer](https://forum.ansible.com/u/rbooyer)\ **Post date:** [April 6, 2026, 8:14pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/1 "2026-04-06T20:14:48Z")
Has anyone seen any news on the AWX Development process? I know it’s in a rebuild / redesign process but it has been two years without any news. Are there any alternatives to AWX that work well for ansible automation as I may need to investigate something else as the containers are getting very outdated and may not comply with our internal security audits for much longer. (operator / task / web pods not the ee as i can build an ee). I was just curious if there was any news or if the current recommendation would be to search for another solution to scheduling ansible automation. ---
**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\ **Post date:** [April 7, 2026, 8:37am UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/2 "2026-04-07T08:37:21Z")
Related topics: - [Streamlining AWX Releases](https://forum.ansible.com/t/streamlining-awx-releases/6894) - [Is there a future for AWX?](https://forum.ansible.com/t/is-there-a-future-for-awx/44527) - [AWX modernization: Moving forward](https://forum.ansible.com/t/awx-modernization-moving-forward/45134) [@gundalow said, “There will be updates soon,”](https://forum.ansible.com/t/awx-modernization-moving-forward/45134/18) but since that was 26 days ago, I’m not sure how soon “soon” actually is. ---
**Author:** ![jpmens](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jpmens/32/5543_2.png) [@jpmens](https://forum.ansible.com/u/jpmens)\ **Post date:** [April 7, 2026, 8:54am UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/3 "2026-04-07T08:54:39Z")
I have given up holding my breath for anything AWX related, and I have sadly also given up on believing in or trusting that “there will be updates soon”. While only AWX will give you everything AWX gave you, I hear quite good things from people using Semaphore UI, Jenkins (with Ansible plugins), and Rundeck (with Ansible plugins). ---
**Author:** ![kurokobo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kurokobo/32/182_2.png) [@kurokobo](https://forum.ansible.com/u/kurokobo)\ **Post date:** [April 7, 2026, 9:05am UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/4 "2026-04-07T09:05:56Z")
This might sound a bit on the pessimistic side: I get the impression that Red Hat’s main focus is more on enhancing AAP (the downstream product) than AWX itself. Although there are still active commits happening in the `ansible/awx` and `ansible/awx-operator` repository, it feels like many of them are side effects from work done to improve AAP. So even if the ongoing refactoring is completed, it may not necessarily mean that AWX, the AWX Operator, or various plugins will be released with versioned tags in a way that’s particularly easy for community users to adopt, such as with detailed documentation or streamlined deployment guides. It seems the priority for creating assets mainly for the community isn’t especially high right now. It looks like Red Hat’s motivation for investing in community support is gradually becoming less prominent compared to the value they get from the community’s feedback and contributions. Of course, it’s understandable for a company to focus on business goals, and this approach probably makes sense from that perspective. After all, having more free users doesn’t always translate directly into business benefits. I might be being overly pessimistic, but I hope the updates from the AWX Team will prove me wrong. ---
**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\ **Post date:** [April 8, 2026, 12:06pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/5 "2026-04-08T12:06:44Z")
Just the bread crumb that refactor was nearing completion. Typical Redhat behavior. No one can even get a working build since the last release almost 2 years ago ---
**Author:** ![Marcel\_Werner](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marcel_werner/32/4876_2.png) [@Marcel\_Werner](https://forum.ansible.com/u/Marcel_Werner)\ **Post date:** [April 10, 2026, 5:10pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/6 "2026-04-10T17:10:56Z")
Has anyone use [GitHub - ctrliq/ascender: Ascender provides a web-based user interface, REST API, and task engine built on top of Ansible. It is based off the upstream project of AWX. · GitHub](https://github.com/ctrliq/ascender) ? So it Looks Like awx with bugfixes? ---
**Author:** ![2and3makes23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/2and3makes23/32/1406_2.png) [@2and3makes23](https://forum.ansible.com/u/2and3makes23)\ **Post date:** [April 10, 2026, 5:55pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/7 "2026-04-10T17:55:09Z")
We are currently running our AWX-dev instance with Ascender images as a proof of concept. Generally it feels like how you describe it (less critical vulnerabilities due to more recent dependencies). One of the differences I noticed (besides the slightly modified UI theme): - Ascender did not apply the changes on RBAC introduced via the more recent AWX releases. In a way this makes sense, since it diverged from an earlier AWX release and even in the currently most recent AWX release (24.6.1) the RBAC improvements are not finalized (as in: there are still some quirks here and there ([#14657](https://github.com/ansible/awx/issues/14657)), the new RBAC API endpoints coexist next to the deprecated ones; I believe, both are still used by parts of the application) - This is not bound to be a deal breaker, since for migration to Ascender you have to export your AWX resources and import them on the other side anyways (due to DB scheme changes, probably introduced e.g. by more recent django versions etc.). - But I´m not certain about that. We have not made use of the most recet RBAC features (creation of fancy specialized roles etc.), yet, so my guess is, it would be no problem for us to migrate. - Migrating back would be export/import again, which we would develop a migration pipeline including reencryption of secrets (which by design are not exposed by AWX API and therefore not exported) We are considering the switch, because it´s rather manageable (to switch back as well) and it gives us time to think about different solutions, while being able to keep running AWX with less vulnerabilities. It goes without mentioning that of course this is less ideal than a working path to the most recent AWX versions used as AAP´s core. ---
**Author:** ![Klaas](https://avatars.discourse-cdn.com/v4/letter/k/ecc23a/32.png) [@Klaas](https://forum.ansible.com/u/Klaas)\ **Post date:** [April 11, 2026, 4:37pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/8 "2026-04-11T16:37:28Z")
we’ve been quite happy with using ascender instead of awx, having all config handy to redeploy via [GitHub - redhat-cop/infra.controller\_configuration: ansible collection for standardizing configuring AAP 2.4 and earlier · GitHub](https://github.com/redhat-cop/infra.controller_configuration) helped, we only had minor changes coming from awx 24.6.1 – also ascender happily takes PRs if there is something missing 🙂 ---
**Author:** ![Marcel\_Werner](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/marcel_werner/32/4876_2.png) [@Marcel\_Werner](https://forum.ansible.com/u/Marcel_Werner)\ **Post date:** [April 12, 2026, 8:57am UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/9 "2026-04-12T08:57:58Z")
Hi Klaas , thanks a lot for sharing . So actual we are using the awx.awx collection for controller automation . Not everything is possible but 80% are enouph for us. ---
**Author:** ![miguelsn](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/miguelsn/32/7054_2.png) [@miguelsn](https://forum.ansible.com/u/miguelsn)\ **Post date:** [April 15, 2026, 8:42am UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/10 "2026-04-15T08:42:06Z")
I wonder if anyone has experience with Oracle Linux Automation Manager (AWX packaged by Oracle). I am skeptical of Oracle continuing with the project. ---
**Author:** ![rbooyer](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/rbooyer/32/10629_2.png) [@rbooyer](https://forum.ansible.com/u/rbooyer)\ **Post date:** [April 22, 2026, 3:08pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/12 "2026-04-22T15:08:32Z")
On the ascender system i see mentioned. Can this run on standard k8s or is it just for k3s and the cloud systems listed in their install instructions. Has anyone installed it on just k8s before? Is there a cost to this or is the community edition available to those that do not have a budget for these systems. ---
**Author:** ![cigamit](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/cigamit/32/719_2.png) [@cigamit](https://forum.ansible.com/u/cigamit)\ **Post date:** [April 22, 2026, 4:22pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/13 "2026-04-22T16:22:21Z")
If you set the installer to k3s, but ensure kube\_install is set to false, it should deploy on standard k8s, as its just creating and applying basic manifests at that point. Its a fork of Open Source AWX, there is no cost unless you want commercial support. ---
**Author:** ![jwashburn](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jwashburn](https://forum.ansible.com/u/jwashburn)\ **Post date:** [April 30, 2026, 7:38pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/14 "2026-04-30T19:38:02Z")
We moved to OLAM because we already had Oracle licenses, so the cost was not an issue. OLAM has been around a while. The big difference is it runs on a server not K8s ---
**Author:** ![BoerBart](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/boerbart/32/10083_2.png) [@BoerBart](https://forum.ansible.com/u/BoerBart)\ **Post date:** [April 30, 2026, 9:51pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/15 "2026-04-30T21:51:01Z")
As far as Im aware of, OLAM is based on Ansible AWX, as in being (nearly) the same product, with small adjustments here and there for Oracle Linux. This would suggest that no licensing comes into play at any time, or am I wrong about OLAM? ---
**Author:** ![bvitnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bvitnik/32/4132_2.png) [@bvitnik](https://forum.ansible.com/u/bvitnik)\ **Post date:** [April 30, 2026, 11:21pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/16 "2026-04-30T23:21:38Z")
First time hearing about OLAM. I wasn’t aware Oracle made a fork of AWX. Thanks for sharing. I’ll have to give it a try. ---
**Author:** ![jwashburn](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jwashburn](https://forum.ansible.com/u/jwashburn)\ **Post date:** [April 30, 2026, 11:49pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/17 "2026-04-30T23:49:03Z")
The current version of OLAM is 2.3 and is based on 24.6.1. It is identical in everywhere except it runs on an Oracle Linux server instead of K8s. We have an Oracle Enterprise agreement, so I know its part of that. ---
**Author:** ![jwashburn](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jwashburn](https://forum.ansible.com/u/jwashburn)\ **Post date:** [April 30, 2026, 11:50pm UTC](https://forum.ansible.com/t/any-news-on-awx-development/45639/18 "2026-04-30T23:50:33Z")
![image](https://us1.discourse-cdn.com/ansible/original/2X/1/1957f99dec74eb73fb642973086f1d8584e4cd26.png) It has the penguin instead of the AWX logo 🙂