Atera is presented as an Agentic AI platform for IT management, that offers a digital workforce of AI agents that proactively and autonomously support entire IT operations. Atera’s all-in-one IT management platform consolidates RMM, helpdesk, ticketing, and automation, so IT teams and MSPs can manage and protect infrastructure, automate tasks, and boost service quality by reducing downtime and improving SLAs. Atera boasts users among over 13K customers in 120+…
$139
per month per user
Ansible
Score 9.2 out of 10
N/A
The Red Hat Ansible Automation Platform (acquired by Red Hat in 2015) is a foundation for building and operating automation across an organization. The platform includes tools needed to implement enterprise-wide automation, and can automate resource provisioning, and IT environments and configuration of systems and devices. It can be used in a CI/CD process to provision the target environment and to then deploy the application on it.
If you want an extremely small, easy-to-install setup for your servers that manages your machine's IT part hassle-free and integrates with some amazing third-party tools at decent pricing, you should definitely go forward with Atera. However, the tool does have certain limitations on aspects like features and customization, so do check if Atera has those features you require before subscription or trial.
I'm going to say it is best suited for configuration management. Like I said, patching even with security, things of that nature. Probably less suited is hardware management, but Red Hat IBM/IBM has Terraform for that. So it's a trade off.
Debugging is easy, as it tells you exactly within your job where the job failed, even when jumping around several playbooks.
Ansible seems to integrate with everything, and the community is big enough that if you are unsure how to approach converting a process into a playbook, you can usually find something similar to what you are trying to do.
Security in AAP seems to be pretty straightforward. Easy to organize and identify who has what permissions or can only see the content based on the organization they belong to.
Better documentation of how all the options/parameters are meant to be used (when creating things like jobs, templates, inventories, etc)
More recommendations of best practices as far as the best way to organize job templates, workflows, roles. Much can be found on how to organize pure Ansible, but not so much for AAP specifically.
I have found some things that seem like they should be easy but are not possible. Things like moving a host from one inventory to a different inventory. As far as I know this is not possible and requires deletion and recreation. Maybe I just don't know how this could be done or don't understand the design decisions behind this?
As of right now, we have found nothing that can offer as many features as Atera does along with the affordability. They are doing monthly releases each month and not just making small changes (shared scripting library, chocolatey support, Install packages, Splashtop SOS support, Scheduled tickets to name a few). The uptimes are great and accessibility to the dashboard has yet to be limited. We are a happy customer and bordering on fanboy status now
Even is if it's a great tool, we are looking to renew our licence for our production servers only. The product is very expensive to use, so we might look for a cheaper solution for our non-production servers. One of the solution we are looking, is AWX, free, and similar to AAP. This is be perfect for our non-production servers.
Atera has a user-friendly interface that improves navigation. Support staff can quickly access real-time alerts and remote devices and manage tickets without much training. Atera’s usability has positively impacted our organization by increasing operational efficiency and improving response times to resolve issues.
It's overall pretty easy to use foe all the applications I've mentioned before: configuring hosts, installing packages through tools like apt, applying yaml, making changes across wide groups of hosts, etc. Its not a 10 because of the inconveinience of the yaml setup, and the time to write is not worth it for something applied one time to only a few hosts
Great in almost every way compared to any other configuration management software. The only thing I wish for is python3 support. Other than that, YAML is much improved compared to the Ruby of Chef. The agentless nature is incredibly convenient for managing systems quickly, and if a member of your term has no terminal experience whatsoever they can still use the UI.
Atera support provides answers to my questions lightning fast. They have never left me feeling like I'm out there on my own. I can ask questions by email, or by chat, or by opening a ticket with them and they are always on it quickly. They also have a forum where other Atera users can help you if you need it, and you can also add feature requests via the forum.
There is a lot of good documentation that Ansible and Red Hat provide which should help get someone started with making Ansible useful. But once you get to more complicated scenarios, you will benefit from learning from others. I have not used Red Hat support for work with Ansible, but many of the online resources are helpful.
Because Atera is a much more effective and efficient solution to manage all our IT operations, it automates each of our business processes. It offers us the best support to respond to any problem that may arise. I think Atera is much more cost-effective and reliable; its value is justified with each function and satisfies all our business needs and requirements.
I used puppet prior to moving to open source Ansible and eventually to Red Hat Ansible Automation Platform. I appreciate the agentless approach of Red Hat Ansible Automation Platform and feel that its deterministic approach to applying code is superior to puppet
The intuitive user interface has enabled both users and support technicians to familiarize themselves quickly with the functionality, and the learning curve is less.
Some features need to be accessed through documentation; they're not available directly on the dashboard.
Sometimes, internet access plays a significant role, whereas low connectivity is a hindrance.
POSITIVE: currently used by the IT department and some others, but we want others to use it.
NEGATIVE: We need less technical output for the non-technical. It should be controllable or a setting within playbooks. We also need more graphical responses (non-technical).
POSITIVE: Always being updated and expanded (CaC, EDA, Policy as Code, execution environments, AI, etc..)
