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

Automic Continuous Delivery Director [EOL] vs GitLab comparison

Why PeerSpot?
 

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
GitLab
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
93
Ranking in other categories
Application Security Tools (9th), Build Automation (3rd), Release Automation (2nd), Static Application Security Testing (SAST) (6th), Rapid Application Development Software (15th), Software Composition Analysis (SCA) (6th), Enterprise Agile Planning Tools (2nd), Fuzz Testing Tools (2nd), DevSecOps (1st)
 

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.
BasilJiji - PeerSpot reviewer
System engineer at a retailer with 10,001+ employees
Role-based workflows have transformed daily deployments and improve team collaboration
GitLab has role-based access control, so when a team member needs to make a code change, they cannot directly apply it to the environment but must put in a merge request. Once a senior reviews the code and approves it, then it is implemented across the environment, making it safer and allowing everyone to experience the process. The best features GitLab offers are version control and automation, which are the major things that stand out to me. When it comes to access, the login is very smooth, with just one login integrated with our Okta, allowing everyone to log in easily. Deployments become much easier, and that is how GitLab helps. The automation features make my work easier because we use a tool called AWX, which is connected to GitLab. Whenever we run a job on AWX, it directly checks the code and uses it. Since the code is not preserved locally but kept in the cloud, it is safe and nobody can tamper with it. When it comes to safety, that is a major thing. Automation features allow the code to be accessed from any tools we use, so the jobs we run are helping tremendously and doing their work perfectly. For pipeline tasks, we have created a significant amount of pipelines, which are all hosted in GitLab. Running the pipelines has become much easier, and they are doing a perfect job, helping tremendously in our day-to-day activities. GitLab has positively impacted my organization because previously we stored code locally on servers, leading to many risks. Since GitLab came into our environment, our integration and deployments became much easier, helping our work become much smoother. Improvements from GitLab have led to better team collaboration because when several people are working, they can all edit the code and submit it as a merge request, and once approved, it reflects directly to the main branch. Many can work at the same time. When it comes to deployments, deploying has become much faster since we started using GitLab, and even if errors occur, we can spot them easily and troubleshoot, which has helped tremendously.

Quotes from Members

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

Pros

"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."
"It's the simplicity; it's very simple to use and deploy and deliver, and it works."
"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 second valuable aspect is its capability to drive external systems like deployment automation engines or to integrate with Agile Central."
"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."
"Its ability to automate release deployments, streamline release scope, and reduce the cost of and time for deployment."
"Its extensive range of available connectors eliminates the need for manual code writing when implementing solutions, thus reducing coding efforts."
"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."
"A user friendly solution."
"It is a speedy platform compared to the others I have used, and I have also enjoyed using the platform as this solution offers a good user experience."
"Continuous integration with deployment is very powerful, which is a significant reason for migrating from TFS to GitLab."
"They incorporate new features every September, and they have introduced their own code editor and AI features."
"I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand."
"I recommend GitLab for DevOps engineers."
"The most valuable features of Gitlab are integration with CIE and the ability to rapidly deploy solutions, projects, and applications. It is very easy to use, and there are no complaints."
"It is scalable."
 

Cons

"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."
"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."
"The product's development has been stopped. It focuses on maintaining existing products."
"Automic Continuous Delivery Director can improve the integrations. We have 25 but would like more."
"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."
"CDD and RA should be two modules in the same product. They do not automatically “talk” to each other. and they require endpoint definition."
"Unfortunately, today in CDD, we don't have that capacity to integrate the testing yet."
"As GitLab is not perfect, what needs improvement in the solution is the Wiki feature of the groups or the repertories because currently, it's not searchable by default. You'll need an indexing service such as Elasticsearch to make it searchable, and that requires too much work, so for me, it's the main feature that should be improved in GitLab. In the next version of the solution, from the top of my head, the documentation could be improved. Besides the Wiki, it would be good if there's documentation that would be automatically generated based on the code repository. In other words, there should be some tutorials from GitLab for developers in the next release."
"It is a little complex to set up the pipelines within the solution."
"The solution does not have many built-in functions or variables so scripting is required and that is a drawback."
"The solution should expand features to match other tools such as Coverity, Veracode, or SonarQube with its static code analysis tool so third-party integrations are not required."
"The documentation could be improved to help newcomers better understand things like creating new branches."
"GitLab should include more features because, during the pandemic, companies like Google introduced more features."
"In the next release, I would like to see GitLab expand its integration capabilities to include platforms like DigitalOcean, which developers widely use for cloud infrastructure. Enhancing CI/CD automation features specifically tailored for DigitalOcean would be beneficial."
"I would like to have some features to support peer review."
 

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."
"I'm not aware of the licensing costs because those were covered by the customer."
"The solution is free."
"GitLab is cheap."
"I think that we pay approximately $100 USD per month."
"It seems reasonable. Our IT team manages the licenses."
"This product is not very expensive but the price can be better."
"I'm not sure if they have some kind of discount. I've been negotiating with them on prices before, and I believe they weren't too happy to give discounts, but list prices are $19 per user, per month for Premium and $99 per user, per month for Ultimate. So, the difference between Premium and Ultimate is a bit bigger, and in most companies, you need to build some type of business case."
"As I work in a vast enterprise, I'm unsure about the licensing cost for GitLab. It's the management team that takes care of that."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
31%
Manufacturing Company
10%
Transportation Company
5%
Computer Software Company
5%
Financial Services Firm
13%
Manufacturing Company
11%
Government
8%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business39
Midsize Enterprise10
Large Enterprise50
 

Questions from the Community

Ask a question
Earn 20 points
What is your experience regarding pricing and costs for GitLab?
I was using the free version of GitLab , but I think the price is comparative and not a major differentiator.
What needs improvement with GitLab?
Since GitLab [Private Offer Only] the main part is the Git part. With AI being available, I see one thing happening. For example, Claude Code allows people to connect Jira or ClickUp, and then they...
What is your primary use case for GitLab?
My basic use case for Gitlab was the ticket management, the wiki, the CI/CD pipeline, and the code repository. These four use cases form my core usage.
 

Also Known As

CA CDD, CA Continuous Delivery Director
Fuzzit
 

Overview

 

Sample Customers

United Airlines
1. NASA  2. IBM  3. Sony  4. Alibaba  5. CERN  6. Siemens  7. Volkswagen  8. ING  9. Ticketmaster  10. SpaceX  11. Adobe  12. Intuit  13. Autodesk  14. Rakuten  15. Unity Technologies  16. Pandora  17. Electronic Arts  18. Nordstrom  19. Verizon  20. Comcast  21. Philips  22. Deutsche Telekom  23. Orange  24. Fujitsu  25. Ericsson  26. Nokia  27. General Electric  28. Cisco  29. Accenture  30. Deloitte  31. PwC  32. KPMG
Find out what your peers are saying about Microsoft, GitLab, Amazon Web Services (AWS) and others in Release Automation. Updated: October 2026.
920,769 professionals have used our research since 2012.