Platforms

Platforms#

A Git hosting platform usually provides: remote repositories, code review, issues / project management, CI/CD, package registries, and integrations. The choice rarely comes down to Git itself; the surrounding tooling is what differs.

Top Providers#

The hosting providers an operator picks among in 2026. Top of the list by market share and ecosystem; bottom by self-hosted reach and specialization.

#

Provider

Hosting

Pricing

Niche

1

GitHub

SaaS + Enterprise

free + paid

The default. Largest ecosystem; Actions; Codespaces; Copilot.

2

GitLab

SaaS + self-hosted

free CE + paid EE

All-in-one DevSecOps. Built-in CI/CD, container registry, package, security scanning.

3

Gitea

Self-hosted

open source (MIT)

Lightweight, single-binary, runs on a Raspberry Pi. The default self-host pick for operators who want a private forge without the GitLab footprint.

4

Forgejo

Self-hosted

open source (MIT / GPL)

Soft fork of Gitea governed by Codeberg e.V. Reference self-hosted option for federated projects.

5

Codeberg

SaaS (non-profit)

free, donation-funded

Hosted Forgejo run by Codeberg e.V. The “ethical” alternative to GitHub for open source.

6

Bitbucket (Atlassian)

SaaS + Data Center

paid

Jira integration. Default for teams already on the Atlassian stack.

7

Azure DevOps Repos

SaaS

paid (with free tier)

Microsoft estates that have not migrated to GitHub Enterprise. Boards, Pipelines, Artifacts in one product.

8

AWS CodeCommit

SaaS (AWS-only)

paid (per-user)

In-account git hosting tied to IAM. Closed to new customers in 2024; existing repos still work.

9

Google Cloud Source Repositories

SaaS (GCP-only)

paid

Mirrors of GitHub / Bitbucket repos inside GCP for Cloud Build pipelines.

10

Gerrit

Self-hosted

open source

Patch-set review model used by the Android, Chromium, OpenStack projects.

11

Gogs

Self-hosted

open source

Original lightweight Go-based forge. Gitea forked from it; Gogs is now the smaller project.

12

SourceHut

SaaS + self-hosted

paid

Mail-list workflow; minimal JavaScript. Drew Devault’s principled forge.

13

Heptapod

SaaS + self-hosted

paid + open source

GitLab fork that adds Mercurial support. The mainstream home for hg projects.

14

Launchpad

SaaS (Canonical)

free

Canonical’s hosting. Original home of Bazaar; now hosts Git, package archives, and Ubuntu development.

15

Phabricator / Phorge

Self-hosted

open source

Long-running review tool from the Facebook era. Phabricator archived 2021; Phorge is the maintained fork.

16

cgit / GitWeb

Self-hosted

open source

Read-only web frontends over a Git server. Lightweight; the kernel.org pattern.

17

SourceForge

SaaS

free + ads

Legacy host of older open-source projects. Still active; mostly downloads and mirrors.

18

Bitbucket Server (legacy)

Self-hosted

paid

Replaced by Bitbucket Data Center. Still in production on many Atlassian estates.

19

Tea / Radicle

P2P

open source

Decentralised, peer-to-peer Git hosting. Niche but the long-term answer to platform consolidation.

20

Tuleap

Self-hosted

open source + commercial

Enlist project-management around the repo; the ALM all-in-one pick.

The deeper notes below cover the providers run into most often.

GitHub#

The dominant platform; default home of open source. Microsoft- owned since 2018; the most extensive ecosystem of any Git host. Most of the third-party tooling assumes a GitHub deployment unless explicitly told otherwise.

  • Pull requests, code review, draft PRs, suggested edits.

  • GitHub Actions, in-platform CI/CD; large marketplace of actions.

  • GitHub Packages, container, npm, maven, NuGet, RubyGems registries.

  • GitHub Codespaces, cloud dev environments.

  • GitHub Copilot, AI assistance.

  • Issues, Projects, Discussions, Wikis.

  • Apps + GitHub API + webhooks for extension.

gh CLI:

$ gh repo create org/name --public
$ gh pr create --fill
$ gh pr view --web
$ gh pr checks
$ gh issue list
$ gh release create v1.0.0 --notes-file CHANGELOG.md

GitLab#

The “DevOps platform” angle: tightly integrated CI/CD, security scanning, and project management. Self-hostable for free in the Community Edition, which is why GitLab dominates internal corporate deployments where GitHub Enterprise is either too expensive or out of policy.

  • Merge requests (MRs), code review.

  • GitLab CI/CD, .gitlab-ci.yml pipelines; widely used in self-hosted setups.

  • Container registry, package registry, environments.

  • Built-in SAST/DAST/secret scanning (paid tiers).

  • Self-hosted Community Edition is fully featured.

glab CLI mirrors most of gh’s operations.

Bitbucket#

Atlassian’s hosting; common in shops already on Jira and Confluence where the bundling discount and ticket integration matter more than the broader marketplace. Smaller third-party ecosystem than GitHub or GitLab, but the Atlassian stack integration is excellent if you’re already there.

  • Pull requests, code review.

  • Bitbucket Pipelines for CI/CD.

  • Strong Jira integration.

  • Smaller marketplace than GitHub or GitLab.

Gitea / Forgejo#

Self-hosted, open-source GitHub-style platforms. Trivial to deploy on a small VM, lightweight enough to run on a Raspberry Pi, and popular for indie infrastructure or privacy-conscious teams that want a familiar UX without sending code to a third party.

  • Gitea, the original; lightweight Go binary.

  • Forgejo, soft-fork of Gitea; non-profit governance.

  • Both: pull requests, issues, CI via Gitea Actions / Forgejo Actions (GitHub-Actions-compatible).

  • Trivial to deploy on a small VM; popular for indie infrastructure and privacy-conscious teams.

Sourcehut#

sr.ht, minimal, mailing-list-driven (git send-email), no-JavaScript UI. Strong appeal in BSD and kernel-style communities where email-based patches are the established norm; idiosyncratic for newcomers used to GitHub-style PR flows.

  • Email-based patches and discussion.

  • Per-project services (lists, builds, todo, hg/git/etc.) priced individually.

  • Strong appeal in BSD / kernel-style communities; idiosyncratic for newcomers.

Cloud-Vendor Repositories#

Most major clouds host Git for in-cloud projects. Useful when deeply integrated with the rest of the cloud’s tooling, but typically not the platform a team chooses for community visibility; contributors expect to find the project on GitHub or GitLab.

Useful when deeply integrated with the rest of the cloud’s tooling; typically not the platform a team chooses for community visibility.

Self-Hosted: Daemons and Bare Repos#

For very small teams or single-developer setups, plain SSH + bare repos still work and are the lowest-overhead Git hosting option there is. Add Gitolite on top for access control and you have multi-user Git on a single VPS.

$ mkdir -p /srv/git/myrepo.git
$ cd /srv/git/myrepo.git
$ git init --bare

$ git clone user@server:/srv/git/myrepo.git

Gitolite adds access control on top.

This is a powerful low-overhead option for simple cases.

Selecting a Platform#

The decision tree as a flat list. Match the row to the constraints that bind on your project. Switch costs are real, so git push --mirror to a second platform is cheap insurance regardless of which primary platform you pick.

  • Open-source project where contributors matter most, GitHub.

  • Enterprise with deep CI/CD needs, GitLab (especially self-hosted).

  • Atlassian shop, Bitbucket.

  • Privacy / sovereignty / cost concerns, Forgejo / Gitea.

  • Minimalist / email-driven, Sourcehut.

  • Already deep in one cloud, the cloud’s repo plus their CI.

Switch costs are real. Mirroring (git push --mirror) is cheap and worth setting up as a safety net regardless of platform.

Cross-Platform Operations#

The bits that work the same regardless of platform, plus the ones that don’t. Git itself is portable; what doesn’t migrate cleanly is the platform-specific metadata, review comments, issue links, CI configuration, automation hooks.

  • Mirroring, push to two platforms; useful for bus-factor / DR.

  • Importing, every platform has migration tooling; issue and PR migration is the bumpier part.

  • Code review portability, comments don’t migrate cleanly. Plan a cutover, don’t dual-run.

Beyond Git Hosting#

Adjacent tools that often live on the platform but don’t have to. Each one is a separate buying decision: most platforms ship “good enough” defaults, with mature third-party alternatives available when the defaults run out of room.

  • Issue tracking, platform issues, or Jira / Linear / Shortcut.

  • CI/CD, platform pipelines, or CircleCI / Buildkite / Jenkins.

  • Code review extensions, Reviewable, Gerrit-style flows.

  • AI assistance, Copilot, GitLab Duo, Cody, Codeium.

  • Code search, Sourcegraph, GitHub code search.

  • Code intelligence, LSIF / SCIP indexing for cross-repo navigation.

Contents