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.
Here because a renewal quote just landed, the node count grew faster than the budget, or a contract is up and somebody asked what else is out there? That is the usual reason people arrive on this page, and it is the right moment to look.
AAP is the enterprise standard, and it's priced and deployed like one. Three things send teams looking for something lighter.
AAP is a subscription that meters by managed node, so the cost climbs with the fleet you automate. SwitchTender is source-available under BSL 1.1 and self-hosts free, with no per-node meter and no seat count to reconcile at renewal.
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.
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.
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're buying is Red Hat's support, certified content, and a name your auditors already trust, buy AAP. SwitchTender can't sell you a support contract. This page is for teams who want the capability without the subscription and the platform.
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 | Source-available, 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 |
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 for reaching segmented networks, and analytics through Insights. SwitchTender is new. Every claim on this page is backed by a test you can run, and what it doesn't have yet is the support desk, the certified content, or the years in production. What it does have is a plugin path: 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's the product, the footprint, and the bill.
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.
switchtender import awx controller-export.json --db switchtender.dbswitchtender import awx controller-export.json --db switchtender.db --applyThe 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.
The three asked most often when somebody is comparing this against what they already run.
No. It reaches the machines it manages over SSH, the same way Ansible does, and installs nothing on them. There is no per-host daemon to deploy, patch, or account for. You run the one server binary, and optionally a few more worker processes against the same store for throughput, which are pool members rather than agents belonging to a host.
All three, resolved at launch rather than copied into this database. Vault dynamic secrets go further: a short-lived credential is minted for each run and revoked when the run ends. AWS and Azure both authenticate from an instance role or managed identity with no stored key, and anything else resolves through a command whose output is the secret.
Yes, and it is what pipelines are for here. Steps mix tools freely on a dependency graph with parallel branches, built on a drag-and-drop canvas. The approval is not a convention somebody can skip: a policy decides which runs are held, the core enforces the hold, and the approval binds to the exact plan reviewed, so a run cannot be approved as one thing and executed as another.