The per-node bill
AAP is a subscription that meters by managed node, so the cost climbs with the fleet you automate. SwitchTender is open source under BSL 1.1 and self-hosts free, with no per-node meter and no seat count to reconcile at renewal.
Everything AAP governs.
Without the subscription.
Red Hat Ansible Automation Platform is the full enterprise Ansible stack: Automation Controller, private Automation Hub, Automation Mesh, Event-Driven Ansible, and a support contract. It is also priced per managed node and stands up on OpenShift or RHEL with Postgres before the first playbook runs, and Ansible is the only tool it runs. SwitchTender is one Go binary. Download it, run it, and you have job templates, schedules, RBAC, surveys, SSO, workflows, and approvals, plus a live host-by-task matrix and seven tools instead of one. Your Controller export imports in one command.
Why teams weigh a lighter option
AAP is the enterprise standard, and it prices and deploys like one. Three things send teams looking for a lighter path.
The platform to stand up
A supported AAP install means OpenShift or a RHEL fleet, Postgres, and the platform's own operators, then keeping all of it patched. SwitchTender is one process and one file. Upgrading is replacing a binary.
Ansible only
AAP automates Ansible. Real fleets also run Terraform, scripts, and one-off tooling. SwitchTender runs Ansible, Terraform, OpenTofu, Bash, PowerShell, Python, and Go through one engine, one UI, and one audit trail, each with a dry-run mode.
What AAP gets right
An honest page beats a loud one. AAP is the mature, certified, fully supported enterprise Ansible platform. Red Hat backs it with an SLA and a phone number, ships certified content and Event-Driven Ansible, and has a decade of production deployment behind it. If what you are buying is Red Hat's support, certified content, and a name your auditors already trust, AAP delivers it and SwitchTender does not pretend to be a support contract. This page is about the other axis: whether you want that capability without the subscription and the platform.
Feature for feature
The enterprise checklist, side by side. The full three-way table including AWX and Semaphore is on the comparison page.
| Capability | SwitchTender | Ansible Automation Platform |
|---|---|---|
| Deploy | One binary, SQLite or Postgres | OpenShift or RHEL + Postgres |
| Model | Open source, self-host free | Per managed-node subscription |
| Commercial support and SLA | Community and SDK | |
| Tools | Ansible, Terraform, OpenTofu, Bash, PowerShell, Python, Go | Ansible only |
| Live host-by-task matrix | ||
| Job templates, surveys, schedules, workflows | ||
| RBAC, teams, organizations | ||
| LDAP, SAML, OIDC sign-in | ||
| Private collections hub | Galaxy or Automation Hub, token | |
| Execution environments | All seven tools, Docker or Podman | Ansible only, Podman |
| Reach isolated networks | Outbound worker relay | Automation Mesh, multi-hop |
| Event-Driven Ansible | ||
| High availability | Active-active on Postgres | Via the platform |
| Duration-balanced job splitting | Round-robin slicing | |
| Fleet memory: flaky hosts, trends | ||
| Tamper-evident, signed audit | ||
| Drift detection and reconcile, Ansible and Terraform | ||
| Advisory AI triage and fleet answers | ||
| Drop-in Go plugins: tools, secrets, AI, notifiers | ||
| Import from the other side | One command |
Where AAP is still ahead
AAP is a decade of enterprise Ansible with Red Hat behind it: a support desk with an SLA, certified content you can point an auditor at, Event-Driven Ansible, a multi-hop Automation Mesh built for reaching deep into segmented networks at scale, and analytics through Insights. SwitchTender is new. Every claim on this page is backed by a test you can run, and what it does not have yet is that support desk, that certified-content ecosystem, or that decade of production miles. It closes the gap differently: any team can add a tool, a secret engine, an AI provider, or a notification channel as a drop-in Go plugin binary, no fork and no rebuild of the server. Pick AAP when the deciding factor is Red Hat support and certified content. Pick SwitchTender when it is the product, the footprint, and the bill.
Move in one command
Automation Controller is AWX's data model, so its export imports into SwitchTender the same way AWX's does. Projects, inventories, templates, surveys, and schedules come across, with a dry run first so you see the plan before anything is written.
-
1
Preview the import
switchtender import awx controller-export.json --db switchtender.db -
2
Apply it
switchtender import awx controller-export.json --db switchtender.db --apply
The switching guide maps every Controller concept to its SwitchTender equivalent, and the migration reference covers the details. Weighing the community edition instead? The AWX alternative page and the Ascender alternative page make those cases.