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

Automic Continuous Delivery Automation [EOL] vs Microsoft Azure DevOps 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
13
Ranking in other categories
No ranking in other categories
Microsoft Azure DevOps
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
137
Ranking in other categories
Application Lifecycle Management (ALM) Suites (2nd), Release Automation (1st), Enterprise Agile Planning Tools (1st)
 

Featured Reviews

reviewer895359 - PeerSpot reviewer
Principal Project Engineer at a computer software company with 501-1,000 employees
Automatic installation for complex deployments and environments, with good workflow support
I like that really complex deployments are possible with it. It's very good. You have everything you need. You can design your workflows for your needs. You can do so much more, it's not just an automatic installation tool. It's a real deployment tool. I can do the complete deployment with everything that is possible.
Bharadwaj Deepak Mohapatra - PeerSpot reviewer
DevOps Engineer at ENTERPRISE SYSTEM SOLUTIONS LIMITED
Have built reliable end-to-end pipelines and streamlined cloud provisioning through consistent collaboration practices
I am currently working with open-source tools such as Jenkins for my main CI/CD pipeline, and for enterprise clients, I am using Microsoft Azure DevOps CI/CD pipeline. For other clients, I have also implemented CI/CD YAML pipelines through GitLab CI/CD workflow and GitHub Actions. I am creating the end-to-end CI/CD pipeline from development to deployment and monitoring all of this. Azure Boards is easier than Jira for my understanding because there are very easy points to manage the Agile methodology which we work on. Because it is a GUI, sometimes the process may take a few minutes more than the CLI process since the backend is running the exact CLI, but we are commanding through the GUI. There is definitely a time lag, but it is more secure. Microsoft Azure DevOps pipelines work very seamlessly rather than other CI/CD pipelines, as of my understanding. The downside is that the process may take more time when deploying some clusters, Kubernetes, Azure AKS service, or some vast microservice architecture deployments. There may be a little bit of lag I feel, though I cannot tell very strictly that this is a disadvantage, but sometimes it takes a little more time than other cloud infrastructures. All the major things are done by GUI, which is somewhat a little slow. However, if considering automations, process, monitoring, and provisioning, then it is the best cloud service across all the other service providers. Our implementation is a hybrid cloud. Microsoft Azure DevOps is definitely easily scalable. I have worked on many Kubernetes infrastructures and microservice deployments, and I have seen that replication is very good because it is very easy. The replication process is very straightforward. I definitely advocate for using less code because it is very time-consuming. If using GCP or Amazon Web Service, there is more interaction related to work over the CLI process. In terms of Microsoft Azure DevOps, there are many things done by the GUI, which is the best part.

Quotes from Members

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

Pros

"I think on a day-to-day basis, it has increased the capacity to deploy. We don't have to wait for someone to do something."
"It provides a wonderful user interface which is easy to use."
"The product provides efficiency, in terms time, cost, and resources."
"The most valuable feature is the ability to see which problems have been resolved from deployment."
"The capability to provide visibility to the stakeholders, to management, is the biggest piece that showcases what the solution is about."
"I like that really complex deployments are possible with it."
"In first pilot run, we achieved five times faster deployment without human work."
"You can automate everything you want."
"This includes the ability to build and customize sprints, and I like the tracking and that we can monitor our velocity."
"Since it is a cloud product, it is constantly updated and not the responsibility of the user."
"There are great automation tools."
"The work items option is incredibly flexible."
"Two of the most valuable features include the integrated project management suite, which consolidates source code and project management in a single location, and its powerful reporting capabilities."
"We have a solid base and can do everything with DevOps, and it is possible to add third-party extensions to increase the usability of the product."
"The solution has proven itself to be very mature and robust, quite stable, and its scalability potential is very good."
"As a result, the throughput and velocity increased simply because the Kanban board made them more visible."
 

Cons

"I would like to see more support for WebSphere."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"One of the biggest features I've been asked by my team to put in there is opening more scripting languages to be part of the platform. There is a little bit of a learning curve in learning how to code some of the workflows in Automic at this time. If widely used languages like Perl and Python were integrated, on top of what's already there, the proprietary language, it would make it easier to on-board new resources."
"We're a WebSphere shop so I would like to see more support for WebSphere, only because it's the platform that they seem to want to use the most."
"There are some bugs. For example, during the design of a workflow, important information is lost, it vanishes."
"The first time setup can be very complicated."
"The stability of the solution can be improved."
"I would like to see new features added."
"It is not that intuitive. Sometimes, it is hard to find some of the functions."
"With an ecosystem that has been up and running for some time, you won't have the full-flexibility that you would have with a new ecosystem."
"Its UI can be easier and more customer-friendly. The UI can be improved from the project management and agile perspective."
"I can't think of any specific things at the moment, but I've run into things that I didn't like. I came across something that I wanted to be changed in DevOps, but I can't remember what it was. It was a particular feature I was looking for that I couldn't find."
"The solution can improve by adding integration with on-premise tools. The only built-in repository options are GitHub and DevOps."
"At times, our development work encounters issues, particularly when executing numerous CI/CD processes."
"The administrative capabilities of the tool need a huge improvement. Its Wiki and reporting also need a lot of improvement. Their support can also be better."
 

Pricing and Cost Advice

"We increased our quality and reduced our time costs."
"I can save time and money more quickly."
"Customers often complain about the price."
"If you have a fixed contract, it has limits to spreading out. If you have a flexible enterprise license contract, then you have a lot of scalability for this tool."
"The pricing is very competitive because of the whole development cycle by Azure DevOps. You don't have to buy and integrate several different tools."
"As the cost structure is per user, I would recommend paying the cost structure based on the amount of data you use rather than the number of users."
"The price of the solution is expensive."
"The main agile features are very expensive."
"I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees."
"There is a license for this solution."
"It is the least expensive product in this class."
"The price is cheaper than Jira and some of the other competing tools."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
899,324 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
14%
Comms Service Provider
14%
Financial Services Firm
12%
Marketing Services Firm
11%
Manufacturing Company
15%
Financial Services Firm
9%
Government
8%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise2
Large Enterprise9
By reviewers
Company SizeCount
Small Business43
Midsize Enterprise28
Large Enterprise69
 

Questions from the Community

Ask a question
Earn 20 points
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
Which is better - TFS or Azure DevOps?
TFS and Azure DevOps are different in many ways. TFS was designed for admins, and only offers incremental improvements. In addition, TFS seems complicated to use and I don’t think it has a very fri...
Microsoft Azure DevOps: what is your experience regarding pricing and costs ?
Pricing experience is limited, as I am a user of this product and not involved in the pricing aspects. There has definitely been a lot of return on investment from using Microsoft Azure DevOps due ...
 

Also Known As

CA Continuous Delivery Automation, Automic Release Automation, Automic ONE Automation, UC4 Automation Platform
Azure DevOps, VSTS, Visual Studio Team Services, MS Azure DevOps
 

Overview

 

Sample Customers

BET365, Charter Communications, TASC
Alaska Airlines, Iberia Airlines, Columbia, Skype
Find out what your peers are saying about Microsoft, GitLab, Red Hat and others in Release Automation. Updated: May 2026.
899,324 professionals have used our research since 2012.