ARNIE is an operator, not a chatbot. It turns intent into real infrastructure changes — and it stops, every single time, to let a human approve before anything touches your cluster.
You don't hand-write YAML or memorize module syntax. Tell ARNIE what you want — "lock the staging database to the app subnet," "roll the ingress certs," "drain and patch worker three" — and it generates the exact Ansible playbook to do it. The intent is yours; the implementation is ARNIE's.
drain-patch-worker3.yml — 4 tasks. Review before it runs.This is the line ARNIE never crosses. Every generated change pauses at a human approval gate. You see the full playbook, exactly what it will touch, and you decide: approve, edit, or reject. There is no "auto-run," no silent execution, no surprises. Approval isn't a setting — it's the architecture.
restrict-payments-netpol.ymlOnce you approve, ARNIE doesn't just save a file. It pushes the playbook to Git, syncs it to Ansible Automation Platform, and AAP executes it against your real cluster. The change is versioned, run through your actual pipeline, and applied for real — then the result comes back to you in the chat.
ARNIE isn't locked to a single model. Route generation through the provider that fits — bring your own keys, switch between models, keep control of where your prompts go. The operator stays the same; the intelligence behind it is yours to choose.
Every request, every generated playbook, every approval, every execution and its result — recorded. When someone asks "who changed this, and why," the answer is already written down. ARNIE is built for the environments where that question gets asked.
Features are one thing. Watch how a sentence becomes live infrastructure, end to end.
How it works →