# Is there a future for AWX?

**URL:** <https://forum.ansible.com/t/is-there-a-future-for-awx/44527>\
**Category:** Get Help\
**Tags:** awx\
**Created:** [September 22, 2025, 1:30pm UTC](https://forum.ansible.com/t/is-there-a-future-for-awx/44527 "2025-09-22T13:30:56Z")\
**Posts on this page:** 1\
**Showing post:** 78

<div class="post-metadata">

**Author:** ![Nico\_Kadel-Garcia](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nico_kadel-garcia/32/9998_2.png) [@Nico\_Kadel-Garcia](https://forum.ansible.com/u/Nico_Kadel-Garcia)\
**Post date:** [October 10, 2026, 10:54pm UTC](https://forum.ansible.com/t/is-there-a-future-for-awx/44527/78 "2026-10-10T22:54:29Z")

</div>

It wasn’t easy to activate if you did not trust ‘pip intall’ to correctly install secured or securable versions of the _massive_ and never RHEL published tree of python interdependent modules. mrmeee tried to RPM bundle hem but seems to have given up. I’m afraid the casual use of bleeding edge modules and their inherently unstable dependency trees makes casually bundling and deploying AWX risky, especially without tagged releases in several years. Since Red Hat is not “eating its own dog food” by RPM bundling even those python dependencies, not even in Fedora, it makes me very leery of having to hand-bundle and security scan all the [pypi.org](http://pypi.org) published dependency chains.

Others may be more trusting of ‘pip install’, but some very painful experience with JPackage and CPAN and even old BSD based ‘make install’ operations leaves me far less confidence of such dynamic compilation and deployment tools.

---

_[View the full topic](https://forum.ansible.com/t/is-there-a-future-for-awx/44527)._