Ansible Automation Platform: A Founder's Guide (2026)

I Tried to Buy the Enterprise Version of a Free Tool (For a Product With Zero Users)

Mid-2023. Clickly was a URL shortener with exactly no users, and I was deep in the Broken Engineer phase — learning every infrastructure tool a real company would need, for a product that didn’t need any of them. Kubernetes for a redirect service. Terraform for three imaginary VMs. And somewhere in that haze, Ansible — the free command-line tool that SSHes into servers and makes them match a YAML file.

I learned ansible-playbook. I pulled roles off Ansible Galaxy. I wrote YAML that installed nginx on a VM that didn’t exist. And then, because I’m me, I did the next logical thing: I went looking for the paid version.

Not “is there a paid version.” I knew there was one. I went looking for it because I genuinely thought I might need it. For a redirect service. With no users. On no servers.

That paid version is Ansible Automation Platform — AAP for short, formerly Ansible Tower — and for about a week I was trying to figure out if I should pay for it. I couldn’t find the price without booking a sales call, which should have been my first clue. But I was in too deep.

I want to save you that week. Here’s what AAP actually is, why half the internet still calls it “Ansible Tower,” what it does that the free CLI doesn’t, what it costs (you literally can’t see the price without talking to a rep), and then — like everything in this series — I’m going to talk almost all of you out of ever needing it.

---

Wait, This Was Called “Ansible Tower” (The Name Keeps Moving)

If you searched “Ansible Tower” and landed here — you’re in the right place, and you’re not behind. The name has shifted twice.

Ansible Tower was Red Hat’s commercial web UI for Ansible for years. Then Red Hat repackaged everything into one product called Ansible Automation Platform. Starting with AAP version 2, the piece that used to be called Tower got renamed automation controller. The Tower brand was retired. So when someone says “Tower,” they mean the thing now called automation controller, which lives inside the thing now called Ansible Automation Platform. Three names for the same lineage. Enterprise software does this to you.

There’s a free side to this story too. Back in 2017, Red Hat open-sourced the guts of Tower as AWX. AWX is the free, upstream, community version — automation controller is the supported, tested, downstream product built from it. Think Fedora → RHEL, same relationship. Keep AWX in your back pocket; it matters at the end.

---

What AAP Actually Gives You (On Top of Plain Ansible)

Plain Ansible is free. You write YAML describing what state a server should be in — “nginx installed, this config present, this service running” — and Ansible SSHes in and makes it true. You run it from your laptop or a CI job. It’s idempotent, costs nothing, and for a staggering number of teams it’s the entire toolchain. Nothing about AAP replaces that. AAP wraps a management layer around it.

That layer, as of AAP 2.5 in 2026, sits behind a single web console (Red Hat calls the front door the “platform gateway”). The important pieces:

• automation controller — the old Tower. Web UI, REST API, control plane. Playbooks become clickable “job templates.” Runs get logged and audited. You stop SSHing from a laptop to kick off automation.
• RBAC — role-based access control. This team can run the database playbook, that contractor can only view it, nobody touches production without the right role. This is the entire reason enterprises write the cheque.
• Job scheduling — run playbooks on a cron-like schedule with logging, retries, and notifications to email or Slack. “Patch every box at 2 AM Sunday and tell me if anything failed.”
• Credential management — SSH keys, cloud credentials, vault passwords stored centrally instead of scattered across ten laptops.
• Private Automation Hub — your own vetted, on-prem registry of certified collections (the paid, curated cousin of public Ansible Galaxy).
• Event-Driven Ansible — automation that fires off events (“disk filled up → run the cleanup playbook”) instead of a human clicking go.

Notice the pattern. Every single feature is about more than one person, and more than a handful of machines. Audit logs matter when auditors exist. RBAC matters when there’s a team. Central credentials matter when keys would otherwise live on ten laptops. AAP isn’t a better Ansible. It’s Ansible with governance, a control room, and a compliance story bolted on.

---

Where It Runs, and What It Costs

Two install paths: Red Hat Enterprise Linux (VM-based, traditional), or OpenShift (Red Hat’s Kubernetes, via an operator that deploys the whole platform with one click). The OpenShift route is supported on OCP 4.12 and up, and most new 2026 deployments land there — because if a company is big enough to buy AAP, it’s usually already running OpenShift somewhere. Both are firmly “we have a platform team” territory.

Now the part everyone actually wants. There is no public price. Red Hat doesn’t publish a list price for Ansible Automation Platform. You go to the pricing page, and it routes you to “contact sales.” That alone should tell a bootstrapper everything they need to know.

What we can piece together from third-party resellers and reported contracts: it’s a per-node annual subscription — you pay by how many machines (“managed nodes”) you’re automating — with tiers like Standard and Premium (Premium being 24×7 support, tighter compliance). Public reseller estimates float around $175 per node per year for Standard and roughly $250 for Premium. Reported real-world deals land anywhere from about $25,000 to over $250,000 a year depending on fleet size and support level. Treat those as ballpark, not gospel. The point isn’t the exact figure — it’s the shape. This is a five-to-six-figure enterprise line item negotiated with a sales rep, priced for organizations counting machines by the hundred.

For context: I was trying to run one redirect service that belonged on a $5 box. The smallest sensible AAP conversation starts at a number bigger than most bootstrapped SaaS make in their first year.

---

AWX — The Free Cousin Nobody Told You About

There’s a plot twist in this story that Red Hat’s sales page won’t highlight. Remember AWX, the open-source upstream I mentioned earlier?

AWX is the free, self-hosted version of the automation controller. You deploy its operator on a Kubernetes cluster, and you get the same web UI, the same job templates, the same RBAC — at $0. No per-node pricing. No sales call. No support contract.

The trade: you give up Red Hat’s certification, their 24×7 support, and the guaranteed stability of the downstream build. For enterprises with compliance requirements and SLAs, that’s a deal-breaker. For a solo founder? It’s barely a trade at all.

I’m not even saying you should run AWX. Most people reading this shouldn’t. But you should know it exists, because it changes the picture completely. The free ansible CLI gives you the automation. AWX gives you the dashboard. Between those two, you’re covered until you have a team, a fleet, and an auditor.

---

Why You (a Solo Founder) Need Exactly None of This

This is the part tutorials never say out loud. Ansible Automation Platform solves problems you get after you’ve won. Its features map one-to-one onto things a broke founder doesn’t have:

• RBAC solves “too many people can touch production.” You are one person. You’re the entire org chart.
• Audit logging solves “prove to the compliance officer who changed what.” You have no compliance officer. You have git history and a memory of last Tuesday.
• A web UI for playbooks solves “non-terminal teammates need to run automation safely.” Your teammate is you. You live in the terminal.
• Central credential management solves “keys are scattered across a team.” Your keys are on one laptop. That laptop is this laptop.
• The support contract solves “the business loses real money if automation breaks at 3 AM.” At $0 MRR, the business that breaks is a hobby, and the community forums answer for free.

And the biggest one: AAP configures fleets of servers. If your stack is Vercel for the frontend, Railway or Fly.io for the backend, and Neon for Postgres, you don’t have a fleet. You don’t have a server. There’s no box to bring into a described state, because your platform deleted the box. Paying a per-node automation platform when you own zero nodes is a special kind of Broken Engineer theatre — and yes, I laughed at exactly this version of myself.

The rule of thumb: you graduate to AAP when you have a team, a fleet of machines you own, and someone who says the word “compliance” in meetings. That’s a good problem — it usually means real headcount and real revenue. It is not a $0 MRR problem. If you genuinely run servers but it’s just you, learn the free ansible CLI and pull vetted roles from Ansible Galaxy; that’s the whole toolkit. If you outgrow the CLI and want a dashboard, self-host free AWX before you ever email a Red Hat sales rep.

---

The Layer They Sell, and the One You Actually Need

Ansible Automation Platform is Red Hat’s paid governance layer around Ansible. It gives big organizations a control room: a web dashboard, granular RBAC, scheduling, credential management, audit logs, and a support contract — running on RHEL or OpenShift, priced per node with no public list price, in deals that start in the tens of thousands a year. The free, open-source version of that dashboard is AWX. And the automation itself — the part that actually does the work — is the free ansible command-line tool that never needed any of this.

The real lesson isn’t the product. It’s that vendors sell governance separately from capability. Enterprises pay for AAP not because their servers won’t configure without it, but because their teams and auditors can’t be governed without it. You have neither yet. So the best enterprise automation platform for a broke founder is no platform at all: the free CLI when you have servers, a managed platform that hides the servers entirely when you don’t. I went shopping for the paid version of a tool I barely needed the free version of. Classic. Don’t be like me.

This is the Broken Engineer Guide. I over-engineer everything, fail at business, and write it down so you don’t have to. When you catch yourself shopping for a five-figure enterprise platform for your zero-user SaaS, close the tab. Go build something instead.