GitLab vs IBM Engineering Workflow Management comparison

 

Comparison Buyer's Guide

Executive Summary
 

Categories and Ranking

GitLab
Ranking in Enterprise Agile Planning Tools
2nd
Average Rating
8.6
Number of Reviews
70
Ranking in other categories
Application Security Tools (6th), Build Automation (1st), Release Automation (2nd), Static Application Security Testing (SAST) (7th), Rapid Application Development Software (10th), Software Composition Analysis (SCA) (6th), Fuzz Testing Tools (2nd), DevSecOps (3rd)
IBM Engineering Workflow Ma...
Ranking in Enterprise Agile Planning Tools
10th
Average Rating
6.8
Number of Reviews
15
Ranking in other categories
Software Configuration Management (5th)
 

Market share comparison

As of June 2024, in the Enterprise Agile Planning Tools category, the market share of GitLab is 31.9% and it increased by 38.8% compared to the previous year. The market share of IBM Engineering Workflow Management is 1.2% and it increased by 68.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Enterprise Agile Planning Tools
Unique Categories:
Application Security Tools
3.7%
Build Automation
24.4%
Software Configuration Management
2.8%
 

Featured Reviews

HA
May 16, 2023
Efficiently streamlines and automates tasks
My primary use case is for creating pipelines and automation workflows By streamlining tasks that we used to do on a daily basis and scheduling them. CI/CD, GitLab scanning, and the cloud are the most valuable features.  There is room for improvement in GitLab Agents.  I would like to see more…
Suvajit Chakraborty - PeerSpot reviewer
Oct 31, 2023
Offers good traceability elements but UI needs improvement
There is room for improvement in the UI. The UI has to improve a lot compared to the competitive tools, like Atlassian Jira, for example. It's very easy to use. It is easy to manage and easy to use. Anybody can learn it right quickly and start with it. But IBM ELM is something where somebody has to have good knowledge, training, and understanding and then only start using it. But there's a big known knowledge curve for IBM ELM. But once that is there, it's normally; organizations do have their own internal team to basically manage it IBM ELM portfolio, the tool chain. So if they have internal teams who are doing it for quite some time, not something new, then it is definitely better. But if there's if somebody is starting new, definitely there is a knowledge curve time it can take at least a year or maybe a couple of years before they can start realizing the benefits.

Quotes from Members

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

Pros

"It is scalable."
"The best thing is that as the developers work on separate tasks, all of the code goes there and the other team members don't have to wait on each other to finish."
"GitLab's best feature is Actions."
"Key features allow creation of well-presented Wiki that includes ideas, development, and domains."
"It scales well."
"I have had no problem with the stability of the solution."
"It is a speedy platform compared to the others I have used. I have also enjoyed using the platform as this solution offers a good user experience."
"GitLab integrates well with other platforms."
"Good for managing stories, sprints, hydration and releases."
"The most valuable features of the solution are highly customizable reports and visibility for all the higher management."
"Agile templates give us a standard methodology for every Agile project. Also, the ability to create our own object types and linkages to features/epics allows us to enhance the verification of feature readiness."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data."
"Work distribution among team members and accountability for completion with a clearer picture."
"Traceability reporting is inbuilt and includes all your requirements."
 

Cons

"GitLab would be improved with the addition of templates for deployment on local PCs."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"I would like to have some features to support peer review."
"The solution should again offer an on-premises deployment option."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"There is room for improvement in GitLab Agents."
"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."
"GitLab can improve by integrating with more tools, such as servers with Docker."
"Lacks ability to customize and reporting can be slow."
"Some administrative tasks are difficult to perform. These could be simplified."
"The solution is very heavily vendor dependent."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"If you have multiple projects on one server, the tool becomes very slow, and some reports take longer to load."
"We have encountered issues with stability. We have seen where the entire system kind of goes for a toss when certain people use certain types of queries, which are very costly. Then the system kind of slows down a bit, and we have to monitor it."
 

Pricing and Cost Advice

"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."
"The price is okay."
"The open-source version is very good and the commercial version is reasonably priced."
"GitLab is comparatively expensive, but it provides value because it's feature-rich."
"This is an open-source solution."
"The price of GitLab could be better, it is expensive."
"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."
"Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."
"I've heard IBM Engineering Workflow Management is more expensive than other tools."
"It is not a free tool. We use a token-based licensing model, which is specific to IBM. The cost per token is around $115-$120."
"It's an expensive investment to make, so the decision should be driven on individual requirements."
"Licensing: The solution cost is high and should be brought down to increase competition."
report
Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
787,383 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
26%
Computer Software Company
12%
Financial Services Firm
11%
Manufacturing Company
8%
Manufacturing Company
22%
Government
13%
Computer Software Company
10%
Financial Services Firm
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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 is your experience regarding pricing and costs for GitLab?
For small-scale usage, GitLab offers a free tier. For enterprise pricing, GitLab is more expensive than GitHub, as it's not as widely adopted. GitLab is the preferred choice for many developers des...
What needs improvement with GitLab?
I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities. Better integration and usability within the pipeline could make a significan...
What do you like most about IBM Engineering Workflow Management?
We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data.
What is your experience regarding pricing and costs for IBM Engineering Workflow Management?
I've heard IBM Engineering Workflow Management is more expensive than other tools. On a scale from one to ten, where one is cheap and ten is expensive, I rate the solution's pricing a six out of ten.
What needs improvement with IBM Engineering Workflow Management?
If you have multiple projects on one server, the tool becomes very slow, and some reports take longer to load. We have already created some cases with IBM, and they are looking into it.
 

Also Known As

Fuzzit
IBM Rational Team Concert (IBM ALM), IBM RTC
 

Learn More

Video not available
 

Overview

 

Sample Customers

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
Telstra Corporation, Visteon, Atos SE, Panasonic Automotive Systems, IBM Global Technology Services, CareCore National, JTEKT Corp., ItaÒ BBA, Avea, CACEIS, Danske Bank Group, APIS IT
Find out what your peers are saying about GitLab vs. IBM Engineering Workflow Management and other solutions. Updated: May 2024.
787,383 professionals have used our research since 2012.