

GitHub and GitLab are leaders in the domain of code hosting and collaboration, both offering strong solutions in this competitive space. GitHub has the upper hand in ease of use and community support, while GitLab excels in providing comprehensive DevOps features, particularly in CI/CD capabilities.
Features: GitHub is renowned for its user-friendly code management, advanced security with SSH key management, and strong support from a vibrant open-source community. In contrast, GitLab offers seamless CI/CD integration, robust automated pipelines, and comprehensive DevOps tools, making it a favorite for those prioritizing integration and deployment efficiency.
Room for Improvement: GitHub could enhance its project management tools and automate more complex DevOps integrations, aiming for better cooperation with platforms like Slack and Jira. Meanwhile, GitLab can focus on improving its user interface for more intuitive navigation, further enhancing integration with popular tools like Slack and Jira, and building in more advanced security scanning features.
Ease of Deployment and Customer Service: Both GitHub and GitLab facilitate flexible deployment, catering to public and hybrid cloud setups. GitHub garners positive feedback for its user-friendly platform and supportive community, though its direct support experiences vary. GitLab shines in its deployment capabilities for CI/CD processes but receives feedback suggesting the need for more robust documentation and enhanced user support.
Pricing and ROI: GitHub is valued for its cost-effectiveness and attractive free-tier offerings, optimal for both public and private repositories. Users praise GitHub for its affordability and accessibility. In comparison, GitLab's competitive pricing is justified by its extensive features, although its premium tiers can pose challenges for smaller teams.
Regarding release frequency, previously we had one to two releases per week, but now we achieve daily or on-demand releases, resulting in a three to five-fold increase in release frequency.
Migrating to GitLab is bringing time-saving benefits, and everything is easier to automate.
We have saved time significantly, reducing deployment time from four hours to five minutes per deployment.
The technical support from GitHub is generally good, and they communicate effectively.
Some forums help you get answers faster since you just type in your concern and see resolutions from other engineers.
I have not used GitHub's technical support extensively because there are many resources and a robust knowledge base available due to the large user community.
We have rarely needed to escalate issues to technical support since GitLab usually runs seamlessly.
I have interacted with architects for some advice during the implementation, and they were prompt in their response.
I have had meetings where they taught me, explained things, and provided guidance for starting from scratch.
We have never had a problem with scalability, so I would rate it at least eight to nine.
GitHub is more scalable than on-prem solutions, allowing for cloud-based scaling which is beneficial for processing large workloads efficiently.
It has all the features required for our coding and deployment needs, which makes it scalable to our changing requirements.
We're transitioning to OpenShift for future scalability with increased user numbers.
For scaling, other deployment options from GitLab's side need to be adopted.
If a skilled developer uses it, it is ten out of ten for stability.
It provides a reliable environment for code management.
GitHub is mostly stable, but there can be occasional hiccups.
I have not encountered any performance or stability issues with GitLab so far.
The updates are frequent and demanding, happening at least once a week due to security reasons.
We raised a request with GitLab support, but they were unable to help because they could not find the root cause of what went wrong.
When working with the CI/CD pipeline and somebody is writing the workflow file, it would be best to include the AI feature so if they write incorrect code, it will notify me about it in the same dashboard, eliminating the need to use third-party tools to review the file.
I am providing this feedback for Copilot because it seems more widespread and more companies allow it rather than Amp, and it would be beneficial if they catch up with Amp on this capability.
Security could make GitHub better. OWASP Top Ten security advisors could be integrated on GitHub, and it could provide checks and advice.
It would be beneficial to have a user-friendly interface for setting up these configurations, instead of just writing YAML files.
It is essential to conduct proper testing, such as unit tests and code coverage, within the SDLC pipelines.
GitLab can improve its user interface to make conflict resolution more user-friendly.
Normally, GitHub is not expensive, but it would be welcome if it reduces costs for developing countries.
The pricing of GitHub is reasonable, with the cost being around seven dollars per user per month for private repositories.
The pricing of GitHub depends on the choice of solutions, such as building one's own GitHub Runners to save money or using GitHub's Runners with extra costs.
Even when working in other small organizations, we opted for GitLab as it was cost-efficient.
The pricing of GitLab is reasonable, aligning with what I consider to be average compared to competitors.
The price is high, and it limits user accessibility.
The pull request facility for code review.
GitHub Actions allow for creating multiple jobs that run in different stages such as build, test, and deploy, which enable better visibility and control over the deployment pipeline.
For branching, it works well, especially in an agile environment.
As we implement automated testing and DevSecOps, it speeds up the process by forty to sixty percent.
The Ultimate version offers enhanced features for security scanning through DAST and SAST analysis, which have greatly benefitted our project workflow.
By integrating GitLab as a DevOps platform, we have enhanced agility, improved our time to market, and different teams can work collaboratively on various projects.
| Product | Market Share (%) |
|---|---|
| GitHub | 1.3% |
| GitLab | 2.1% |
| Other | 96.6% |


| Company Size | Count |
|---|---|
| Small Business | 42 |
| Midsize Enterprise | 13 |
| Large Enterprise | 49 |
| Company Size | Count |
|---|---|
| Small Business | 36 |
| Midsize Enterprise | 10 |
| Large Enterprise | 46 |
GitHub is a web-based Git repository hosting service. It offers all of the distributed revision control and source code management (SCM) functionality of Git as well as adding its own features. Unlike Git, which is strictly a command-line tool, GitHub provides a Web-based graphical interface and desktop as well as mobile integration. It also provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project.
GitLab offers a secure and user-friendly platform for CI/CD pipeline management, code repository control, and collaboration, enhancing development speed and efficiency. It facilitates automation with extensive customization and tool integration, ideal for DevOps processes.
GitLab supports source code management, version control, and collaborative development. It's frequently used in CI/CD processes to automate builds and deployments while integrating DevOps practices. GitLab allows companies to manage repositories, automate pipelines, conduct code reviews, and maintain development lifecycles. The platform supports infrastructure and configuration management, enabling efficient code collaboration, deployment automation, and comprehensive repository handling. Many organizations commit and deploy developed code using GitLab's capabilities.
What are GitLab's most valuable features?In specific industries, GitLab serves as a backbone for source code management and CI/CD implementation. Companies leverage its capabilities for infrastructure management and deployment automation, thus streamlining project delivery timelines. Its ability to handle configuration management and code repositories effectively aids in maintaining development lifecycles, making it a preferred choice for organizations committed to enhancing their DevOps practices.
We monitor all Application Security Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.