GitLab vs ImmuniWeb comparison

"GitLab offers a good interface for doing code reviews between two colleagues."

"The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline."

"It is user-friendly, easy to use, and easy to administer."

"The CI/CD process is very efficient."

"I have found the most valuable features of GitLab are the GitClone, GitPush, GitPull, GitMatch, GitMit, GitCommit, and GitStatus."

"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."

"The initial setup of GitLab is pretty simple, with no complications."

"GitLab's best features are continuous integration and fast deployment."

"ImmuniWeb is stable."

"I like the fully automated continuous discovery run by ImmuniWeb in the background. We do not need to rerun the same tests or the same scanning against our resources. We need to supply our IP addresses, domain names, and significant resources with special domain names and URLs, and we need to do it only once. Then we always have an up-to-date picture. I also like the integration with our single sign-on system. We do not need to maintain a separate set of usernames or user accounts. We can plug this ImmuniWeb service into our authentication technology, enabling two-factor authentication. We have secure authentication right out of the box. The other important feature I like is the executive view. You can easily switch from a technical view to an executive view and have a helicopter view of the compliance status. We can see how much effort is required and our current status."

"After the assessment, you clearly know which assets require penetration testing."

"The solution's most valuable feature is reporting."

"The most valuable features are the SLA of Zero false-positives, less time of service development, validation of unlimited patched vulnerabilities, and several others."

"The initial setup process is user-friendly."

"ImmuniWeb boasts a robust vulnerability detection mechanism, formidable threat mitigation, and an efficient remediation process, incorporating automation techniques and ALM strategies. The solution is highly stable. The solution is scalable. Editing Key Points for Review "Review about ImmuniWeb" What is our primary use case? We use the solution when we face challenges and urgent attention is needed for complex cases from our clients. To address this, we collaborate with the middleware, internal, and client teams to analyze and sort through intricate logs concerning our business cybersecurity program. How has it helped my organization? The solution helped us with one of our clients in the New York area contacted us about a data breach. In response, we swiftly organized a case meeting involving our client, internal, and email customer support teams. Together, we conducted an incident response, facilitating offline assistance for proper planning and risk management processes. We delved into the details of the data breach, identified how it occurred, and collaborated to rectify the issue. The client expressed satisfaction with the resolution process. What is most valuable? ImmuniWeb boasts a robust vulnerability detection mechanism, formidable threat mitigation, and an efficient remediation process, incorporating automation techniques and ALM strategies. It also focuses on consumer satisfaction and operates in English-speaking markets, primarily required by the UAE, the United States, Canada, and Australia, among other developed countries. For how long have I used the solution? We have been using this product for the past one and half years. What do I think about the stability of the solution? The solution is highly stable. I rate it a perfect ten. What do I think about the scalability of the solution? The solution is scalable. I rate it a nine out of ten. How are customer service and support? Support is generally excellent"

"Currently, GitLab is not easy to scale because GitLab has specific deployment instructions. We deploy it on one of the VMs."

"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."

"The self-hosted version of GitLab is not very stable when under load. It slows down and requires restarts every few days."

"I would like to see better integration with project management tools such as Jira."

"The integration and storage capabilities could be better."

"It would be really good if they integrated more features in application security."

"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."

"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."

"ImmuniWeb sometimes shows previous scans instead of running tests."

"A great idea would be to support using Discovery on the internal network, allowing delivery of all the features of the current Discovery to internal network resources."

"A great idea would be to make a mobile application for the ImmuniWeb portal so that all information would be available on the go and from a mobile phone as well. It would be much more convenient."

"It would be better if they had an automated tagging feature. The tagging functionality currently requires manual tagging, and that's probably the most needed feature from my standpoint. We also do not have enough tools, enough features, or options to display different resources in the way we need. There are basic grouping and some filtering features, but we still cannot fully separate some flavors of our resources. However, we may not be aware of the latest features."

"The deployment process on the cloud is straightforward, while on-premise can be complex. Support is generally excellent, although there can be delays in ticket resolution."

"Its technical support could be better."

"The product’s interface for the web applications could be similar to Android and iOS versions."

"I think that we pay approximately $100 USD per month."

"The open-source version is very good and the commercial version is reasonably priced."

"GitLab's pricing is good compared to others on the market."

"The solution is based on a licensing model that includes technical support and is paid annually."

"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 of GitLab could be better, it is expensive."

"The solution's pricing is acceptable."

"GitLab is cheap."

"I use the product's free version. The tool costs around 229 dollars."

"It is pretty expensive."

"ImmuniWeb is relatively cheap. It's a competitive price compared to other products in the marketplace. It's worth the money we are paying for it."

"It is pretty expensive."

"The values of ImmuniWeb are currently significantly below what is valued in the Chilean market for these services and solutions."

"The platform is expensive if a large development is involved. However, it is less expensive for scheduled-based testing, quarterly or in a year."

"There should be the flexibility to change or add pricing, especially for pay-per-use cases."