Prepare a job your team can run
Save the playbook, inventory, credential references and inputs in a Task Template. Share a consistent launch form and schedule recurring work.
Explore Task Templates →Keep your Ansible playbooks. Run Semaphore your way, from a standalone server to Kubernetes, and connect provisioning, configuration and scripts in one workflow.
Get regular updates, deploy on your terms and run Ansible alongside your other automation tools.
Semaphore continues to ship releases and security fixes. AWX’s public release pause complicates upgrades and security maintenance.
Use a binary, Linux package or Docker. Kubernetes is optional.
Connect Ansible, Terraform, OpenTofu and scripts across your cloud and on-premises systems in Workflows.
Host Semaphore and run PowerShell on Windows. Ansible needs a compatible runtime.
A simple web UI lets colleagues run jobs and review results without learning the platform inside out.
Add Pro or Enterprise capabilities and support, with custom roles and high availability in Enterprise.
Our migration tool helps transfer your existing AWX setup to Semaphore UI. Request access and discuss your migration with our team.
Former AWX users explain what changed with Semaphore: straightforward configuration, low resource use and less maintenance.
“We moved to Semaphore UI … AWX is very overcomplicated”
“I have been using AWX (open-source) in the past and I already love semaphore 1000x better.”
“Much more straightforward to configure and easy on resources than the first thing I tried for this, AWX.”
“I moved to Semaphore UI as AWX was not maintainable for my homelab.”
Keep your playbooks, prepare the jobs your team needs and connect the whole operation.
Save the playbook, inventory, credential references and inputs in a Task Template. Share a consistent launch form and schedule recurring work.
Explore Task Templates →Use runners with the network access and toolchain each job needs. Scale execution separately from the Semaphore web application.
Explore runners →Provision with Terraform, configure with Ansible and verify with Python. Pass outputs between jobs and add approvals or failure paths.
Explore Workflows →Tell us about your AWX setup and what you want to achieve. Talk to our team about migration options, planning the move or getting access to the migration tool.
Prefer email? Contact [email protected]
Your Ansible code is the starting point. The surrounding AWX configuration needs a deliberate transfer.
Reconnect Git repositories and retain your playbooks. Match Ansible versions, collections and Python dependencies before comparing results.
Map inventory sources and supported credential types. Test host discovery and secret resolution rather than copying AWX-specific plugins unchanged.
Rebuild the required sequence, shared outputs and approvals. Check who can run each operation and who may change its configuration.
Validate a representative job on non-production targets. Move schedules deliberately to avoid duplicate runs, with a rollback plan for production.
Semaphore UI runs Ansible playbooks from your repositories. Start with your existing code and verify its dependencies, variables, credentials and inventory in the new environment. AWX-specific configuration and integrations need their own review.
Yes. Use a separate pilot environment and non-production targets to validate the jobs you care about. Keep production scheduling in one place until you have agreed and tested the cutover.
The two products have different configuration and access models. Request the migration tool, review what it can transfer and validate the resulting jobs. Some AWX-specific configuration and integrations need to be rebuilt.
You can install Semaphore UI Community to evaluate core Ansible automation. Request the migration tool separately. Hands-on migration assistance is available with Enterprise.
Map inventory sources and credential types to the resources your Semaphore jobs use. Validate dynamic inventory, host access and secret resolution during the pilot. Do not assume that AWX-specific credential plugins or inventory behavior transfer unchanged.
Check the Ansible version, collections, Python dependencies and network access required by each job. Prepare the Semaphore server or runner accordingly. Validate container-based execution separately, including how its image and credentials are configured.
Semaphore Workflows connect Task Templates with dependencies, approvals and success or failure paths. Ansible can run alongside Terraform, OpenTofu and scripts. Rebuild and test the steps and shared outputs your operation needs. Workflow API access is available in Pro and Enterprise.
Share your AWX version, deployment model, representative jobs and requirements for inventory, credentials and execution. These details help the team respond to your tool-access request. Do not send passwords, tokens or private keys.
Requesting the tool gives you a way to obtain access to the migration tooling. Hands-on migration assistance is an Enterprise service. Talk to our team about Enterprise if you need help planning and carrying out the move.
Review deployment options, supported tools, access controls and commercial capabilities before planning your move.