Git hosting platforms
Git hosting platforms store your code, track changes, and add pull requests, issue tracking, and automated builds on top. This grid compares the cloud versions of six common choices, from the big all-in-one platforms (GitHub, GitLab, Azure DevOps, Bitbucket) to non-profit and open-source alternatives (Codeberg, SourceHut). The real trade-offs are price per user, how much free CI/CD you get, whether the software is open source, and how much of the surrounding toolset you want bundled.
Last updated
How to choose
Start with who will use it. A solo developer or a small team of up to five can run on the free tiers of GitHub, GitLab, Bitbucket, or Azure DevOps. Past five people, GitLab, Bitbucket, and Azure DevOps start charging per user, while GitHub's free plan stays free for collaborators.
Questions to ask
- Do you need private repositories? Codeberg is aimed at free and open-source projects and does not offer private hosting beyond a tiny allowance.
- How much CI/CD will you run? Free build minutes range from 50 per month on Bitbucket to about 2,000 on GitHub. You can always bring your own runners on most platforms.
- Do you need to self-host later? GitHub, GitLab, Bitbucket, and Azure DevOps all sell a self-managed edition; Codeberg and SourceHut run open-source software you can host yourself.
- Does open source matter to you? Only Codeberg and SourceHut are fully open source; GitLab is open core.
- Which other tools do you already use? Bitbucket pairs with Jira, Azure DevOps with Microsoft tooling, GitHub with the widest set of third-party integrations.
Check the full cost, not just the entry price: security scanning, AI features, and extra CI minutes are often paid add-ons. Prices change often, so confirm on the maker's page before you buy.
Answer
Browse the table. Filter to what matters.
Use the filters below, then sign in if you want to shortlist and decide with friends.
Sign in to vote, hide services and features, and reorder.
Verified: hover a cell and click its green dot for the source Estimate: no cited source Not stated: the company doesn't publish it
| Feature | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ | ⠿ |
|---|---|---|---|---|---|---|
|
⠿
Entry paid price
|
Doesn't apply
|
Doesn't apply
|
||||
|
⠿
Free plan user limit
|
Unlimited users (free and open-source projects)
|
Doesn't apply
|
||||
|
⠿
Private repositories
|
|
|||||
|
⠿
Free CI CD minutes
|
0 min
|
|||||
|
⠿
Package registry
|
|
|
||||
|
⠿
Static site hosting
|
|
|
||||
|
⠿
Self hosted edition
|
||||||
|
⠿
Source code license
|
Proprietary
|
Proprietary
|
Proprietary
|
|||
|
⠿
Built in AI features
|
||||||
|
⠿
Security scanning
|
Why these features matter
-
Entry paid price ($/user/month)
Per-user pricing adds up as a team grows; a cheap seat matters more for large teams than small ones.
-
Free plan user limit
A user cap on the free plan decides when a small team must start paying.
-
Private repositories
Closed-source and client work needs private repositories; open-source-only hosts are not an option then.
-
Free CI CD minutes (min)
Free build minutes cover small projects; busy pipelines run out quickly and then cost extra.
-
Package registry
A built-in registry keeps builds and packages in one place instead of needing a separate service.
-
Static site hosting
Handy for project sites and docs without extra hosting.
-
Self hosted edition
Teams with strict data rules or who want to avoid lock-in need a self-managed path.
-
Source code license
Open-source platforms can be audited and self-hosted freely; proprietary ones tie you to the vendor.
-
Built in AI features
Some teams want AI assistance built in; others actively avoid it.
-
Security scanning
Catching leaked secrets and vulnerable code early is cheaper than fixing them later, but is often paid.
About the services
-
GitHub · GitHub
The largest code host, with the biggest open-source community and the widest integrations. The free plan has unlimited repositories; the paid Team plan adds protected branches and more CI minutes. Copilot and security scanning are extra on most plans.
-
GitLab · GitLab
An all-in-one DevSecOps platform with built-in CI/CD, planning, and security scanning. Free is limited to 5 users per private group; Premium costs more per user than most rivals but bundles more. Can be self-managed.
-
Bitbucket · Atlassian
Atlassian's Git host, best for teams already on Jira. Cheapest paid per-user price here, but the free plan includes only 50 build minutes a month and 5 users.
-
Azure DevOps Services · Microsoft
Microsoft's hosted suite of Azure Repos (Git), Pipelines, Boards, and Artifacts. First 5 users are free; good fit for teams on Azure and Visual Studio, which includes free access.
-
Codeberg · Codeberg e.V.
A non-profit, donation-funded host running the open-source Forgejo software, in Germany. Free for free and open-source projects; no paid plans and essentially no private hosting.
-
SourceHut · SourceHut
A minimalist, fully open-source forge with Git and Mercurial hosting, mailing-list workflows, and CI, built to work without JavaScript. Flat pay-what-you-can pricing per account, with no AI features.
Suggest a change
Related comparisons
-
Bug tracking softwareBug trackers log, prioritize, and track defects through to a fix. Some are standalone issue trackers, while others come bundled with code hosting or a wider project suite. This grid compares seven, covering what they cost, how many people use them free, and whether they host code or run on your own servers.
-
Translation management softwareTranslation management systems (TMS) keep a team's UI strings, documents and translations in one place, with translation memory, glossaries, machine and human translation, and integrations with code and design tools. The decision is how you are charged (words, strings or keys), what a free plan covers, and how much automation and security you need.
-
Feature flag toolsFeature flag tools let engineers switch features on or off, roll them out to a slice of users, and roll them back without redeploying. This grid compares ten hosted and self-hosted tools, from open source servers to full experimentation platforms. The real trade-offs are how each one bills (per seat, per request, per user), whether you can run it yourself, and whether approvals, SSO, and A/B testing sit behind an enterprise plan.
-
Incident management softwareIncident management software wakes the right person when something breaks, gives the team one place to run the response, and records what happened so it doesn't happen again. This grid compares eight tools on what most buyers decide on: what the first paid plan really costs, whether on-call paging is included or sold separately, how well incidents run inside Slack or Teams, and how far AI goes.
-
Status page softwareStatus page software gives your customers one trusted place to see whether your service is up, read incident updates, and subscribe to alerts. Some tools are stand-alone status pages, while others bundle uptime monitoring, on-call paging, or full incident response. The trade-offs are price model (flat plan, per user, or per component), how many subscribers and team members each plan allows, and whether monitoring and paging come with it.
-
API management platformsAPI management platforms sit in front of your APIs to handle authentication, rate limits, analytics, a developer portal, and increasingly AI and MCP traffic. This grid compares seven well-known options on what you can see before talking to sales: entry price, free access, how pricing works, where it can run, and which capabilities come built in.