No more typing reviews! Try our Samantha, our new voice AI agent.

Automic Continuous Delivery Director [EOL] vs Nolio Release Automation comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Automic Continuous Delivery...
Average Rating
8.0
Number of Reviews
5
Ranking in other categories
No ranking in other categories
Nolio Release Automation
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
51
Ranking in other categories
Release Automation (7th)
 

Featured Reviews

Umair (Abu Mohaymin) Akhlaque - PeerSpot reviewer
Group CEO at Flexsolutions
An automation solution to automate the entire release process but lacks development
Automic eliminates a lot of error mishandling. If implemented, it can save a significant amount of money. It requires a substantial investment upfront because it eliminates the need for manual intervention in each process or job. Essentially, an operator oversees the releases, ensuring they are ready for release without needing to understand the intricacies of the process. This streamlines the release process and allows for monitoring at every step, reducing manual errors and providing automation, as the name "Automic" suggests. Automic offers a wide range of out-of-the-box integrations, available through its marketplace. This includes monitoring tools, release processes, and various other tools, making it a comprehensive solution.
Akhilesh B N - PeerSpot reviewer
DevOps Delivery Engineer at Barclays Capital
Real-time monitoring and seamless integration enhance deployment efficiency
The main disadvantage I see is the limited awareness of Nolio Release Automation in other organizations. It is a very nice tool, but its market presence is limited. I heard from the organization that the licensing cost was somewhat expensive. Perhaps focusing on marketing efforts would be beneficial. It is a really nice tool, and I am unsure why many organizations are not using Nolio Release Automation. It is one of the greatest tools for continuous deployment, yet its popularity remains limited. Some organizations are not aware of its existence. This might be an area worth researching and potentially developing new marketing strategies.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It's the simplicity; it's very simple to use and deploy and deliver, and it works."
"The most valuable features of Automic Continuous Delivery Director are the UI, release planning, and tracking, and you can do your soft and hard freeze through CDP."
"CDD is primarily used for showing end users (managers, business teams, project managers, and release managers) what is happening with each release. The status and reporting features are very important. Automation reduces time to deploy. It also allows us to do more with releases and testing prior to production, better guaranteeing a smooth deployment."
"The most valuable feature is the thorough coordination of software delivery across multiple environments, where multiple actors (typically business stakeholders, devs and ops engineers, release engineers, testers, and change managers) can easily cooperate to ensure a proper and repeatable delivery by combining constant follow-up on manual and automated activities."
"The most valuable feature for me is the fact that you can easily design a pipeline to promote applications from a development environment up to a production environment, and the team can become autonomous in designing those pipelines."
"Its ability to automate release deployments, streamline release scope, and reduce the cost of and time for deployment."
"The second valuable aspect is its capability to drive external systems like deployment automation engines or to integrate with Agile Central."
"Its extensive range of available connectors eliminates the need for manual code writing when implementing solutions, thus reducing coding efforts."
"Our requirement was to deploy to 300 servers which used to take two to three days before CA RA, now it takes only two to four hours."
"Deployment workflows has not only increased the confidence in the release process, but also opens up a whole new world to automate the deployment for not just code, but DB, network appliances, application servers, and AWS."
"The release time has gone down from a number of days to a few minutes."
"Usability – it’s good for developers who are both technical and non-technical."
"It’s an enterprise-class continuous delivery solution that takes release automation to the next level, providing an agile and collaborative application delivery chain."
"Before LISA RA implementation, the developers request for a restart would, for instance, take two to three days, with LISA RA, we developed a process where the restart is done within 10-15 minutes, and this process is used 15-20 times a day, from Monday to Friday."
"Ability to maintain the maps of different environments in a single tool."
"We previously used a different solution, and CA Release Automation really makes life easier as follows: it has a large number of available actions, deployment pipeline and approval gateway features that increase security to the deployment flow, and it integrates with service desk tools."
 

Cons

"We have rolled out the SAFe model, but what we would like to have is better integration with Agile Central, for instance, or at least at the plugin level, where we would select only certain stories instead of many stories in the sprint."
"Automic Continuous Delivery Director can improve the integrations. We have 25 but would like more."
"Unfortunately, today in CDD, we don't have that capacity to integrate the testing yet."
"Reporting and dashboarding could be improved. Release pipelines should be creatable via templates as well as easily integrable/chained together. Visual navigation could also be improved when the pipelines become too large."
"CDD and RA should be two modules in the same product. They do not automatically “talk” to each other. and they require endpoint definition."
"We would like to have a more user-friendly interface. It is already very friendly, but as soon as you start to have many applications with many tasks, the applications should be easier to manipulate on the screen."
"The product's development has been stopped. It focuses on maintaining existing products."
"There are some technologies that this product doesn't support such as some emerging technologies that we need to build the interfaces for; so if that came as a readymade/off-the-shelf feature, it would help us."
"Mainframe automation is one of the biggest challenges for us and currently the product doesn’t address it."
"A task for using a dynamic language like Groovy could be very useful in order to create easily simple tasks."
"Tags are virtual snapshots of different deployment processes. Over time, if you often update your processes, it gets hard to track what exact changes were made between the different tags of the same process."
"There are some stability issues. Sometimes, the server crashes or throws out of memory."
"I think the biggest complaint that we've gotten from the development side is that the user interface, the experience is not as good as they'd like it to be."
"What I personally want to see is more features for data warehousing deployment."
"If I were to consider investing in a new deployment automation tool, I wouldn't switch to CA Release Automation, because of the CA strategy."
 

Pricing and Cost Advice

"There is a free trial available that people can try. The solution has a subscription and it is based on the users that use the solution."
"Nolio is a pretty much good tool, though its pricing is relatively high in the market. It's more expensive than other tools."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
906,781 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
20%
Construction Company
14%
Marketing Services Firm
13%
Outsourcing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise5
Large Enterprise39
 

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with Nolio Release Automation?
The main disadvantage I see is the limited awareness of Nolio Release Automation in other organizations. It is a very nice tool, but its market presence is limited. I heard from the organization th...
What is your primary use case for Nolio Release Automation?
I am working for an organization where they have been using Nolio Release Automation since 2016-2017. We are currently using version 6.6, and due to dependencies and lack of support from Broadcom, ...
What advice do you have for others considering Nolio Release Automation?
The 6.9 version offers significant improvements over 6.6. The dashboard is very appealing, showing information about applications and offline agents. We can easily remove offline agents and upgrade...
 

Also Known As

CA CDD, CA Continuous Delivery Director
CA Release Automation
 

Overview

 

Sample Customers

United Airlines
CA Release Automation customers include Citrix, NIIT Technologies, ING Bank, Molina Healthcare, Swisscom, Bupa and Tesco. Read case studies from customers who are igniting and advancing their continuous delivery journey with CA Release Automation.
Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation. Updated: June 2026.
906,781 professionals have used our research since 2012.