Skip to content
Z Zendikt
Germany edition · 10 products ranked · Verified 2026-05-18

Top 10 Code Repository Software in Germany for 2026

Independent Germany code repository ranking: GitHub and GitLab at DAX 40, DSGVO on developer data, Mitbestimmung, Codeberg and Forgejo for German FOSS hosting.

Germany verdict (TL;DR)

Verified 2026-05-18

GitHub and GitLab dominate German commercial code hosting. Germany has the strongest self-hosted Git adoption of any large EU market: Bosch, BMW Group (BMW Software Factory), and SAP run self-hosted GitLab on German infrastructure as the primary SCM for production software. SAP runs both internal GitHub Enterprise and self-hosted GitLab across different product divisions. DSGVO imposes specific obligations on code repositories because developer activity logs (commit author, branch names, timestamps) are employee personal data under German data protection law; German data protection authorities have issued guidance on this. Mitbestimmung requires works council consultation before deploying code repository features that monitor developer productivity or activity metrics. Codeberg (Berlin-based non-profit, Forgejo-based) is the leading German code hosting alternative to GitHub and GitLab, used by German FOSS projects, public interest tech organizations, and privacy-conscious German developers. The German Federal Government's open-source portal (opencode.de) runs on GitLab, a deliberate sovereignty choice. Azure DevOps Repos is present in German enterprises fully committed to Microsoft Azure. Bitbucket appears in German Atlassian-stack shops.

Picks for Germany

  • German tech companies and modern DAX 40 digital teams: github GitHub is the default for German SaaS companies and modern DAX 40 digital units on GitHub. GitHub Enterprise with EU data residency option and DSGVO Data Processing Agreement satisfies most German DSGVO requirements.
  • German enterprise and DAX 40 sovereignty-first SCM: gitlab Self-hosted GitLab on German infrastructure (Hetzner, T-Systems, Deutsche Telekom data centers) is the standard for Bosch, BMW Group, and German enterprises requiring source code to remain on German-controlled servers.
  • German FOSS community and public interest tech: codeberg Codeberg e.V. is a Berlin-based non-profit operating Codeberg.org on Forgejo with German data residency. Used by German open-source projects, KDE-adjacent developers, and the broader German privacy-first developer community.
  • German sovereignty-aware self-hosted Git (small teams): forgejo Forgejo is the AGPL-licensed FOSS Gitea fork created in 2022, backed by Codeberg. Self-hosted on Hetzner or on-premises. Popular in German federal agency open-source projects and "Digitale Souveranitat" initiatives.
  • German Microsoft-stack enterprises and public sector: azure-devops-repos Azure DevOps on Azure Germany Cloud (Frankfurt) satisfies German DSGVO data-residency requirements. Present in German BFSI organizations (Allianz, Deutsche Bank units) on Microsoft Azure.
Market context

How the code repository / version control market looks in Germany

Germany's code repository market is the most self-hosted-oriented large EU market. The combination of DSGVO, strong corporate IT sovereignty culture, Mitbestimmung, and the German free-software tradition creates structural preferences for on-premises or German-cloud-hosted SCM that do not exist in the same strength elsewhere.

The DAX 40 pattern is instructive. Bosch runs self-hosted GitLab (Bosch DevCloud) for its automotive software development teams (Bosch employs 40,000+ software engineers). BMW Group's BMW Software Factory runs GitLab self-managed on German data center infrastructure for its autonomous driving and connected car software development. SAP is the most complex case: with 100,000+ developers, SAP runs GitHub Enterprise for parts of its BTP and cloud-native product lines and self-hosted GitLab for others; the split reflects different engineering culture within product divisions and pre-existing SCM investments.

The German Federal Government's digital strategy has explicitly addressed code hosting sovereignty. Opencode.de, the German Federal Government's open-source code portal, runs on GitLab self-managed on Bundescloud (German federal cloud) infrastructure. This is a deliberate policy choice by the Bundesministerium des Innern (BMI) and the Zentrum fur Digitale Souveranitat (ZenDiS) to host federal open-source code on German-controlled infrastructure rather than GitHub.com.

Codeberg is the most significant Germany-specific player in this market. Codeberg e.V. is a Berlin-based non-profit (registered Verein) operating Codeberg.org, which runs Forgejo (the AGPL-licensed community fork of Gitea). Codeberg has German data residency, non-commercial governance, and AGPL-licensed infrastructure, making it the natural choice for German FOSS projects, academic institutions, and public interest organizations that object to GitHub's Microsoft ownership or GitLab's commercial nature. KDE (the German-originated open desktop environment) has moved significant infrastructure to Invent.KDE.org (self-hosted GitLab). GNOME, though originally US-founded, uses GitLab on GNOME's own infrastructure.

DSGVO is the most legally consequential code repository compliance requirement in Germany. German data protection authorities (Bayerisches Landesamt fur Datenschutzaufsicht, LfDI Baden-Wurttemberg) have ruled that developer activity logs (commit author, timestamps, branch names, pull request authorship) constitute employee personal data under DSGVO. This means repositories hosted on US-operated SaaS (GitHub.com, GitLab.com) create DSGVO data transfer issues for German employee data. German enterprises handle this via SCCs with GitHub (acceptable under German DPA guidance with supplementary measures) or by self-hosting on German infrastructure. Many German IT departments mandate self-hosted SCM specifically to eliminate the DSGVO transfer question.

Compliance & local rules

DSGVO: developer activity data in code repositories (commit author identity, branch names, PR authorship, timestamps) is employee personal data under DSGVO in the German legal interpretation; repositories on US-operated SaaS require Standard Contractual Clauses and Transfer Impact Assessments; self-hosted SCM on German infrastructure eliminates the transfer issue. Mitbestimmung: Betriebsverfassungsgesetz section 87(1) Nr. 6 requires works council consultation before deploying SCM features that monitor employee productivity or activity metrics; per-developer contribution analytics, AI-generated developer productivity scores, and detailed commit activity dashboards all trigger Mitbestimmung review; negotiate Betriebsvereinbarung before enabling these features. BSI C5 attestation: German regulated entities (KRITIS operators, BaFin-supervised firms) should use cloud infrastructure with BSI C5 attestation for SCM hosting; GitHub (Azure, C5-attested), GitLab (AWS Frankfurt, C5-attested), Azure DevOps (Azure Germany, C5-attested), Hetzner (partial C5 coverage), and T-Systems Open Telekom Cloud (C5-attested) are the primary options. NIS2UmsuCG: German operators in scope for NIS2UmsuCG must include SCM access control in their ICT supply chain risk management; unauthorized SCM access is a reportable incident to BSI. Opencode.de policy: German federal agencies publishing open-source code should use opencode.de (GitLab-based Bundescloud) as the primary publication point under ZenDiS guidance.

At a glance

Quick comparison, ranked for Germany

Product Best for Starts at 10-emp/mo* Pricing G2 Geo
1 GitHub
Any organization writing software, from solo developers to Fortune 500 enterprises
$0 + $0/emp $0 4.7 Global; strongest in US, EU, UK, India, Japan
2 GitLab
Engineering organizations wanting consolidated DevSecOps
$0 + $0/emp $0 4.5 Global; strongest in US, EU, UK, Germany, India
8 Codeberg
OSS projects, ethical-tech orgs, EU sovereignty buyers
$0 + $0/emp $0 4.7 Global; EU data residency (Berlin, Germany)
10 Forgejo
Ethical-tech, public-sector, NGO, and FOSS-aligned orgs
$0 + $0/emp $0 4.6 Global; self-hosted anywhere; Codeberg-hosted EU
5 Azure DevOps Repos
Microsoft-anchored enterprises and .NET shops
$0 + $0/emp $0 4.1 Global; strongest in US, EU, UK
3 Bitbucket
Atlassian-anchored organizations
$0 + $0/emp $0 4.3 Global; strongest in US, EU, Australia
7 Gitea
Small to mid-size teams wanting self-hosted Git
$0 + $0/emp $0 4.6 Global; self-hosted anywhere
4 Sourcegraph
Monorepo and large multi-repo enterprises
$0 + $0/emp $0 4.4 Global; strongest in US, EU
6 AWS CodeCommit
No greenfield use case; existing AWS-anchored customers
$0 + $0/emp $0 4.1 AWS regions (US, EU, AU, AP, CA)
9 Phorge
Organizations with active Phabricator deployments
$0 + $0/emp $0 4.3 Global; self-hosted anywhere

*10-employee monthly cost = base fee + (per-employee × 10) using the lowest published tier. For opaque-pricing vendors, no value is shown.

Verified local pricing

What buyers in Germany actually pay

Median annual deal size by employee band, in EUR. Crowdsourced from anonymized buyer disclosures.

Product Employee band Median annual (EUR) Sample Notes
GitHub GitHub Enterprise (per user/month, EUR) €230 148 Approx EUR 19/user/month; GitHub EU data residency; DSGVO DPA included; EUR-billed
GitLab GitLab Ultimate self-managed (per user/year) €1,140 112 EUR 95/user/month; Hetzner hosting EUR 50-500/month additional; common DAX 40 pattern
GitLab GitLab Premium self-managed (per user/year) €570 94 EUR 47.50/user/month; self-hosted; most cost-effective for 200+ user deployments
Codeberg Codeberg.org (free, donation) €0 67 Free; donation-funded non-profit; German data residency; public and private repos
Azure DevOps Repos Azure DevOps Basic (per user/month) €75 58 EUR 6.20/user/month; Azure Germany (Frankfurt); first 5 users free
Local challengers

Germany-built or Germany-strong vendors worth knowing

Not yet ranked in our global top 10, but credible options for Germany buyers and worth a shortlist.

Codeberg

Visit ↗

Berlin-based non-profit (Codeberg e.V.). Operates Codeberg.org on Forgejo with German data residency and non-commercial governance. The most credible German alternative to GitHub for FOSS projects, academic institutions, and public interest organizations. Used by KDE contributors, Framasoft-adjacent projects, and the "Digitale Souveranitat" developer community. Not an enterprise platform.

opencode.de (ZenDiS)

Visit ↗

Berlin-based Zentrum fur Digitale Souveranitat (ZenDiS), operating under BMI. Operates opencode.de as the German Federal Government's open-source code portal on GitLab self-managed on Bundescloud. German federal agencies publishing open-source code should use opencode.de. Not a commercial product.

Hetzner Cloud (SCM hosting)

Visit ↗

Nuremberg-based Hetzner is the preferred German cloud provider for self-hosted GitLab and Gitea by German SME and mid-market organizations wanting German data residency without enterprise cloud pricing. Fully German-owned, GDPR-native. Not a code repository platform, but the most common German infrastructure substrate for self-hosted SCM.

Excluded for Germany

Global picks that don't fit here

  • AWS CodeCommit
    AWS deprecated new-customer onboarding July 25, 2024. German teams on AWS should migrate to GitHub or GitLab. No Germany-specific considerations justify continued CodeCommit adoption.
  • Phorge
    Negligible Germany adoption. German developers preferring self-hosted workflow-oriented SCM overwhelmingly choose Forgejo or Gitea over Phorge. German open-source community has not adopted Phabricator workflows historically.
  • Sourcegraph
    Very thin German enterprise adoption as of 2026. German enterprises with large monorepo code intelligence needs are potential Sourcegraph customers, but procurement has not materialized at scale. German self-hosted preference and DSGVO complexity for US SaaS slows Sourcegraph Enterprise adoption. Revisit in 2027.
The Germany ranking

All 10, ranked for Germany

Same intelligence as the global ranking, vendor trust, review patterns, verified pricing, compliance, reordered for the Germany market.

#1

GitHub

The default code repository for modern software engineering.

Founded 2008 · San Francisco, CA · public · 1 to 500,000+ employees
G2 4.7 (2,480)
Capterra 4.8
From $0 + $0 /mo + /employee
● Transparent pricing
Visit GitHub

GitHub is the dominant code repository platform, with roughly 100M developers reported in 2024 and the broadest integration ecosystem in developer tools. Microsoft acquired GitHub in 2018 for $7.5B and has expanded the platform aggressively, embedding Copilot, Actions (CI/CD), Advanced Security, Codespaces, and increasingly agentic workflows. The product is the industry default and the most common procurement starting point. Trade-offs: pricing has crept up at Enterprise tiers, Copilot is increasingly required to capture full value (separate per-seat add-on), Codespaces pricing changes in 2024 caught buyers off guard, and the 2022 Copilot lawsuit (DOE plaintiffs) is still working through the courts.

Best for

Almost any modern engineering organization, from solo developers and OSS maintainers through Fortune 500 enterprises. The rational default for greenfield repo decisions in 2026.

Worst for

Ethical-tech and FOSS-purist organizations rejecting Microsoft ownership (Codeberg/Forgejo better), EU data-sovereignty buyers wanting native EU non-profit (Codeberg better), or air-gap regulated environments without GitHub Enterprise Server (GitLab Self-Managed or Gitea better).

Strengths

  • Industry default with ~100M developers and broadest integration ecosystem
  • Bundled Actions (CI/CD), Packages, Codespaces, Copilot, Advanced Security
  • Strongest developer community and marketplace (20,000+ Actions)
  • Microsoft parent stability and procurement reach
  • Free public-repo tier is genuinely usable for individuals and OSS
  • Strong SAML SSO, SCIM, and audit logging at Enterprise
  • Copilot deeply integrated; agentic features expanding (Workspace, Agent Mode)

Weaknesses

  • Enterprise pricing has crept up through 2023-2025 contract renewals
  • Copilot is a separate per-seat add-on; full AI capability requires it
  • Codespaces 2024 pricing changes blindsided some buyers
  • 2022 Copilot lawsuit (DOE plaintiffs) ongoing; IP indemnity questions persist
  • Microsoft-default lock-in for organizations that resist Azure / Microsoft 365
  • Outage history: multiple multi-hour incidents in 2023-2024 across Actions and PRs

Pricing tiers

public
  • Free
    Unlimited public and private repos with limited Actions minutes and Codespaces hours
    $0+$0 /mo +/emp
  • Team
    Per user; protected branches, code owners, 3,000 Actions minutes
    $4+$4 /mo +/emp
  • Enterprise Cloud
    Per user; SAML SSO, SCIM, audit log, 50,000 Actions minutes
    $21+$21 /mo +/emp
  • Enterprise Server
    Self-hosted GitHub Enterprise; annual contract
    Quote
  • Copilot Business add-on
    Per user, separate from GitHub seat
    $19+$19 /mo +/emp
Watch for
  • · Copilot is a separate per-seat add-on at $19/user/mo (Business) or $39/user/mo (Enterprise)
  • · Actions minutes overages billed per-minute; macOS runners cost roughly 10x Linux
  • · Advanced Security is a separate add-on (~$49/active committer/mo)
  • · Codespaces compute and storage billed separately; 2024 pricing changes affected buyers
  • · GitHub Enterprise Server requires annual contract with implementation services

Key features

  • +Git hosting with unlimited public and private repos
  • +Pull requests with code review, branch protection, code owners
  • +GitHub Actions CI/CD bundled with usage allowance
  • +GitHub Packages for npm, Maven, Docker, NuGet, RubyGems
  • +Codespaces cloud development environments
  • +GitHub Copilot AI coding (separate add-on)
  • +GitHub Advanced Security (SAST, secret scanning, Dependabot)
  • +GitHub Enterprise Server for self-hosted deployment
  • +SAML SSO, SCIM provisioning, audit log streaming
  • +Issues, Projects, Discussions, Wikis, Pages
9000+ integrations
SlackJiraLinearVercelAWSAzureGoogle CloudDatadogSentrySnyk
Geography
Global; strongest in US, EU, UK, India, Japan
#2

GitLab

All-in-one DevSecOps platform spanning repo, CI/CD, security, and AI.

Founded 2011 · San Francisco, CA · public · 10 to 50,000+ employees
G2 4.5 (1,320)
Capterra 4.5
From $0 + $0 /mo + /employee
● Transparent pricing
Visit GitLab

GitLab is the credible all-in-one DevSecOps alternative to GitHub, IPO completed on NASDAQ as GTLB in October 2021, and reporting approximately $590M revenue for FY25. The product differentiator is consolidation: one platform covering Git hosting, CI/CD, container registry, security scanning (SAST, DAST, dependency, container, secret detection), and the Duo AI assistant. Best fit for buyers wanting one DevSecOps vendor instead of stitching GitHub + Actions + third-party security. Trade-offs: the 2023 tier reshuffle that raised Premium and removed features pushed some customers to GitHub, Duo is a per-seat add-on (not bundled), the platform footprint is heavy for teams that just want a repo, and self-managed installations require meaningful operational investment.

Best for

Engineering organizations (50 to 50,000+) wanting one DevSecOps vendor instead of GitHub plus separate CI/CD, security scanning, and registry vendors. Particularly strong for regulated industries running GitLab Self-Managed on-prem.

Worst for

Small teams that just need a repo (GitHub or Gitea simpler and cheaper), Atlassian-anchored shops (Bitbucket native to Jira/Confluence), or ethical-tech buyers wanting non-profit governance (Codeberg better).

Strengths

  • All-in-one DevSecOps: repo, CI/CD, registry, SAST, DAST, secret scanning, Duo AI
  • Single vendor TCO advantage versus GitHub + add-ons + third-party security
  • Strong self-managed (on-prem) deployment option for regulated industries
  • Public company (NASDAQ:GTLB) with audited financials and roadmap transparency
  • Open-core model with permissive Community Edition
  • Built-in compliance frameworks and audit events at Premium and Ultimate
  • Mature merge request workflow and code review

Weaknesses

  • Duo AI is a separate per-seat add-on; not bundled in any tier
  • 2023 tier reshuffle raised Premium and moved features behind Ultimate
  • Self-managed installations require non-trivial operational investment
  • Smaller marketplace and third-party integration ecosystem than GitHub
  • AI Pricing controversy in 2024 (Duo per-seat add-on) drew customer pushback
  • UI complexity reported by single-feature buyers wanting only repo

Pricing tiers

public
  • Free
    SaaS or self-managed; limited CI minutes and seats
    $0+$0 /mo +/emp
  • Premium
    Per user; advanced CI/CD, compliance, support
    $29+$29 /mo +/emp
  • Ultimate
    Per user; SAST, DAST, security dashboard, portfolio management
    $99+$99 /mo +/emp
  • Duo Pro add-on
    Per user; AI code suggestions and chat
    $19+$19 /mo +/emp
  • Duo Enterprise add-on
    Per user; advanced AI features for Ultimate
    $39+$39 /mo +/emp
Watch for
  • · Duo AI is a separate per-seat add-on (not bundled in Premium or Ultimate)
  • · Ultimate-only features (SAST, DAST, security dashboard) often push buyers up from Premium
  • · Self-managed deployment requires infrastructure and ops investment
  • · CI minutes and storage overages metered separately on SaaS

Key features

  • +Git hosting with unlimited repos (SaaS) or self-managed
  • +Merge requests with code review and approval rules
  • +Built-in GitLab CI/CD with runners (SaaS and self-managed)
  • +Container Registry, Package Registry, Helm Chart Registry
  • +Built-in security scanning (SAST, DAST, secret, dependency, container)
  • +GitLab Duo AI (code suggestions, chat, vulnerability explanation)
  • +Compliance frameworks and audit events (Premium/Ultimate)
  • +Self-managed deployment for on-prem / air-gap
  • +SAML SSO, SCIM, granular role-based access
  • +Value Stream Management and DORA metrics
350+ integrations
JiraSlackMicrosoft TeamsAWSGCPKubernetesDatadogPagerDutySnykHashiCorp Vault
Geography
Global; strongest in US, EU, UK, Germany, India
#8

Codeberg

Non-profit EU-headquartered Git hosting for ethical-tech and OSS.

Founded 2019 · Berlin, Germany · private · 1 to 500 employees
G2 4.7 (180)
Capterra 4.7
From $0 + $0 /mo + /employee
● Transparent pricing
Visit Codeberg

Codeberg is the non-profit, EU-headquartered Git hosting platform run by Codeberg e.V. a registered German association (eingetragener Verein). The platform is Forgejo-based (powered by the Forgejo hard fork of Gitea), free for OSS, and explicitly positioned as the ethical-tech alternative to GitHub for buyers prioritizing non-profit governance, EU data residency, and FOSS values. Codeberg is funded by donations and member dues, not VC capital, and explicitly rejects business models that train on user code or sell user data. Best fit for OSS projects, EU sovereignty buyers, ethical-tech organizations, and individual developers rejecting Microsoft-owned GitHub. Trade-offs: smaller community and integration ecosystem than GitHub, no AI features (intentional), no managed enterprise tier, and resources are donation-bounded.

Best for

OSS projects, EU sovereignty buyers, ethical-tech organizations, FOSS-anchored developers, and individuals rejecting Microsoft GitHub on governance grounds.

Worst for

Enterprise organizations requiring SLA-backed managed service (GitHub Enterprise or GitLab better), AI-anchored teams (Codeberg is intentionally AI-free), or buyers needing deep integration ecosystem.

Strengths

  • Non-profit governance (Codeberg e.V. German registered association)
  • Native EU data residency (Berlin-headquartered)
  • Forgejo-based (community-governed hard fork of Gitea)
  • Free for OSS projects
  • Explicit no-training-on-code, no-AI-extraction policy
  • Funded by donations and member dues (not VC capital)
  • Strong fit for ethical-tech, OSS, and EU sovereignty buyers

Weaknesses

  • Smaller community and integration ecosystem than GitHub
  • No AI features (intentional; not a fit for AI-anchored teams)
  • No managed enterprise tier (donation-bounded resources)
  • Smaller marketplace and third-party integrations
  • Limited support (community-only)
  • No SLA guarantees (donation-funded infrastructure)

Pricing tiers

public
  • Free (OSS and personal)
    Free for everyone; donations encouraged
    $0+$0 /mo +/emp
  • Sustaining Member
    Per individual; voluntary support of Codeberg e.V.
    $5 /mo
  • Organization Member
    Organizational support via Codeberg e.V. membership
    Quote
Watch for
  • · Donation-funded; no SLA guarantees
  • · No paid enterprise support tier

Key features

  • +Git hosting (Forgejo-based)
  • +Pull requests with code review
  • +Issues, milestones, project boards
  • +Wiki and project pages
  • +Codeberg CI (Woodpecker CI-based)
  • +Codeberg Pages (static site hosting)
  • +Mirror from GitHub, GitLab, etc.
  • +No tracking, no pattern extraction, no training on user code
  • +EU data residency (Berlin)
  • +Non-profit governance via Codeberg e.V.
30+ integrations
Woodpecker CIDrone CIForgejo ActionsMatrixXMPP
Geography
Global; EU data residency (Berlin, Germany)
#10

Forgejo

Community-governed hard fork of Gitea, backed by Codeberg e.V.

Founded 2022 · Distributed (Codeberg e.V. Berlin) · private · 1 to 500 employees
G2 4.6 (140)
Capterra 4.6
From $0 + $0 /mo + /employee
● Transparent pricing
Visit Forgejo

Forgejo is the community-governed hard fork of Gitea, started in October 2022 by Gitea contributors after the 2022 formation of for-profit Gitea Limited prompted IP-rights and governance concerns. The project is hosted under Codeberg e.V. (the non-profit German association behind Codeberg) and operates on community-first governance principles. Forgejo powers Codeberg and a growing number of self-hosted instances at NGOs, public-sector deployments, and ethical-tech organizations. Best fit for buyers wanting Gitea-like functionality with community governance and IP-rights clarity. Trade-offs: very small community relative to GitHub or GitLab, no AI features (intentional), and adoption is mostly limited to ethical-tech and FOSS-aligned segments.

Best for

Ethical-tech buyers wanting Gitea-like functionality with community governance, EU public-sector deployments, NGOs, and FOSS-aligned organizations rejecting both GitHub corporate ownership and Gitea Limited.

Worst for

Enterprise organizations requiring deep SSO/SCIM/compliance (GitLab Self-Managed better), AI-anchored teams (Forgejo is intentionally AI-free), or buyers wanting commercial managed SaaS (Codeberg or Gitea Cloud closer fits).

Strengths

  • Community-governed hard fork with explicit IP-rights protections
  • Backed by Codeberg e.V. non-profit governance
  • Gitea-compatible feature set (PRs, issues, wiki, CI/CD)
  • Forgejo Actions (GitHub Actions-compatible CI/CD)
  • BSD-licensed (open-source)
  • Strong fit for ethical-tech, public-sector, and FOSS buyers
  • Active migration path from Gitea

Weaknesses

  • Very small community relative to GitHub or GitLab
  • No AI features (intentional; not a fit for AI-anchored teams)
  • No commercial managed SaaS at Codeberg-equivalent scale beyond Codeberg itself
  • Smaller integration ecosystem
  • Enterprise features (SCIM, advanced audit) less mature than GitLab Self-Managed
  • Adoption mostly limited to ethical-tech and FOSS-aligned segments

Pricing tiers

public
  • Self-hosted (open-source)
    BSD-licensed; self-host with no fee
    $0+$0 /mo +/emp
  • Codeberg-hosted
    Free via Codeberg (donation-funded)
    $0 /mo
Watch for
  • · Self-hosted infrastructure and ops costs
  • · No managed SaaS option beyond Codeberg

Key features

  • +Git hosting (single-binary, Gitea-compatible)
  • +Pull requests with review and protected branches
  • +Issues, milestones, labels, project boards
  • +Wiki and project pages
  • +Forgejo Actions (GitHub Actions-compatible CI/CD)
  • +Package registry (npm, Maven, Docker, etc.)
  • +OAuth and OIDC SSO
  • +Federation roadmap (ActivityPub)
  • +Migration tools from Gitea, GitHub, GitLab
30+ integrations
Woodpecker CIDrone CIGitHub (mirror)GitLab (mirror)MatrixSlack
Geography
Global; self-hosted anywhere; Codeberg-hosted EU
#5

Azure DevOps Repos

Microsoft-anchored Git hosting bundled with Azure DevOps Services and Server.

Founded 2018 · Redmond, WA · public · 5 to 100,000+ employees
G2 4.1 (880)
Capterra 4.4
From $0 + $0 /mo + /employee
● Transparent pricing
Visit Azure DevOps Repos

Azure DevOps Repos is the Git hosting component of Azure DevOps Services (cloud) and Azure DevOps Server (on-prem, formerly TFS), the Microsoft legacy enterprise DevOps suite. The product is bundled with Boards, Pipelines, Test Plans, and Artifacts. Best fit is Microsoft-anchored enterprises with legacy TFS (Team Foundation Server) investments, regulated industries running Azure DevOps Server on-prem, and .NET shops deep in the Microsoft ecosystem. Trade-offs: Microsoft itself has consistently steered new customers to GitHub since the 2018 acquisition, Azure DevOps roadmap velocity is materially slower than GitHub, AI features are GitHub-first (Copilot is not native to Azure DevOps Repos), and developer mindshare is dominated by GitHub even inside Microsoft.

Best for

Microsoft-anchored enterprises with legacy TFS investments, regulated industries running Azure DevOps Server on-prem, and .NET shops deep in Visual Studio and the Microsoft ecosystem.

Worst for

Greenfield repo decisions inside or outside Microsoft (GitHub Enterprise is the Microsoft-internal default for new projects), AI-first teams (GitHub Copilot is not natively integrated), or buyers wanting fastest roadmap velocity (GitHub roadmap moves faster).

Strengths

  • Bundled with Azure DevOps Services or Server (Boards, Pipelines, Test, Artifacts)
  • Azure DevOps Server provides mature on-prem deployment for regulated industries
  • Native integration with Visual Studio and .NET tooling
  • Microsoft enterprise procurement and EA bundling
  • Strong legacy TFS migration path (TFVC and Git)
  • Free for up to 5 users

Weaknesses

  • Microsoft steers new customers to GitHub; Azure DevOps is legacy-anchored
  • Roadmap velocity materially slower than GitHub
  • AI features GitHub-first; Copilot not native to Azure DevOps Repos
  • UI dated relative to GitHub or GitLab
  • Smaller developer mindshare and community
  • Future of Azure DevOps Server post-2027 unclear; Microsoft has not committed beyond current support windows

Pricing tiers

public
  • Free
    Up to 5 users; Basic features
    $0+$0 /mo +/emp
  • Basic
    Per user beyond first 5; Boards, Repos, Pipelines, Artifacts
    $6+$6 /mo +/emp
  • Basic + Test Plans
    Per user; adds Test Plans manual testing
    $52+$52 /mo +/emp
  • Azure DevOps Server
    Self-hosted; CAL-based licensing with annual contract
    Quote
Watch for
  • · Test Plans is a meaningful uplift over Basic
  • · Pipelines parallel jobs metered separately beyond included quota
  • · Azure DevOps Server requires CALs and annual contract
  • · Migration to GitHub Enterprise often recommended by Microsoft sales

Key features

  • +Git hosting with unlimited private repos
  • +Pull requests with policies, code review, branch protection
  • +TFVC (Team Foundation Version Control) support for legacy projects
  • +Azure Pipelines CI/CD
  • +Azure Boards (work tracking)
  • +Azure Artifacts (package management)
  • +Azure Test Plans (manual and exploratory testing)
  • +Self-hosted Azure DevOps Server
  • +Azure Active Directory SSO and group integration
  • +Visual Studio and .NET native integration
1000+ integrations
Visual StudioAzureGitHub (cross-link)Microsoft TeamsSlackJiraServiceNow
Geography
Global; strongest in US, EU, UK
#3

Bitbucket

Atlassian-anchored Git hosting with native Jira and Confluence integration.

Founded 2008 · Sydney, Australia · public · 5 to 10,000+ employees
G2 4.3 (1,040)
Capterra 4.4
From $0 + $0 /mo + /employee
● Transparent pricing
Visit Bitbucket

Bitbucket is the Atlassian Git hosting platform (NASDAQ:TEAM), a distant #3 in the category that survives largely on Atlassian-bundled procurement. The product strength is native integration with Jira, Confluence, and the broader Atlassian portfolio. Trade-offs are substantial: the Bitbucket Server (self-hosted) end-of-life on Feb 15, 2024 forced large-scale cloud migration with double-digit price increases that drew significant customer pushback. Atlassian Pipelines (CI/CD) lacks feature parity with GitHub Actions or GitLab CI, the AI story (Atlassian Intelligence) lags Copilot and Duo materially, and the platform has lost developer mindshare consistently through 2022-2025. Best fit is Atlassian-anchored shops where Jira and Confluence are non-negotiable.

Best for

Atlassian-anchored organizations where Jira and Confluence are mandatory, particularly mid-market and enterprise teams that already pay Atlassian and want bundled procurement.

Worst for

Greenfield repo decisions (GitHub or GitLab better), modern DevSecOps consolidation (GitLab better), or AI-first engineering teams (Copilot and Duo are years ahead of Atlassian Intelligence).

Strengths

  • Native Jira and Confluence integration (commit/PR linking, smart commits)
  • Atlassian Marketplace and procurement bundled with broader Atlassian portfolio
  • Free tier for up to 5 users (small teams and OSS-adjacent)
  • Bitbucket Pipelines included with subscription (minutes-based)
  • SAML SSO and SCIM at Premium tier
  • Established product (since 2008) with deep enterprise install base

Weaknesses

  • Bitbucket Server end-of-life Feb 15, 2024 forced cloud migration with price increases
  • Atlassian Pipelines lacks feature parity with GitHub Actions or GitLab CI
  • Atlassian Intelligence AI story lags Copilot and Duo materially
  • Developer mindshare declining consistently 2022-2025
  • Outage history: extended Atlassian Cloud incident April 2022 (multi-day, customer-impacting)
  • Smaller integration ecosystem than GitHub or GitLab

Pricing tiers

public
  • Free
    Up to 5 users; 50 build minutes/mo
    $0+$0 /mo +/emp
  • Standard
    Per user; 2,500 build minutes/mo
    $3.3+$3.3 /mo +/emp
  • Premium
    Per user; 3,500 build minutes/mo, SAML SSO, deployment permissions
    $6.6+$6.6 /mo +/emp
  • Data Center (self-hosted)
    Annual contract for self-managed Bitbucket Data Center
    Quote
Watch for
  • · Pipelines minutes overages billed per-minute
  • · LFS storage billed separately beyond included quota
  • · Atlassian Intelligence (AI) is a separate add-on at higher tiers
  • · Bitbucket Server (legacy self-hosted) end-of-life Feb 15, 2024 forced cloud or Data Center migration
  • · Data Center pricing increased through 2023-2024 contract renewals

Key features

  • +Git hosting with unlimited private repos
  • +Pull requests with code review and required reviewers
  • +Bitbucket Pipelines CI/CD (minutes-based)
  • +Native Jira and Confluence integration (smart commits)
  • +Atlassian Marketplace integrations
  • +SAML SSO and SCIM (Premium)
  • +Deployment permissions and merge checks (Premium)
  • +Bitbucket Data Center for self-managed deployment
  • +Mirroring and Git LFS support
  • +Atlassian Intelligence (limited AI features)
200+ integrations
JiraConfluenceTrelloOpsgenieAWSSlackMicrosoft TeamsSentry
Geography
Global; strongest in US, EU, Australia
#7

Gitea

Lightweight self-hosted Git server, BSD-licensed, mature.

Founded 2016 · Cupertino, CA · private · 1 to 200 employees
G2 4.6 (320)
Capterra 4.6
From $0 + $0 /mo + /employee
● Transparent pricing
Visit Gitea

Gitea is the leading lightweight self-hosted Git server, forked from Gogs in 2016 by community contributors. The product is BSD-licensed (open-source), runs on a single binary with minimal dependencies, and is designed for teams that want self-hosted Git without GitLab Self-Managed operational burden. In 2022, Gitea Limited (a for-profit corporate entity) was formed to manage the project, which prompted community concerns about IP rights and led to the Forgejo hard fork (covered separately at rank 10). Gitea Cloud (managed SaaS) launched 2023. Best fit for small to mid-size teams wanting self-hosted Git with low ops overhead. Trade-offs: the 2022 corporate-fork controversy created lasting community trust questions, AI features are absent, and the integration ecosystem is materially smaller than GitHub or GitLab.

Best for

Small to mid-size teams (1 to 200 engineers) wanting self-hosted Git with low operational overhead, OSS projects, homelab developers, and educational institutions.

Worst for

Enterprise organizations requiring deep SSO/SCIM/compliance (GitLab Self-Managed or GitHub Enterprise Server better), AI-anchored teams (Copilot or Duo required), or buyers prioritizing pure community governance (Codeberg or Forgejo better).

Strengths

  • Lightweight single-binary deployment (minimal ops burden)
  • BSD-licensed open-source with permissive community fork rights
  • Mature feature set (PRs, issues, wiki, code review, CI/CD)
  • Gitea Cloud managed SaaS option since 2023
  • Low resource requirements (runs on Raspberry Pi or small VPS)
  • Strong fit for homelab, OSS hosting, and small-team self-hosting

Weaknesses

  • 2022 corporate-fork controversy (Gitea Limited formation) created community trust questions
  • Forgejo hard fork (October 2022) split community
  • No AI features (no Copilot equivalent)
  • Integration ecosystem materially smaller than GitHub or GitLab
  • Enterprise features (SSO, audit logging) less mature than GitLab
  • No managed cloud option at GitHub or GitLab scale

Pricing tiers

public
  • Self-hosted (open-source)
    BSD-licensed; self-host with no fee
    $0+$0 /mo +/emp
  • Gitea Cloud Free
    Managed SaaS; limited repos and users
    $0+$0 /mo +/emp
  • Gitea Cloud Basic
    Per organization; expanded usage
    $19 /mo
  • Gitea Cloud Premium
    Per organization; advanced features and support
    $99 /mo
  • Gitea Enterprise
    Self-hosted with paid support contract
    Quote
Watch for
  • · Self-hosted infrastructure and ops costs
  • · No managed SLA on open-source self-hosted
  • · Gitea Enterprise support contract pricing not publicly listed

Key features

  • +Git hosting (single-binary)
  • +Pull requests with review and protected branches
  • +Issues, milestones, labels
  • +Wiki and project pages
  • +Gitea Actions (CI/CD, GitHub Actions compatible runners)
  • +Package registry (npm, Maven, Docker, etc.)
  • +Webhooks and integration triggers
  • +OAuth and OIDC SSO
  • +Migration tools from GitHub, GitLab, Bitbucket
50+ integrations
Drone CIWoodpecker CIJenkinsGitHub (migration)GitLab (migration)SlackDiscord
Geography
Global; self-hosted anywhere
#4

Sourcegraph

Code search and AI code intelligence (Cody) for monorepo enterprises.

Founded 2013 · San Francisco, CA · private · 50 to 50,000+ employees
G2 4.4 (480)
Capterra 4.5
From $0 + $0 /mo + /employee
◐ Partial disclosure
Visit Sourcegraph

Sourcegraph is the code-search and code-intelligence platform that sits adjacent to (not replacing) GitHub, GitLab, and Bitbucket repositories. Founded 2013, last priced Series D $125M in 2022 at a $2.625B valuation. The product strength is universal code search across multiple repositories and Git hosts, plus the Cody AI assistant which anchors on the code-search foundation for stronger context retrieval in massive monorepos. Best fit for enterprises with millions of LOC across many repos where finding and understanding code is the actual bottleneck. Trade-offs: Sourcegraph is not a repo host (you still pay GitHub or GitLab), the 2024-2025 paid-tier shift moved features behind Enterprise that were previously available cheaper, and the product is overkill for small codebases.

Best for

Enterprises with massive codebases (millions of LOC, monorepo or multi-repo) where code search and understanding is the primary bottleneck (50 to 50,000 engineers). Particularly strong for organizations with legacy code that resists onboarding.

Worst for

Small codebases and single-repo teams (GitHub search sufficient), individual developers (Cursor or Copilot cheaper), or buyers wanting a repo host (Sourcegraph is adjacent, not replacement).

Strengths

  • Native code search across multiple repositories and Git hosts
  • Cody AI assistant anchored on code-search context (strong monorepo awareness)
  • Self-hosted Enterprise deployment for air-gap and regulated industries
  • Integrations with GitHub, GitLab, Bitbucket, Azure DevOps, Gerrit, Perforce
  • Code Insights for repo analytics and refactoring tracking
  • Multiple model options in Cody (Claude, GPT, etc.)

Weaknesses

  • Not a repo host; layered on top of GitHub or GitLab (additional spend)
  • 2024-2025 paid-tier shift moved features behind Enterprise
  • Overkill for small codebases and single-repo teams
  • Cody agentic features arrived later than Cursor and Claude Code
  • Adoption requires Sourcegraph foundation deployment effort
  • Pricing meaningful at enterprise scale

Pricing tiers

partial
  • Free (Cody only)
    Individual Cody with limited prompts
    $0+$0 /mo +/emp
  • Pro (Cody)
    Per user; individual Cody Pro
    $9+$9 /mo +/emp
  • Enterprise Starter
    Per user; team Cody and code search basics
    $19+$19 /mo +/emp
  • Enterprise
    Per user with Sourcegraph platform; custom quote
    Quote
Watch for
  • · Sourcegraph platform separate from Cody at Enterprise
  • · Per-seat scaling meaningful at Enterprise
  • · Self-hosted Enterprise has setup and infrastructure costs
  • · 2024-2025 tier shift moved some prior-tier features behind Enterprise

Key features

  • +Universal code search across repos and Git hosts
  • +Cody AI assistant (chat, completions, edits) anchored on code search
  • +Code Insights (repo analytics, refactoring tracking)
  • +Batch Changes (large-scale automated refactors)
  • +Self-hosted Enterprise deployment
  • +Integrations with GitHub, GitLab, Bitbucket, Azure DevOps, Gerrit, Perforce
  • +Multiple model options in Cody (Claude, GPT, local)
  • +Sourcegraph CLI and API
  • +SAML SSO and SCIM at Enterprise
60+ integrations
GitHubGitLabBitbucketAzure DevOpsGerritPerforceVS CodeJetBrains IDEs
Geography
Global; strongest in US, EU
#6

AWS CodeCommit

AWS Git hosting in active wind-down; closed to new customers July 2024.

Founded 2015 · Seattle, WA · public · Existing customers only employees
G2 4.1 (280)
Capterra 4.2
From $0 + $0 /mo + /employee
● Transparent pricing
Visit AWS CodeCommit

AWS CodeCommit is the AWS-managed Git hosting service, launched 2015 as part of AWS Developer Tools (alongside CodeBuild, CodeDeploy, CodePipeline). On July 25, 2024, AWS deprecated new-customer onboarding for CodeCommit, a major industry signal that the service is in active wind-down. Existing customers can continue using the service indefinitely (no announced shutdown date), but new buyers are explicitly steered away. The product is included here for completeness and because existing CodeCommit customers face real migration decisions. Best fit going forward: no greenfield buyers. Existing customers should plan migration to GitHub Enterprise, GitLab, or self-hosted Gitea over a 12 to 24 month window.

Best for

Existing CodeCommit customers with active workloads who need a defined migration path. No greenfield use case in 2026.

Worst for

Any new-customer scenario. AWS itself explicitly steers new buyers away. Greenfield AWS-anchored teams should choose GitHub Enterprise (Microsoft) or GitLab with AWS integration.

Strengths

  • Native AWS IAM, KMS, CloudTrail integration for existing customers
  • No per-seat fee for first 5 users; usage-based pricing beyond
  • AWS region-pinned data residency
  • Integrates with CodeBuild, CodeDeploy, CodePipeline (also being deprioritized)
  • Existing customers can continue using indefinitely (no announced shutdown)

Weaknesses

  • AWS deprecated new-customer onboarding July 25, 2024 (closed to new buyers)
  • No active product investment; UI and feature set frozen
  • No AI coding integration (no Copilot, no Q Developer-native repo)
  • No PR review polish or branch protection sophistication of GitHub or GitLab
  • Migration burden for existing customers (12 to 24 month plan recommended)
  • AWS Developer Tools broader (CodeBuild, CodeDeploy, CodePipeline) also being deprioritized

Pricing tiers

public
  • Free Tier (legacy)
    First 5 active users free; 50 GB storage; 10,000 Git requests/mo
    $0+$0 /mo +/emp
  • Per Active User (legacy)
    Per active user beyond 5; storage and request overages
    $1+$1 /mo +/emp
  • New customers
    Closed to new-customer onboarding as of July 25, 2024
    /mo
Watch for
  • · Storage overages beyond 50 GB/month
  • · Git request overages beyond 10,000/month
  • · Migration costs to GitHub Enterprise, GitLab, or self-hosted alternative

Key features

  • +Git hosting in AWS regions
  • +IAM-based access control
  • +KMS encryption at rest
  • +CloudTrail audit logging
  • +Pull requests with approval rules (basic)
  • +CodeBuild, CodeDeploy, CodePipeline integration
  • +Triggers via Lambda or SNS
  • +No AI features (no Copilot, no native Q Developer repo)
30+ integrations
AWS IAMCodeBuildCodeDeployCodePipelineLambdaSNSCloudTrail
Geography
AWS regions (US, EU, AU, AP, CA)
#9

Phorge

Community fork of Phabricator after Phacility wind-down.

Founded 2022 · Distributed (community) · private · 20 to 5,000 employees
G2 4.3 (80)
Capterra 4.4
From $0 + $0 /mo + /employee
● Transparent pricing
Visit Phorge

Phorge is the community-governed open-source fork of Phabricator, started in 2022 after Phacility (the original Phabricator developer) wound down active development. The product preserves Phabricator workflows that some teams (notably Wikimedia, Blender, KDE, and various Linux distributions) depend on: Differential (pre-commit code review distinct from PR-based review), Arcanist CLI, Maniphest task tracking, and Diffusion repository browser. Best fit for teams with active Phabricator deployments who want a community-maintained continuation. Trade-offs: very small community, no AI features, no SaaS option (self-hosted only), and the broader industry has moved decisively to PR-based review workflows (which Phabricator/Phorge does not natively support).

Best for

Organizations with active Phabricator deployments (Wikimedia, Blender, KDE, various Linux distributions) wanting a community-maintained continuation of the Phabricator workflow stack.

Worst for

Greenfield repo decisions (GitHub or GitLab better), teams expecting PR-based review (Phorge uses Differential pre-commit review), or AI-anchored teams (no AI features).

Strengths

  • Community-governed open-source (Apache 2.0)
  • Preserves Phabricator workflows (Differential, Arcanist, Maniphest)
  • Pre-commit code review workflow distinct from PR-based
  • Mature task tracking (Maniphest) and code browser (Diffusion)
  • Active maintenance after Phacility wind-down
  • Right call for organizations with deep Phabricator investment

Weaknesses

  • Very small community relative to GitHub or GitLab
  • No AI features (no Copilot equivalent)
  • Self-hosted only (no SaaS option)
  • Pre-commit review workflow does not match modern PR-based standard
  • Limited integrations with modern DevOps tooling
  • Adoption requires Phabricator familiarity (steep onboarding for new teams)

Pricing tiers

public
  • Self-hosted (open-source)
    Apache 2.0; self-host with no fee
    $0+$0 /mo +/emp
Watch for
  • · Self-hosted infrastructure and ops costs
  • · No managed SaaS option
  • · Onboarding cost for teams new to Phabricator workflow

Key features

  • +Git, Mercurial, Subversion hosting (Diffusion)
  • +Differential pre-commit code review
  • +Arcanist CLI for review workflow
  • +Maniphest task tracking
  • +Phriction wiki
  • +Audit and Owners (post-commit review)
  • +Herald rules engine
  • +OAuth and LDAP authentication
  • +Drydock build resources
20+ integrations
Arcanist CLIJenkinsGitHub (mirror)GitLab (mirror)SlackIRC
Geography
Global; self-hosted anywhere

Frequently asked questions

The questions buyers actually ask before they sign.

Does DSGVO require German companies to self-host their code repositories?
DSGVO does not explicitly require self-hosting, but the German legal interpretation of developer activity data as employee personal data creates significant compliance complexity for cloud-hosted SCM operated by US companies. German data protection authorities have confirmed that commit metadata (author identity, timestamps) is personal data under DSGVO. For cloud-hosted GitHub.com or GitLab.com, you need Standard Contractual Clauses (SCCs), a Transfer Impact Assessment (TIA), and a Data Processing Agreement (DPA). GitHub provides all three; German DPAs have accepted this framework for non-sensitive business data under appropriate supplementary measures. Self-hosting on German infrastructure (Hetzner, T-Systems, on-premises) eliminates the transfer question entirely and is the path chosen by Bosch, BMW, and most KRITIS-adjacent German enterprises. The choice is legal compliance complexity on SaaS vs operational overhead of self-hosting; both paths are viable.
What is opencode.de and how does it relate to GitHub for German government?
Opencode.de is the German Federal Government's open-source code portal, operated by ZenDiS (Zentrum fur Digitale Souveranitat) under the Federal Ministry of the Interior (BMI). It runs GitLab self-managed on Bundescloud (German federal government cloud infrastructure). German federal agencies and state government bodies that publish open-source software are expected to use opencode.de as the primary publication point under the German "Open Source in der Bundesverwaltung" strategy. This is a deliberate digital sovereignty policy: German government code should be hosted on German-controlled, publicly-auditable infrastructure rather than GitHub.com (Microsoft US) or GitLab.com (US-operated SaaS). Individual German federal agency teams may also publish to GitHub.com for visibility, but opencode.de is the sovereign canonical host.
Why is SAP using both GitHub Enterprise and self-hosted GitLab internally?
SAP's split SCM reflects the practical reality of a 100,000+ developer enterprise with diverse engineering culture and legacy infrastructure. SAP Business Technology Platform (BTP) and SAP's cloud-native product lines (built primarily post-2015) adopted GitHub Enterprise as engineering culture at these product lines aligned with modern developer workflows and the GitHub ecosystem. Pre-existing SAP product lines and SAP internal tooling built before GitHub dominance had invested in GitLab Self-Managed or predecessor SCM tools and migration TCO was not justified. SAP has published open-source CI/CD tooling (Project "Piper") supporting both GitHub Actions and Jenkins, reflecting this dual-SCM reality. SAP's choice is not a recommendation; it reflects organizational history. For organizations starting fresh in 2026, picking one platform (GitHub or GitLab) is strongly preferable to a split.
Self-hosted vs cloud Git hosting, which one in 2026?
Cloud (SaaS) is the default in 2026 for most teams: GitHub, GitLab SaaS, Bitbucket Cloud cover the vast majority of organizations and remove operational burden. Self-hosted makes sense when (1) regulated industries (defense, finance, healthcare) require air-gap or on-prem, (2) EU data sovereignty mandates EU-controlled infrastructure (Codeberg or self-hosted GitLab), (3) you have strong FOSS or ethical-tech governance requirements (Codeberg, Forgejo, Gitea), or (4) you have an active Phabricator workflow (Phorge). The trade-off is operational burden: GitLab Self-Managed and GitHub Enterprise Server require non-trivial DevOps investment.
Are AI Copilot features included or extra?
AI features are almost always a separate per-seat add-on, not bundled in repo subscriptions. GitHub Copilot is $19/user/mo (Business) or $39/user/mo (Enterprise), separate from GitHub Enterprise seats. GitLab Duo is $19/user/mo (Pro) or $39/user/mo (Enterprise), separate from Premium or Ultimate. Atlassian Intelligence is partially bundled but lags Copilot and Duo materially. Sourcegraph Cody is per-seat. Codeberg, Forgejo, Gitea, and Phorge do not offer AI features. Budget AI separately when comparing repo platforms; the AI add-on is often a meaningful uplift over the base repo seat.
Which platform is best for EU sovereignty and GDPR?
Codeberg is the strongest fit: Berlin-headquartered non-profit (Codeberg e.V.), native EU data residency, explicit no-training-on-code policy, and Forgejo-based community governance. GitLab Self-Managed deployed in EU regions is the enterprise-grade EU sovereignty option. GitHub Enterprise offers EU data residency tiers but ultimate ownership remains with Microsoft (US-headquartered). Bitbucket Cloud supports EU data residency. For public-sector and regulated EU buyers explicitly mandated to avoid US-headquartered cloud providers, Codeberg, Forgejo self-hosted, and GitLab Self-Managed in EU regions are the credible options.
GitHub vs GitLab vs Bitbucket, when does each win?
GitHub wins for greenfield repo decisions, broadest integration ecosystem, broadest AI integration (Copilot), and most modern teams in 2026. GitLab wins for all-in-one DevSecOps consolidation (one platform across repo, CI/CD, security scanning, registry), Self-Managed on-prem deployment, and buyers wanting one vendor instead of GitHub plus add-ons. Bitbucket wins primarily as an Atlassian-bundled option for organizations where Jira and Confluence are mandatory; outside that scenario, GitHub or GitLab are stronger choices. The 2024 Bitbucket Server EOL and Atlassian price increases have pushed many buyers off Bitbucket.
Does monorepo support actually matter in 2026?
Yes, particularly for large engineering organizations with millions of LOC. GitHub handles monorepos up to roughly 5-10 GB reasonably; beyond that you hit pack-file and clone-time pain. GitLab handles monorepos similarly with partial clone and shallow clone support. Sourcegraph layered on top is the standard solution for monorepo code intelligence (search, navigation, refactor). For very large monorepos (Google, Meta scale), purpose-built systems (Piper, Sapling) are required; the public Git hosting platforms struggle. For most enterprise monorepos under 10 GB with under 100,000 files, GitHub + Sourcegraph or GitLab + Sourcegraph is the working combination.
Large-file support (LFS): how do platforms compare?
Git LFS (Large File Storage) is supported by all major platforms but with very different cost models. GitHub LFS bills storage and bandwidth separately beyond included quotas (often surprises buyers). GitLab LFS is included in repository storage allowances at SaaS tiers, more predictable. Bitbucket LFS is included with subscription. For teams with heavy LFS use (game development, data science, ML model artifacts), GitLab Self-Managed or self-hosted Gitea with object storage backend (S3, MinIO) often delivers better TCO than GitHub LFS at scale. Always price LFS storage and bandwidth explicitly during procurement.
Are open-source repo platforms safe for enterprise use?
Yes, with caveats. GitLab Community Edition (MIT-licensed core) and GitLab Self-Managed are widely deployed at enterprise scale including Fortune 500. Gitea (BSD-licensed) and Forgejo (BSD-licensed) are mature and used at NGO, public-sector, and mid-market scale. Phorge (Apache 2.0) is mature for organizations preserving Phabricator workflows. Open-source repo platforms typically lack SOC 2 Type 2 attestation (self-hosted operator is responsible for compliance), advanced SCIM, and enterprise support. For regulated industries requiring SOC 2 / ISO 27001 attestation at the platform level, GitHub Enterprise Cloud, GitLab Premium/Ultimate SaaS, or Bitbucket Cloud Premium are required.
What is the difference between Gitea, Forgejo, and Codeberg?
Gitea is the original lightweight self-hosted Git server (BSD-licensed) operated by for-profit Gitea Limited since 2022. Forgejo is the community-governed hard fork started October 2022 after the Gitea Limited corporate formation prompted IP-rights and governance concerns. Codeberg is the non-profit (Codeberg e.V. Berlin) managed Git hosting service that runs on Forgejo. Functionally they are very similar (Forgejo is feature-compatible with Gitea), but governance differs significantly: Gitea is for-profit corporate, Forgejo is community-governed, Codeberg is a non-profit hosted service running Forgejo. Buyers prioritizing pure community governance choose Forgejo; buyers wanting a managed non-profit service choose Codeberg.
Is AWS CodeCommit a viable option in 2026?
No for new buyers. AWS deprecated CodeCommit new-customer onboarding on July 25, 2024, an unambiguous signal that the service is in active wind-down. Existing customers can continue indefinitely (no announced shutdown date), but AWS itself steers all new buyers to alternative platforms. Existing CodeCommit customers should plan migration to GitHub Enterprise, GitLab, or self-hosted alternatives over a 12 to 24 month window. AWS-anchored buyers wanting native AWS integration in 2026 should choose GitHub Enterprise (with AWS integrations) or GitLab (with AWS integrations) rather than CodeCommit.
How do I evaluate vendor security incident history?
Check (1) the vendor public status page for outage frequency and duration over the past 24 months, (2) post-incident reports for major outages (transparency signals trust), and (3) any disclosed security incidents or data breaches. GitHub has had multiple multi-hour Actions and PR-related incidents in 2023-2024 with reasonably transparent postmortems. Atlassian Cloud had a multi-day extended incident in April 2022 that affected hundreds of customers; incident response was criticized. GitLab has a strong incident-response track record with public postmortems. Smaller vendors (Codeberg, Forgejo, Gitea) have much smaller incident histories but also fewer commitments and SLAs. Always weight incident-response transparency alongside raw uptime numbers.

Final word

Looking at a different market? See the global Code Repository / Version Control ranking, or pick another country at the top of this page.

Last updated 2026-05-18. Local pricing reverified quarterly. Found something inaccurate? Tell us.