Red Hat Ansible Automation Platform bundles automation controller (formerly Ansible Tower), Event-Driven Ansible and private automation hub under quoted subscriptions. Pages here cover replacing it with self-hosted AWX or Semaphore UI.
Red Hat's supported platform against its upstream: what AWX shares with automation controller, what AAP adds (certified content, Event-Driven Ansible, private automation hub, 18-month support), AWX's paused releases and community-only support, and the operator-based install AWX needs.
AAP against Semaphore UI, an MIT licensed web interface for Ansible, OpenTofu and scripts: projects, inventories and schedules, what Semaphore's Pro and Enterprise editions add (LDAP, OIDC, project runners, HA), and where it falls short of automation controller at scale.
Moving job templates, inventories, credentials and schedules from automation controller to AWX: installing with the AWX Operator, exporting and re-importing objects with the awx CLI, replacing certified collections and automation hub, and planning around AWX's paused releases.
Moving playbook runs from AAP to Semaphore UI: recreating projects, inventories, key stores and task templates, replacing RBAC, surveys and schedules, choosing community or Pro features such as LDAP and project runners, and running both in parallel during cutover.
Cost of ownership by component: quoted AAP subscriptions with Standard or Premium support, against free AWX or Semaphore UI Community, Semaphore Pro from $20 a month, the hosting and Kubernetes they need, migration, and the support you take on yourself.
AWX has published no release since 24.6.1 in July 2024 while it is refactored, and Red Hat offers no paid support for it. This page weighs running AWX anyway, moving to Semaphore UI, or staying on AAP, and what to watch before committing.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.