Try our new research platform with insights from 80,000+ expert users

Automic Continuous Delivery Automation [EOL] vs GitLab comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

Automic Continuous Delivery...
Average Rating
8.0
Number of Reviews
13
Ranking in other categories
No ranking in other categories
GitLab
Average Rating
8.4
Number of Reviews
74
Ranking in other categories
Application Security Tools (7th), Build Automation (1st), Release Automation (2nd), Static Application Security Testing (SAST) (8th), Rapid Application Development Software (10th), Software Composition Analysis (SCA) (5th), Enterprise Agile Planning Tools (2nd), Fuzz Testing Tools (2nd), DevSecOps (3rd)
 

Featured Reviews

it_user779229 - PeerSpot reviewer
Nov 26, 2017
Reduces our time to market considerably with automated and consistent results
Our most important criteria when selecting a vendor are * the size of the vendor itself * how stable the company is * how long they have been in the market * what product suites they have that can help us achieve our goal at the end of the day. We look for partners, not vendors per se, that can help us implement our vision with us, and that's why we like Automic. I give it a good nine out of 10 at this time. The one piece that I think that could help leverage more of the tool is the scripting language barrier at this time. If that's not there, and some of the pieces that could be delivered faster, it might be adopted more out there in the market. I would suggest look at the complete offering that's out there. I would suggest: Prove it out first with the use case that you have. We were not shy in terms of running some proofs of concept with a couple of big vendors out there, and then making them make the case why their product suits our use case. And don't be shy to restart if there is something that you think is not going right, make sure you fix the problem before it gets too late.
Corné den Hollander - PeerSpot reviewer
Sep 15, 2022
Powerful, mature, and easy to set up and manage
It's more related to the supporting layer of features, such as issue management and issue tracking. We tend to always use, for example, Jira next to it. That doesn't mean that GitLab should build something similar to Jira because that will always have its place, but they could grow a bit in those kinds of supporting features. I see some, for example, covering ITSM on a DevOps team level, and that's one of the things that I and my current client would find really helpful. It's understandably not going to be their main focus and their core, and whenever you are with a company that needs a bit more advanced features on that specific topic, you're probably still going to integrate with another tool like Jira Service Management, for example. However, some basic features on things like that could be really helpful. In terms of additional features, nothing comes to mind. One of the potential pitfalls is to keep adding new features and functionalities. They can just improve some of the existing features to make it high-end, top-quality. I don't have any substantial experience with agile planning. I don't know the industries GitLab is in, and I don't know why they make decisions like this, but as a customer, I would rather see them invest in improving the basic agile planning functionalities rather than adding, for example, portfolio planning features. That's because if I'm going to do portfolio planning, I probably will also need a lot of business users. I'm not sure if I want them in GitLab, I'd rather have them in Jira collaborating with me on portfolio planning. That's way better fitted for that type of work.

Quotes from Members

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

Pros

"You can design your workflows for your needs."
"I would say our headwind, or our time to market, is reduced considerably. We get more consistent results out of it, because you write one time and once it's automated you expect it to behave the same way every time. And it cut down a lot of re-work for us."
"The main benefit is you can deploy everything with it."
"The IT process automation is the most valuable aspect of this solution."
"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 is an umbrella system that allows us to integrate many different systems into our heterogeneous environment."
"Gives people insight into what's happening during the deployment."
"We have saved on our time costs and have seen more quality."
"We're only using the basic features of GitLab and haven't used any advanced features. The solution works fine, so that's what we like about GitLab. We're party using GitHub and GitLab. We have a GitHub server, while we use GitLab locally or only within our team, and it works okay. We don't have any significant problems with the solution. We also found the straightforward setup, stability, and scalability of GitLab valuable."
"I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently."
"The solution's most valuable feature is that it is compatible with GitHub. The product's integration capabilities are sufficient for our small company of 35 people."
"It scales well."
"When a developer checks in code, it is automatically built and deployed, and automated test cases are also run. We have extensive integration with GitLab, which helps us with source code management. We run the static code analysis using SonarQube."
"The SaaS setup is impressive, and it has DAST solutioning."
"CI/CD is very good. The version control system is also good. These are the two features that we use."
"CI/CD is valuable for me."
 

Cons

"There needs to be better error handling and error descriptions. It should be more clear what the errors are and what we can do to fix them."
"If you have a technical problem and need development of the tool, the support team is terrible, because they cannot help with the technical details."
"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."
"The dashboard should allow you to see the current state of packages in each environment, not only on an individual application basis, but across the entire application platform."
"Not a perfect ten because the user interface is brand new and it needs improvement."
"I would like to see more support for WebSphere."
"GUI for mobile phones: Availability to approve and start deployment through mobile phones."
"We hope that we can integrate the new CD Directive into our portfolio, so we can bring the deployment and release management closer together."
"I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities."
"We'd always like to see better pricing on the product."
"I would like more Agile features in the Premium version. The Premium version should have all Agile features that exist in the Ultimate version. IBM AOM has a complete Agile implementation, but in GitLab, you only have these features if you buy the Ultimate version. It would be good if we can use these in the Premium version."
"The integration could be slightly better."
"We'd like to see better integration with the Atlassian ecosystem."
"It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain. If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain."
"You need to have a good knowledge of the product in order to use it."
"GitLab could add a plugin to integrate with Kubernetes stuff."
 

Pricing and Cost Advice

"I can save time and money more quickly."
"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."
"We increased our quality and reduced our time costs."
"Customers often complain about the price."
"The solution's standard license is paid annually. They have changed the pricing model and it used to be better. There is a free version available."
"On a scale of one to ten, where one is cheap, and ten is expensive, I rate the pricing a five out of ten."
"We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive."
"My company uses the free version of GitLab, which is GitLab Community Edition. There is a licensed version also available for GitLab."
"The solution is free."
"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."
"GitLab is cheap."
"In terms of the pricing for GitLab, on a scale of one to five, with one being expensive and five being cheap, I'm rating pricing for the solution a four. It could still be cheaper because right now, my company has a small team, and sometimes it's difficult to use a paid product for a small team. You'd hope the team will grow and scale, but currently, you're paying a high license fee for a small team. I'm referring to the GitLab license that has premium features and will give you all features. This can be a problem for management to approve the high price of the license for a team this small."
report
Use our free recommendation engine to learn which Release Automation solutions are best for your needs.
813,418 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
37%
Computer Software Company
17%
Manufacturing Company
10%
Retailer
5%
Educational Organization
28%
Computer Software Company
12%
Financial Services Firm
11%
Manufacturing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about GitLab?
I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently.
What needs improvement with GitLab?
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 aut...
 

Also Known As

CA Continuous Delivery Automation, Automic Release Automation, Automic ONE Automation, UC4 Automation Platform
Fuzzit
 

Learn More

 

Overview

 

Sample Customers

BET365, Charter Communications, TASC
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, Red Hat and others in Release Automation. Updated: September 2024.
813,418 professionals have used our research since 2012.