Your engineers still log in to servers one at a time. The change should be written once and pushed everywhere — Red Hat Ansible Automation Platform pushes configuration, patches and network changes without agents — self-managed on RHEL or OpenShift, as a managed application in your cloud, or as a Red Hat service.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
This page covers Red Hat Ansible Automation Platform — all three deployment models. The rest:
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
Automation that reaches each system over its existing access, with no agent installed there first; Ansible works this way.
What consolidation actually replaces, dimension by dimension.
| Dimension | Hand-run scripts over SSH | Red Hat Ansible Automation Platform |
|---|---|---|
| Making a change | An engineer logs in to each server in turn | One run pushed to every managed node at once |
| Reaching new kit | Install and maintain an agent first | Agentless: reachable means automatable |
| Who can run it | Only the person who wrote the script | Others launch it from the self-service portal |
| Where it runs | A jump box under someone’s desk | Self-managed, your cloud, or a Red Hat service |
| Support when it breaks | A forum thread and a hope | Standard 9 am–5 pm or Premium 24x7 from Red Hat |
| What it is NOT | — | A published price, or a provisioning-state engine like Terraform |
The cheapest test is one job: automate monthly Linux patching on a test group and compare the hours against last month.
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Installed on RHEL 8.3 or later, on Red Hat OpenShift, or bought through the AWS, Azure and Google Cloud marketplaces, then patched and backed up by your own team.
The platform sits inside a cloud account you own, so the automation runs next to your workloads while the day-to-day running of the platform is handled for you.
Red Hat operates the platform as a service; check where it is hosted before regulated inventory or credentials go in, since no Indian location is documented.
Ansible Lightspeed intelligent assistant reached GA on AAP 2.6 on OpenShift, and a self-service automation portal reached GA as part of the subscription.
One agentless automation platform, three homes — your own servers, a managed app in your cloud, or a Red Hat-run service.
Red Hat Ansible Automation Platform turns one-off admin work into automation anyone on the team can run, with no agent on the targets.
Changes are pushed to each managed node over its existing access, so a new server needs no agent before automation can reach it.
One platform for standard configuration, patch runs and network change across Linux, Windows and network devices after they are built.
The self-service automation portal, GA in 2.6 and part of the subscription, lets people launch automation that others wrote for them.
Run it on RHEL 8.3 or later or on OpenShift in your own data centre, so inventories and credentials never leave your hardware.
Ansible Lightspeed intelligent assistant is GA on AAP 2.6 on OpenShift; whether it is billed on top of the subscription is unconfirmed.
Red Hat’s own material pairs Ansible with HashiCorp Terraform, another IBM product: Terraform builds the resources, Ansible shapes them.
Red Hat’s own videos: the 2026 roadmap, a platform explainer, the team-automation case, and how Ansible and Terraform work together.
Red Hat’s own 2026 roadmap for the platform; treat anything described as future work as a plan, not a feature you can buy today.
A short Red Hat introduction to what the platform adds around Ansible; it predates version 2.6, so the portal and Lightspeed are not in it.
Red Hat’s case for automating as a team rather than script by script, from the 2.x era before the current release.
Red Hat’s view of the two tools as partners — Terraform to create cloud resources, Ansible to configure them — useful now that IBM owns both.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Here’s what genuinely sets it apart — and exactly where it stops.
Ansible reaches managed nodes without an agent installed on them first. A freshly built Linux host, a Windows server or a switch can be brought into automation as soon as it is reachable, and there is no agent fleet of its own to upgrade, monitor and troubleshoot every quarter.
Run it self-managed on RHEL 8.3 or later or on OpenShift, take the managed application inside your own cloud account, or let Red Hat run it as a service. AWS, Azure and Google Cloud marketplaces sell the self-managed route, so an existing cloud commitment can carry the purchase.
Version 2.6 made the self-service automation portal generally available inside the subscription. The people who write automation publish it once; service desk and application teams launch it from the portal instead of asking an engineer to log in and run the same change by hand again.
There is no published price; Red Hat sizes every quote, so get the counting unit in writing. Lightspeed is GA on OpenShift, but whether it costs extra is unconfirmed. Provisioning state is Terraform’s job, not Ansible’s. No Indian location is documented for the managed service. No analyst placement is cited here.
List the servers, network devices and recurring changes in scope, and mark which ones are still done by hand each month.
Choose self-managed on RHEL or OpenShift, a managed application in your cloud, or the Red Hat service, against your data rules.
Take a single recurring job, such as monthly Linux patching, write it once, run it on a test group, then on a real one.
Ask Red Hat which count the quote uses, how short-lived test machines are treated, and whether Lightspeed is extra.
Publish the proven jobs in the self-service portal, retire the matching runbooks, and add network devices in a second wave.
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
“We brought 300 branch switches under one playbook run without touching a single device to install anything first.”
“Monthly Linux patching used to eat a full weekend. Now it is one scheduled job and a report on Monday morning.”
“The service desk now restarts stuck app services from the portal. Our on-call engineers noticed the quiet first.”
“Ask how nodes are counted before you sign. Our first quote included test VMs that only lived for a day.”
“Terraform builds our cloud accounts and Ansible hardens every VM after. Owning both under IBM made that easy to justify.”
“We kept the controller on OpenShift in our own data centre because the auditors wanted credentials on our hardware.”
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the IT automation market — tap any vendor to see why it sits where it does.
Execution strength vs product vision — the classic market map, minus the paywall.
Version 2.6; self-managed, in your cloud or Red Hat-run; quoted.
The grid nobody publishes — how many places the tool can run vs how many kinds of system it can change.
Three deployment models; Linux, Windows and network gear.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Against HashiCorp Terraform, Broadcom Automic Automation, Infoblox NetMRI, Action1 and Fortinet FortiManager — on what each automates, deployment, price, AI, governance, support and India.
| Dimension | Red Hat Ansible Automation Platform | HashiCorp Terraform | Broadcom Automic Automation | Infoblox NetMRI | Action1 Patch Management | Fortinet FortiManager |
|---|---|---|---|---|---|---|
| What it is | Agentless automation | Provisioning as code | Workload automation | Network config manager | Cloud patching | Fortinet-only console |
| Deployment | Self, your cloud or SaaS | CLI, HCP or Enterprise | On-prem, K8s or SaaS | Appliance, VM or AWS | Cloud console only | Appliance, VM or cloud |
| What it automates | Linux, Windows, network | Cloud resources | Jobs, mainframe to cloud | Network devices | Endpoint patches | Fortinet devices only |
| How it reaches targets | Agentless push | Provider APIs + state | Engine plus agents | SNMP, CLI and scripts | One agent per endpoint | Native, plus REST API |
| Pricing model | Subscription by sizing | Per managed resource | Quote, unit unpublished | Per appliance licence | Per endpoint, quoted | By managed devices |
| Published entry price | Not published | $0.10 per resource | Not published | Not published | Free to 200 endpoints | Not published |
| Release and licence | AAP 2.6 | BUSL since v1.6 | V26, April 2026 | 7.6.x; run 7.6.1+ | Cloud-delivered | Not stated here |
| AI assistance | Lightspeed; cost unclear | None graded | AI jobs, MCP, assistant | None documented | Policy, not AI | None described |
| Scale published | No ceiling stated | 500 free resources | 100,000 agents | Set by the licence | 1,000+ goes Enterprise | Up to thousands |
| Governance and approvals | Self-service portal | Sentinel or OPA | SLAs and calendars | Approval + compliance | Rings and pilots | ADOMs for tenants |
| India data location | Yours when self-managed | HCP unverified | SaaS in US and Europe | Self-hosted, yours | Promised, not live | Yours on appliance or VM |
| Support | 9–5 or 24x7 | Tiers not published | Five years a version | Trivandrum centre | Community on free | Through partners |
| Lock-in and exit | Leans on Red Hat | OpenTofu as the exit | XML export | Scripts stay yours | Swap one agent | Fortinet estates only |
| Best fit | Mixed estates, day 2 | Cloud build-outs | Cross-platform batch | Network compliance | Lean patching teams | All-Fortinet networks |
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Red Hat Ansible Automation Platform is one of 35 developer tools products TechBag carries. The Developer Tools guide narrows them to a shortlist and shows the reasoning. →
Drag the sliders (servers and network devices you automate; engineer-hour cost). Estimates model engineer time spent logging in to make configuration changes and run patches at an assumed 1.5 hours per managed system a year, with 70% of it removed by automation written once and pushed everywhere. Both figures are assumptions, and the subscription has its own cost. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Not published: Red Hat says Ansible Automation Platform pricing varies with your sizing, so every subscription is quoted, with Standard support (9 am–5 pm) or Premium (24x7). It runs self-managed on RHEL 8.3 or later or OpenShift, through the AWS, Azure and Google Cloud marketplaces, as a managed application in your cloud, or as a Red Hat service. Whether Lightspeed is extra is unconfirmed. TechBag counts your estate first, then quotes in INR with GST.
Best when data must stay on your servers
Best for a broader rollout
Best when you would rather not run it
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Tell us your requirements and current tools — we’ll model it against what you spend today.
Take this into your next vendor call — including ours.
How many servers and network devices would the platform manage, and which recurring changes are still done by hand?
Which count is Red Hat’s quote built on, and how are short-lived test and build machines treated in it?
Will it run self-managed on RHEL or OpenShift, as a managed application in your cloud, or as Red Hat’s service?
Do your change windows fall outside 9 am to 5 pm, so that Premium’s 24x7 cover is worth paying for?
Is the Lightspeed intelligent assistant included in your subscription, and do you run OpenShift, where it is GA?
Do you also provision cloud resources with Terraform, and who owns the line between building and configuring?
Must inventories and credentials stay in India, which points to a self-managed install on your own servers?
Which teams outside operations would launch automation from the portal, and who approves what they can run?
Count the servers and devices you would automate first, or let a TechBag advisor scope a pilot that automates one recurring change end to end.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.