GitLab is an intelligent orchestration platform for DevSecOps, where software teams enable AI at every stage of the software lifecycle to ship faster. The platform enables teams to automate repetitive tasks across planning, building, securing, testing, deploying, and maintaining software.
$0
TeamCity
Score 7.1 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.
N/A
Pricing
GitLab
TeamCity
Editions & Modules
GitLab Free (self-managed)
$0
GitLab Free
$0
GitLab Premium
$29
per month per user
GitLab Premium (self-managed)
$29
per month per user
GitLab Ultimate
Contact Sales
GitLab Ultimate (self-managed)
Contact Sales
No answers on this topic
Offerings
Pricing Offerings
GitLab
TeamCity
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
GitLab Credits enable flexible, consumption-based access to agentic AI capabilities in the GitLab platform, allowing you to scale AI adoption at your own pace while maintaining cost predictability. Powered by Duo Agent Platform, GitLab’s agentic AI capabilities help software teams to collaborate at AI speed, without compromising quality and enterprise security.
If usage exceeds monthly allocations and overage terms are accepted, automated on-demand billing activates without service interruption, so your developers never lose access to AI capabilities they need.
Real-time dashboards provide transparency into AI consumption patterns. Software teams can see usage across users, projects, and groups with granular attribution for cost allocation. Automated threshold alerts facilitate proactive planning. Advanced analytics deliver trending, forecasting, and FinOps integration.
GitLab is a cost effective alternative to names like GitHub and others. It provides easy to use interface that is not dissimilar from GitHub and Atlassian Bitbucket. Where GitLab really shines is in its simplicity and ease of use. It's very intuitive and effectively allows a …
It is easy to use , devsecops/ dataops / gitops implementation is quite easy and straightforward compared to other tools which we have tested , it provides seamless integration with tools like dbt , talend , snowflake , collibra and python. Merge issues as well as pipeline …
I liked GitLab better than Beanstalk. GitLab had a free option, which Beanstalk did not at the time. From what I have used of Bitbucket, I probably like it better than GitLab, specifically I like the design better. Doing things in Bitbucket seemed a bit slower to me though. Now …
GitLab is widely used throughout the developer community and provides all the required features industry wide. Many of the paid features help the team a lot to achieve efficient source code management. Many features like vulnerability management and AI chat while code review in …
Gitlab is an industry standard tool for version controlling of the source code with multiple features used by the developers to maintain efficient development process and scalable services integration on the larger code bases. Multiple tools like AI code review helps the …
GitLab is an industry standard software and provides alot of features helpful for the developers with a suitable price point. It has most of the features that are provided and are useful. Team management and security for the source code and restrictions helps achieve all the …
GitLab is an all-in-one Git and CI/CD platform that also offers generous credits in its free plan. It allows both private and public projects. The pipelines can be fully defined in YAML files put under version control.
GitLab is superior to beanstalk but still lacking in some areas in comparison to newer features to Github. However, it's enterprise based approach is very attractive to many of our top tier clients making it and effective solution for us within their organizations. It's well …
We have recently migrated from Bamboo to GitLab across our enterprise as part of our tech modernization roadmap. GitLab provides a all-in-one platform for integrated code management. The only advantage that Bamboo had over GitLab was the integration with JIRA. The streamlined …
In our case, we opted for an open source solution and complete control of information, meaning we kept critical information and company developments in-house.
As mentioned earlier, the features like chart visualization sets it apart from the others. Other than that, GitLab is open source while other are not and comparatively more secure that its other counterparts. Also, GitLab supports adding other types of attachments which is not …
When i was using the other platform, Some time i face down time, But GitLabs its not happening for single time. GitLab is having easy user interference as compared to other platforms. Pull Request, Code review, Issue tracking, Merging, Access control and User Roles is having a …
GitLab is miles ahead of the competition. In so many words, having a simple UI with robust security and the ability to conduct Git actions takes the cake. The competitions like to say they can do these things easily but their products are more confusing and hard to use.
Because it has the latest features, it is perfect for collaboration, has the best integrations available, and is super secure. Basically, it covers all my needs and the companies. I love its pipelines because of its secrets and agents. I also love that you can manage the …
GitLab allows a self-hosted version that is easy to setup and configure. It is also open-source as compared to GitHub. The integrated CI/CD tools is a plus, since we do not have to worry about those tools, unlike Github. The All-in-one solution of GitLab made sense for our …
Gitlab offers the best support for CI/CD pipelines and the highest degree of customisation for workflows, permissions, and integrations. The integration of BitBucket with JIRA is better than GitLab but CI/CD features are limited in comparison. GitLab's built-in Container …
Gitlab provides basic functionality like any other git tool. Some features of push and pull requests , clone and merge is handled equally well. It lacks in AI features which are there in GitHub and setup processes are difficult. Cost difference is the only concern while …
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution.
GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" …
It's much simpler than the competitors. The one important feature Gitlab stand out is the CI/CD pipeline. GitHub required integration with external CI tools but Gitlab has this feature built-in. Compare to Jenkins and Teamcity, It's easy to use without any additional Plugins. …
Gitlab seems more cutting-edge than GitHub; however, its AI tools are not yet as mature as those of CoPilot. It feels like the next-generation product, so as we selected a tool for our startup, we decided to invest in the disruptor in the space. While there are fewer …
Jenkins relies on being open source as the primary driver for its success. This low cost is a huge factor for many companies, both small and large. The professional, free tier of TeamCity offers a huge amount of growth before ever needing to pay anything. I personally also find …
Since we were already making use of other JetBrains offerings, TeamCity had a leg up on the competition due to the ease of integration with these tools. With that said, TeamCity's feature set stacks up well with the competition. Jenkins definitely has some nice features, but …
This application is easy to install and deploy at site than most of the similar solutions in market. Easy user interface is one of the reason it can be installed. However each software have its good points and bad points. Study your organizations case and then only choose …
I would also like to compare TeamCity against Snap-Ci as well as Concourse. We chose TeamCity over all of these tools because of its ability to be set up easily against a restricting corporate firewall. We needed to integrate unit tests, integration tests, pushes to production, …
TeamCity competes against the TFS build, Visual Studio Team services and Jenkins the open source workhorse. The reason for selecting TeamCity was because it was found to be a great fit for all the diverse projects on a spectrum of technologies we have which the TFS Build …
Cloud Services Practice Manager and Principal Architect
Chose TeamCity
TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud. VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and …
I like the quality of Jetbrains products. TeamCity is well supported and regularly updated by Jetbrains. They have an active support forum and most questions are answered quickly.
TeamCity is very extendable and has been able to handle everything we've been required to do.
We've only ever really used TeamCity as a CI platform. Running tests on these CI clusters is worlds more efficient and just plain easier than having to run individual tests on your local machine. You just hit one button here, versus either writing some run script or even worse …
TeamCity is the best combination of price and full features. It has a good web UI and doesn't need a lot of manual configuration files, but it still is incredibly extensible and can do just about any build or release task you set it at. If it can't do it, the odds are it has a …
Jenkins and Team Foundation Server (TFS) are both strong products. Compared to Jenkins, TeamCity is much more mature and polished. Though Jenkins is open-source/free, the cost of TeamCity is a drop in the bucket compared to the total cost of even one project we're using it …
It is well-suited for any project that needs VCS. It's an excellent choice for teams that might be remote or have to collaborate across teams. Plenty of features allow for async working. With its dashboards and reporting features, it is also suitable for nontechnical PMs or stakeholders. It allows for very bespoke customization and can most often do much more than you need it to.
TeamCity is well suited for an organization using continuous integration, meaning you release code to production often, and an agile project management system. There are free versions available for small teams and enterprise versions available for large teams with many different builds. TeamCity is probably overkill for basic e-commerce or blog website builds that do not require much development after the initial launch
Fully customizable build process. Each step of the build process can be parameterized and customized to address specific needs of particular applications. This allowed us to easily convert from a custom VM-based environment to our current Docker-based environment.
Manages large numbers of build agents seamlessly. This allows us to run multiple builds on many different applications in a most efficient manner.
Build steps can be managed in an arbitrary manner, allowing some parts of the process to proceed in parallel while restricting others to depend on completion of all relevant steps.
I really feel the platform has matured quite faster than others, and it is always at the top of its game compared to the different vendors like GitHub, Azure pipelines, CircleCI, Travis, Jenkins. Since it provides, agents, CI/CD, repository hosting, Secrets management, user management, and Single Sign on; among other features
I find it easy to use, I haven't had to do the integration work, so that's why it is a 9/10, cause I can't speak to how easy that part was or the initial set up, but day to day use is great!
I've never had experienced outages from GItlab itself, but regarding the code I have deployed to Gitlab, the history helps a lot to trace the cause of the issue or performing a rollback to go back to a working version
GItlab reponsiveness is amazing, has never left me IDLE. I've never had issues even with complex projects. I have not experienced any issues when integrating it with agents for example or SSO
TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft
GitHub is an inferior product from most points of view. We had to use it and the teams finds no positives about it. Everything is a downgrade from our previous GitLab solution. GitLab CI\CD is vastly superior to workflows, for example doing a manual node is just "when : manual" in GitLab while you have to do clickops in GitHub to achieve the same. No overview of code in branches is a minus when we tried to figure out what our colleagues are trying to merge as it looked off.
Jenkins relies on being open source as the primary driver for its success. This low cost is a huge factor for many companies, both small and large. The professional, free tier of TeamCity offers a huge amount of growth before ever needing to pay anything. I personally also find the user experience of TeamCity to be much better, both from a look and feel, as well as from an out-of-the-box feature set perspective. The big selling feature of ADO is its native integration with Azure. TeamCity integrates very well with out-of-the-box .NET support and greatly simplifies our use of another diverse tooling outside of the Microsoft ecosystem.
TeamCity was a key contributor to our organization's adoption of Agile.
TeamCity made it possible to KILL "It works on my laptop" conversations with Developers. If it does not compile in TeamCity - the project is not deployable. TeamCity's easy to use interface made it possible to quickly adopt a "Deploy Only from TeamCity" policy, further ensuring TeamCity Builds were the gold-standard for well-configured source code.