Powerful CI/CD for DevOps-centric teams
According to the JetBrains Developer Ecosystem Report 2026, GitHub is the most popular place to host code. It is used by 85.1% of developers for personal projects and by 56.0% for professional projects.
GitLab ranks second in both groups, but the gap is much smaller among those hosting professional projects there.
That difference is a useful starting point for choosing a platform. A service you use for a side project may also work well for your team. At work, though, the decision involves more people and more requirements: code reviews, access policies, existing tools, and the way you build and release software.
Below, we look at what the survey tells us about those choices, compare the main platforms, and explain where smaller services fit. We also take a separate look at game development, where a repository can contain as much artwork and audio as source code.
Developer Ecosystem 2026
Version control in 2026 at a glance
90.7%regularly use Git. SVN is a distant second at 5.9%.
56.0%use GitHub at work; GitLab follows with 31.3%.
66.5%run version control operations from their IDE or editor, exactly as many as use the terminal.
Version control and repository hosting
Version control keeps a history of your code, so you can see what changed and go back to an earlier version. A hosting platform such as GitHub or GitLab gives your team a shared place for that code, together with reviews, permissions, and other collaboration tools.
Most platforms covered in this article work with Git, and the survey shows why: 90.7% of developers use Git, while Subversion is down to 5.9%. Perforce and Unity Version Control offer different systems for managing code and project files.
Developer Ecosystem · 2025 vs. 2026
Git is still the default
Which version control system(s) do you regularly use, if any? (Multiple answers allowed)
Top 10 version control system tools
Developer Ecosystem 2026
Where developers host code, at work and for personal projects
What stands out in the 2026 results
GitLab is much more competitive in workplace settings
GitHub’s lead is particularly large for personal projects: 85.1% use it, compared with 15.0% for GitLab. At work, the figures are 56.0% and 31.3%, respectively. GitHub goes from having almost six times GitLab’s usage to less than twice its usage.
Developer Ecosystem 2026
Repository hosting: at work vs. personal projects
Which repository-hosting services do you use in your company / for your personal or side projects? (Multiple answers allowed)
For a public project, GitHub’s familiarity can be an advantage. Contributors may already have accounts and know the pull request workflow. A team choosing a shared development platform has more to consider, including where the service can run and how code review connects to builds and releases.
GitLab deserves a closer look in that comparison than the personal-project figures alone would suggest.
The rest of the development setup matters
GitLab’s professional usage is more than double its personal-project usage. For Azure DevOps, it’s three times as high. Bitbucket also has stronger workplace adoption.
The appeal goes beyond code hosting. GitLab brings repositories and CI/CD together, Bitbucket connects with Jira, and Azure Repos works alongside Azure Boards and Azure Pipelines.
For teams already using these tools, those connections can matter more than where individual developers keep their side projects.
Further reading: Bamboo End of Life: How to Prepare and Choose the Right CI/CD Replacement
Bitbucket is losing ground, while GitHub grows for personal projects
Comparing 2025 and 2026 using the same question wording shows one clear shift. Bitbucket’s workplace share fell from 13.7% to 9.1%, and its personal-project share halved from 6.2% to 3.0%. Both drops are statistically significant.
Over the same period, GitHub’s share for personal projects grew from 83.2% to 86.3%, while GitLab’s numbers stayed within the margin of error.
This year-over-year comparison uses the question that kept its 2025 wording, so its 2026 figures differ slightly from the main table above.
Developer Ecosystem · 2025 vs. 2026
Version control services, 2025 vs. 2026
Which version control service(s) do you regularly use? (Same question wording in both years. Multiple answers allowed)
Lower adoption doesn’t mean less useful
A tool’s overall adoption doesn’t necessarily reflect how well that tool suits a particular team’s needs. For example, in the responses to questions about general hosting, Perforce accounts for just 1.0% of professional use. In the separate game development question, it appears at 4.3%, while Unity Version Control is at 6.7%.
These adoption numbers may seem low, but ultimately teams choose these tools because of the specific files and workflows they support. ‘Popularity’ doesn’t tell the whole story, because a less popular tool may still excel within its own niche use cases. It all just depends on how your team actually works with assets.
VCS tools for game teams
General hosting vs. the game development question
Unity Version Control was not an option in the general hosting question.
The same applies to Gitea, Forgejo, and Codeberg. Their smaller numbers give them less visibility in an overall ranking, but they offer different ways to host Git projects, including running your own service or using a nonprofit provider. Those are meaningful choices for developers who care about how their hosting is operated.
How to choose a hosting platform for your team
When trying out an unfamiliar platform, start by making a normal change to one of your projects. For example, a developer pushes code, opens a review, waits for the build, and merges the change. Someone else may need to approve it, or a policy may require a particular test to pass.
Ideally, you’d see how well a platform supports that entire process before making a decision about its suitability.
Evaluation checklist
What to compare during a trial
Try these tasks with a real repository. A small demo project won’t tell you much about cloning years of history, fetching large assets, or starting several builds at once. It is also worth checking the exact plan you would use: Review rules and administration features can differ between free and paid editions.
Also check how the platform fits the tools your developers already use day to day. In the survey, developers were just as likely to run version control operations from their IDE as from the terminal (66.5% each), and 38.3% used the hosting platform’s web interface.
Developer Ecosystem 2026
The IDE is as common as the terminal for Git work
Which tools do you usually use for version control operations? (Multiple answers allowed)
Further reading: How To Choose a CI/CD Tool
Cloud hosting or running the service yourself
Choosing a platform also means deciding who runs it. GitHub, GitLab, and Gitea offer cloud-based and self-hosted options. You can also run Forgejo yourself or use Codeberg’s hosted service.
Cloud hosting means less maintenance for your team. Self-hosting gives you more control over access and storage, but your team handles updates, backups, and recovery. Factor in that time and cost, even if the software is free.
Self-hosting is a popular choice at work. About one in three developers (34.9%) report self-hosted repositories in their company, and 18.1% describe a hybrid setup. For personal projects, the cloud is the clear default at 68.6%.
Developer Ecosystem 2026
At work, one in three developers uses self-hosted repositories
How are your code repositories hosted? (Multiple answers allowed, so bars can exceed 100%)
Version control hosting platforms compared
The main platforms cover many of the same basics. Their differences become clearer when you look at who will use them, which tools they connect to, and how much of the setup your team wants to manage.
GitHub
Hosting: Cloud, with GitHub Enterprise Server for self-hosted installations.
GitHub is a natural starting point for a Git hosting shortlist. It brings code, pull requests, issues, and automation into a familiar interface. For projects that accept outside contributions, using a platform contributors already know can make participation easier. Organizations can also choose Enterprise Server when they need to run their own instance.
- Best for: Teams that want a familiar Git workflow and a wide choice of integrations.
- Strengths: Pull request collaboration, repository rules, required checks, and apps and APIs for connecting other tools.
- Keep in mind: Check which controls are included in your plan, especially for private repositories. Include large-file storage and downloads in the cost estimate.
GitLab
Hosting: GitLab.com, GitLab Self-Managed, and GitLab Dedicated.
GitLab is worth considering when a team wants repository hosting and delivery tools in the same place. A merge request can bring the discussion and pipeline results together, while the deployment options let the team choose who operates the service.
- Best for: Teams evaluating repositories, code review, and CI/CD together.
- Strengths: Merge requests, integrated pipelines, and a choice of cloud-based or self-hosted deployment.
- Keep in mind: Some review controls, including required approval rules, depend on the subscription tier. A self-managed installation also needs ongoing administration.
Bitbucket
Hosting: Bitbucket Cloud and Data Center options for existing self-managed customers.
Bitbucket is most appealing to teams who already use Jira. Its integration links work items with branches, commits, and pull requests, so users can track a task without manually collecting links from several tools. The benefit is twofold: the team gets a place to host their repositories and a tighter connection between code development and their existing workflows.
- Best for: Teams that already organize development work in Jira.
- Strengths: Pull request reviews and links between planned work, code changes, and build or deployment information.
- Keep in mind: Cloud and Data Center are different offerings. Check the available deployment and licensing path before planning a new installation or migration.
Azure DevOps and Azure Repos
Hosting: Azure DevOps Services in the cloud and Azure DevOps Server on your own infrastructure.
Azure Repos is a straightforward option to consider if your team already uses Azure DevOps. Git repositories work with pull requests and branch policies, including reviewer and build requirements. It also supports Team Foundation Version Control, or TFVC, for teams maintaining that setup.
- Best for: Organizations already using Azure DevOps for work tracking and builds.
- Strengths: Branch policies, pull requests, and connections with the wider Azure DevOps toolset.
- Keep in mind: Decide whether the project needs Git or TFVC and whether the service will run in the cloud or on your infrastructure. Those choices affect the tools and administration involved.
Perforce P4 (formerly Helix Core)
Hosting: Self-hosted installations and P4 Cloud.
Perforce P4 deserves a place on the shortlist when large shared assets are a central part of the project. It supports file locking, streams, and workspaces that control which project files each person needs. For a game team, these can be more relevant than having the same review interface as a typical web project.
- Best for: Teams working with large binary files and shared game or design assets.
- Strengths: Exclusive file locking, configurable workspaces, and integrations with game development tools.
- Keep in mind: Moving from Git changes how people work with version control. Include artists, developers, and build engineers in the trial so that you test the whole workflow.
Gitea
Hosting: Open-source self-hosted software, with managed and enterprise offerings.
Gitea combines Git hosting with pull requests, issues, packages, and automation. It is an option for teams who want to run their own Git service while keeping a familiar way to review and discuss changes. Gitea Actions adds CI/CD through separate runners, and external build integrations can be part of the setup too.
- Best for: Teams that want to run their own Git hosting service.
- Strengths: Repository collaboration, package hosting, and automation in the same installation.
- Keep in mind: Someone still needs to maintain the service. If you plan to reuse GitHub Actions workflows, test them: Gitea describes its implementation as mostly compatible.
Forgejo
Hosting: Self-hosted software, also available through public hosting providers.
Forgejo offers a community-developed alternative for hosting Git projects. It grew out of Gitea and has followed its own development path since 2024. A team can run it directly or use a provider that operates it. That choice matters: the same software can come with different support, storage, and service policies depending on who runs it.
- Best for: Developers who want a community-governed Git forge.
- Strengths: Pull requests, issues, and Forgejo Actions, with control over a self-hosted installation.
- Keep in mind: Choose the hosting provider as carefully as the software. Existing automation may need changes when moving from GitHub Actions or Gitea.
Codeberg
Hosting: Nonprofit hosted service powered by Forgejo.
Codeberg is a useful option for free and open-source projects that want a community-operated service without running a server themselves. It uses Forgejo, but choosing Codeberg is a hosting decision as well as a software decision. The service is built around supporting free software, rather than selling general-purpose private repository hosting.
- Best for: Free and open-source projects looking for a nonprofit hosting provider.
- Strengths: Hosted Git collaboration through Forgejo, without the work of maintaining your own instance.
- Keep in mind: Read the project and resource policies. Codeberg is not intended for private commercial projects, and larger storage or CI needs may require a request.
Five more platforms worth considering
AWS CodeCommit
AWS CodeCommit is most useful for teams who want repository access to fit their AWS accounts, network setup, and audit tooling. AWS reopened the platform to new customers in November 2025. It is worth a look for that integration, while the review process and day-to-day developer experience still need to suit your team.
SourceForge
SourceForge combines Git, Mercurial, and Subversion hosting with issue tracking and software downloads. This makes it relevant to public projects that need to distribute releases as well as share source code. For those projects, the download experience is part of the product choice too.
Gitee
Gitee serves the Chinese developer ecosystem with Git hosting, code review, project collaboration, and CI/CD. It belongs in the comparison when those communities or workflows are important to the project. Check the tools and access your contributors will need, including people working from other locations.
Gogs
Gogs focuses on simple Git hosting with low resource requirements. It can run as a standalone program or in a container. It is worth considering if your team can get by with a lightweight self-hosted service. Compare its review and authentication options with your actual requirements.
SourceHut
SourceHut takes a different approach to collaboration, with Git and Mercurial hosting, mailing lists, CI, and email-based patch reviews. It’s suitable for projects that already have this workflow. If your team is used to web-based pull requests, start by trying the review process.
Why game development needs its own approach
Games include much more than code. A project can contain textures, models, animation, audio, and large scene files. Developers and artists need to share those files without overwriting each other’s work, and the build machines need to fetch them in time to produce the next playable version.
That changes what matters in version control. Changes to a source file can often be merged. Changes to a binary asset may be much harder to combine, so developers need a way to see who is working on it and prevent conflicting edits. Decisions about VCS tools also have to factor in file locking and the tools the artists are using.
Game developers · 2025 vs. 2026
Version control in game development
Which version control tools do you or your team use? (Multiple answers allowed)
Git hosting still plays a major role
GitHub is the leading platform among game developers, too, at 68.2%, followed by GitLab at 23.0%. Another 20.4% run their own Git servers. Git hosting clearly has a substantial place in game development. The decision is which combination of hosting, large-file support, and asset tools will work for a particular project.
For a Git-based setup, test Git LFS with the project’s real assets. LFS stores the file contents separately from the references kept in Git, so storage and downloads both matter. Also check locking and engine integration, rather than assuming large-file support covers the entire workflow.
Asset tools change the shortlist
Unity Version Control appears at 6.7%, alongside Bitbucket at 6.2% and Subversion at 5.5%. Perforce reaches 4.3%, and Gitea is used by 3.8%. The choices extend well beyond the platforms at the top of the general company list. Bitbucket’s decline shows up here as well: among game developers, it fell from 10.2% in 2025.
Unity Version Control provides tools for code and content creators, including file checkout and locking. Perforce offers exclusive locking and configurable workspaces. These are practical reasons to include them in an evaluation if your team spends much of its time working with large assets.
What is happening among smaller Git platforms
In free-text answers, Gitea received more workplace mentions than Forgejo: 16 vs. 3. For personal projects, the order flipped: Codeberg had 40 mentions, Forgejo 29, and Gitea 21.
Developer Ecosystem 2026 · write-in answers
Codeberg and Forgejo lead for side projects, Gitea at work
Respondents who named the platform under “Other, please specify” (counts, not shares)
Forgejo is also closing the gap with Gitea. When we compare the same question wording year over year, Gitea led Forgejo 35 to 19 in personal-project mentions in 2025, and 54 to 48 in 2026. Among developers who reported using these platforms, Gitea stands out more in professional work, while Codeberg and Forgejo are more popular for personal projects.
Figures for additional platforms
The table below adds the smaller platforms and rough estimates behind the rest of the comparison.
Developer Ecosystem 2026
Smaller platforms: survey figures and write-in estimates
The ~ symbol marks a rough estimate from free-text answers. Details of the calculation and survey bases are in the source note below.
What’s next: version control for code written with AI agents
The survey shows where teams keep their code today. A newer question is what version control should record when AI agents write part of that code. A commit shows what changed, but not the prompt, the agent’s reasoning, or the alternatives it rejected.
Entire, a company founded by former GitHub CEO Thomas Dohmke, is one of the most visible attempts to close that gap. Its first product, Checkpoints, is an open-source CLI that saves an agent’s session context alongside each Git commit, on a separate branch so the main history stays clean.
Agents reinvented how we produce code. It changed our tools and half of our workflow. It’s time for the other half to catch up. Today, we’re shipping Entire: the Git forge for agent-human collaboration. We’ve built @GoEntire using Entire. Now we want to see what you’ll build with it. Here’s why and what’s different. 🧵— Thomas Dohmke (@ashtom) October 26, 2026
Agents reinvented how we produce code. It changed our tools and half of our workflow. It’s time for the other half to catch up. Today, we’re shipping Entire: the Git forge for agent-human collaboration. We’ve built @GoEntire using Entire. Now we want to see what you’ll build with it. Here’s why and what’s different. 🧵
It works with coding agents such as Claude Code and Gemini CLI. Entire launched in February 2026, so it doesn’t appear in our survey data, but it is a sign of where Git workflows may go next: Git stays the foundation, with new layers built on top for teams that work alongside agents.
Choose hosting and CI/CD platforms that match your workflow
You can choose your code hosting platform and CI/CD platform separately. For example, keep your code on GitHub and use TeamCity to build and test it.
TeamCity supports Git, Perforce, and Subversion. Its Pull Requests feature works with GitHub, GitLab, Bitbucket, and Azure DevOps, while Commit Status Publisher sends build statuses back to your repository. Developers can see whether their checks passed without leaving the code review.
So, which platform should you choose?
GitHub is a good starting point for projects with outside contributors. GitLab brings code hosting and CI/CD together. If your team already uses Jira or Azure DevOps, Bitbucket or Azure Repos may be a natural fit.
For self-hosted Git, consider Gitea or Forgejo. Codeberg offers hosting for free software projects. Game teams working with large assets should also look at Perforce and Unity Version Control.
Use the popularity figures to narrow your options. Then try them on a real project to see how they handle your code, reviews, and builds, and how much maintenance they require.
Where the data comes from
Figures come from the JetBrains Developer Ecosystem Report 2026. Professional-use figures are based on 4,519 respondents; personal-use figures are based on the 3,280 respondents who work on personal projects.
AWS CodeCommit, Space, and SourceForge figures and the year-over-year comparison come from a second 2026 hosting question that kept the 2025 answer list. Multiple answers were allowed; game development used a separate question with different options (n = 1,473).
The main hosting figures are weighted survey results. Values marked with a ~ symbol are rough estimates: unweighted shares of respondents who named the platform in a write-in answer. They are not official adoption rates. The fact that a solution has zero mentions does not mean it has zero use.












