The full review
What is Ansible?
Ansible is an open source IT automation engine. Red Hat describes it as automating provisioning, configuration management, application deployment, orchestration, and many other IT processes. The model is a readable description of the desired state of the system, which Ansible then reconciles the managed machines to match.
The name covers two things: the upstream open source project, home to Ansible Core and the community collections on Ansible Galaxy, and Red Hat Ansible Automation Platform, the supported enterprise product headlined Automation for the enterprise. Engineered for all. The ansible.com domain now redirects to redhat.com, where both live.
The agentless model
The defining design choice is that there is no agent. Red Hat states that Ansible communicates with devices without requiring an application or service installed on the managed node, using OpenSSH for transport with other transports and pull modes as alternatives. Instead of a resident daemon, Ansible pushes small programs it calls modules, written as resource models of the desired state of the system. That erases a category of toil: no agent fleet to install, patch, or debug when it quietly dies.
The paid platform is where Ansible stops being a laptop tool. Automation controller acts as the control plane for defining, operating, and delegating automation across an organization. Automation mesh extends runs across diverse network topologies, which matters when an estate spans data centers, clouds, and edge sites. Automation execution environments package dependencies into container images so a playbook behaves identically everywhere it runs. Ansible Content Collections bundle modules, playbooks, plugins, and roles, and Ansible automation hub is the central repository for finding and managing them.
Event-driven runs and AI assistance
Event-Driven Ansible is the piece worth understanding if you still trigger automation by hand. It lets teams define rule-based constructs so incoming events fire the right playbook without a human in the loop, turning Ansible from a deployment tool into a remediation layer. Red Hat also ships an automation coding assistant that generates YAML from natural language prompts, plus an automation intelligent assistant, a chat interface inside the platform UI. Red Hat Lightspeed for Automation adds visibility across the platform infrastructure itself.
Bringing non-engineers into automation
Ansible has historically been a tool for people comfortable in a terminal, and several platform components are aimed squarely at users who are not. The self-service automation portal extends automation to a broader set of users through a point-and-click interface with step-by-step smart forms, so a service desk technician can run a vetted job without touching YAML. Ansible plug-ins for Red Hat Developer Hub add a custom portal experience with guided learning, while the automation dashboard and automation analytics give managers performance and ROI visibility.
Ansible without a subscription
The free path is genuinely usable. Ansible Core, the engine itself, stays open source, and the Ansible Collaborative is the gathering space Red Hat maintains around it: Ansible Galaxy for collections, an Ansible Community Forum for questions, community training, and interactive labs. Development tools such as ansible-navigator and ansible-builder ship openly, as does the Ansible Rulebook syntax behind Event-Driven Ansible. A small team can automate a real infrastructure estate for years without opening a purchase order.
Who should choose Ansible
Ansible suits infrastructure and platform teams managing heterogeneous fleets, especially anyone tired of maintaining agents. Network, cloud, and security teams get the most from the paid platform, where automation controller, automation mesh, and analytics justify the subscription through governance rather than raw capability. Start with Ansible Core, prove the playbooks, then move to a Standard or Premium subscription when audit trails and support hours become the real constraint.
It is a weaker fit for small teams running a handful of uniform servers, where a shell script and cron already do the job, and for buyers who want transparent self-serve pricing, since the enterprise tiers are quote-only and route through sales.
Strengths
- Ansible Core is genuinely free, open-source, and unlimited-node
- Agentless: no software to install on managed hosts, just SSH/WinRM
- Human-readable YAML playbooks with a gentle learning curve
- Massive module/collection ecosystem via Ansible Galaxy
Watch out for
- Red Hat AAP pricing is quote-based and opaque; no public list price
- Enterprise features (web UI, RBAC, analytics) require paid AAP or self-run AWX
- Can be slow at very large scale vs push-based or agent tools
- Control node runs on Linux/macOS/WSL, not natively on Windows
Key features
| Feature | What it does |
|---|
| Agentless architecture | Connects over SSH (Linux) or WinRM (Windows) with no agent or daemon required on target hosts. |
| YAML playbooks | Automation is defined in declarative, human-readable YAML that is easy to version-control and review. |
| Idempotency | Playbooks describe desired state and only make changes when needed, so re-runs are safe. |
| Automation Controller (AAP) | Web UI, REST API, role-based access control, job scheduling and centralized credentials in the paid platform. |
| Content Collections & Galaxy | Thousands of community and certified modules/roles for clouds, network gear, containers and more. |
| Automation Analytics & policy (AAP) | Fleet-wide reporting, health insights and event-driven automation in the enterprise subscription. |
How Ansible compares
| Alternative | How it differs |
|---|
| Terraform | IaC provisioning (IBM/HashiCorp). Complementary rather than rival: Terraform provisions infra, Ansible configures it; often used together. |
| Puppet | Agent-based, model-driven config management with a Ruby DSL. More mature at compliance drift enforcement but steeper setup. |
| Chef (Progress) | Ruby-based, code-heavy config management with agents. Powerful but a bigger learning curve than Ansible's YAML. |
Frequently asked questions
Is Ansible free?
Yes. Ansible Core, the open-source automation engine, is free under the GPLv3 license with no node limits and no cost. You only pay if you choose Red Hat Ansible Automation Platform (AAP) for a web UI, RBAC, analytics and official support. The community AWX project is also free but unsupported.
How much does Ansible cost?
Ansible Core costs $0. Red Hat's paid Automation Platform is quote-based per managed node; Red Hat publishes no list price. Reseller MSRP for a Standard 100-node yearly subscription (SKU MCT3691) is about $13,000, roughly $130 per node per year. Third-party estimates put ~100 nodes at $10,000-$20,000/yr.
What is the difference between Ansible Core and Ansible Automation Platform?
Ansible Core is the free command-line engine that runs playbooks. Ansible Automation Platform (AAP) is the paid Red Hat subscription that wraps that engine with a web console (Automation Controller), role-based access control, credential management, automation analytics, certified content and 9-5 or 24x7 support with SLAs.
Ansible vs Terraform: which should I use?
They solve different problems and are often paired. Terraform provisions infrastructure (create servers, networks, cloud resources) using declarative state. Ansible configures and manages what's already running (install packages, deploy apps, enforce settings) and is agentless. Many teams use Terraform to build and Ansible to configure, so it's rarely either/or.
Is Ansible owned by Red Hat or IBM?
Ansible was created by Michael DeHaan and acquired by Red Hat in 2015; Red Hat itself was acquired by IBM in 2019. So Ansible is a Red Hat (IBM) product today. The open-source Ansible Core project remains free and community-driven, while Red Hat sells the commercial Ansible Automation Platform on top of it.
Ansible ratings on other platforms
Independent user ratings from third-party review sites, linked here for transparency.
These are not our editorial score, are captured on the date shown, and may have changed since.