# AWX modernization: Moving forward

**URL:** <https://forum.ansible.com/t/awx-modernization-moving-forward/45134>\
**Category:** Project Discussions\
**Tags:** community, awx-modernization, awx\
**Created:** [January 20, 2026, 9:38am UTC](https://forum.ansible.com/t/awx-modernization-moving-forward/45134 "2026-01-20T09:38:58Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**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:** [January 26, 2026, 10:30am UTC](https://forum.ansible.com/t/awx-modernization-moving-forward/45134/13 "2026-01-26T10:30:40Z")

</div>

Yay - We are very much looking forward to documentation for contributing and deploying AWX in its refactored state moving forward!

> We want to make it much easier to contribute to AWX and create [customizable AWX builds](https://forum.ansible.com/t/awx-ui-and-credential-types-transitioning-to-the-new-pluggable-architecture/8027#p-20376-customizable-awx-build-4) as we’ve been saying from the very beginning.

> we want to make it really simple and straightforward for developers to spin up environments and start working with the new plugin architecture

🥳

The two most important things for us:

- Consistent Deployments of AWX (like 24.6.1 used to be: incl. UI, User Authentification/Authorization, Credential Types, etc.)
- Being able to run, test, contribute features and bugfixes

---

_[View the full topic](https://forum.ansible.com/t/awx-modernization-moving-forward/45134)._
