What Claude (Anthropic) with web search answered for code repository hosting (agencies) on 2026-09-21

Claude (Anthropic) with web search claude-opus-5 asked 2026-09-21

Coverage: Claude (Anthropic) with web search. Other engines not included.

The question asked, verbatim: best code repository hosting for agencies

Brands named, in the order the engine gave

1. GitHub mentioned
   Short answer: GitHub, unless you have a specific reason not to.
2. GitLab mentioned
   GitLab - if compliance or "one tool for everything" is the sell.
3. Bitbucket compared
   (GitLab vs Bitbucket 2026 (https://aiproductivity.ai/blog/gitlab-vs-bitbucket/))
4. Jira mentioned
   Bitbucket - if your agency already runs on Jira.
5. Azure DevOps mentioned
   Azure DevOps - only if your clients are Microsoft/.NET shops.
6. Forgejo mentioned
   Gitea or Forgejo, self-hosted - if a client contractually forbids third-party hosting.
7. third-party mentioned
   Gitea or Forgejo, self-hosted - if a client contractually forbids third-party hosting.
8. Ideally mentioned
   - Ideally, the client owns the org and grants you access - then their seats are on their invoice, and the code was never yours to lose.

Sources the engine cited

The answer, as recorded

## Short answer: GitHub, unless you have a specific reason not to. For agencies the hosting platform matters less than the *account structure* - so I'll cover both. **1. GitHub - the default, and what I'd pick for ~90% of agencies.** Team is $4/user/month, and critically, **outside collaborators consume one paid seat total, even across many repos** - so a contractor touching 8 client repos costs you $4, not $32. That's the single biggest cost lever for agency work. You also get the deepest talent pool (every dev you hire already knows it), the best CI ecosystem via Actions, and the easiest client handoff: transfer the repo to the client's org and you're done. Downside: real SSO/SAML and audit logs require Enterprise Cloud, which is a large jump. ([GitHub pricing](https://github.com/pricing), [outside collaborator seat rules](https://docs.github.com/en/billing/managing-the-plan-for-your-github-account/about-per-user-pricing)) **2. GitLab - if compliance or "one tool for everything" is the sell.** Built-in security scanning, project management, and CI in one product, plus a genuine self-managed option if a client demands code stays on their infrastructure. But Premium is ~$29/user/month, which is brutal at agency headcount. Only worth it if you're actually using the DevSecOps features and billing clients for them - otherwise you're paying for shelfware. ([GitLab vs Bitbucket 2026](https://aiproductivity.ai/blog/gitlab-vs-bitbucket/)) **3. Bitbucket - if your agency already runs on Jira.** Cheapest of the three (~$3.30/user/month Standard, free up to 5 users) and the Jira issue↔branch↔PR linking is genuinely tight, which matters if you bill hours against tickets. The ecosystem is thinner and the hiring story is worse - devs grumble about it. Don't adopt it *for* the code hosting; adopt it because you're already in Atlassian. ([Bitbucket pricing](https://www.atlassian.com/software/bitbucket/pricing)) **4. Azure DevOps - only if your clients are Microsoft/.NET shops.** Cheap for small teams and fits enterprise procurement, but Microsoft is clearly investing in GitHub instead. I wouldn't start here in 2026. **5. Gitea or Forgejo, self-hosted - if a client contractually forbids third-party hosting.** Gitea is a single Go binary, runs on a $10 VPS, and gives you GitHub-shaped features with no per-seat cost - attractive when you have 40 client repos and rotating contractors. The catch is you now own backups, uptime, and patching, which is unbilled work. Treat it as a deliberate cost trade, not a default. ([Self-hosted SCM comparison](https://rhodecode.com/blog/170/best-self-hosted-source-code-management-platforms-in-2026)) ## The structural advice that matters more than the vendor - **One GitHub org per client, not one org with all clients' repos.** It keeps billing, access, and IP boundaries clean, and handoff becomes "transfer ownership" instead of "untangle six years of permissions." The cost is more orgs to administer. - **Ideally, the client owns the org and grants you access** - then their seats are on their invoice, and the code was never yours to lose. Many agencies resist this; it's usually the right call anyway. - **Put repo ownership and handoff in the contract.** Most repo disputes I've seen are contract failures, not tooling failures. - **Back up independently of your host.** Git being distributed doesn't cover issues, PRs, or CI config. Something like GitProtect or a scripted export is cheap insurance. If you tell me your headcount, roughly how many concurrent clients, and whether clients want to own their repos, I'd narrow this to one recommendation. **Sources:** - [GitHub Pricing](https://github.com/pricing) - [GitHub Docs - People who consume a license in an organization](https://docs.github.com/en/billing/managing-the-plan-for-your-github-account/about-per-user-pricing) - [Bitbucket Pricing - Atlassian](https://www.atlassian.com/software/bitbucket/pricing) - [GitLab vs Bitbucket 2026: CI/CD, Pricing & Verdict](https://aiproductivity.ai/blog/gitlab-vs-bitbucket/) - [Top 5 Git Hosting Platforms of 2026](https://guptadeepak.com/tools/top-5-git-hosting-platforms-2026/) - [Best Self-Hosted Source Code Management Platforms in 2026 - RhodeCode](https://rhodecode.com/blog/170/best-self-hosted-source-code-management-platforms-in-2026) - [Top Git Hosting Services - GitProtect.io](https://gitprotect.io/blog/top-git-hosting-services/)

Markdown edition · the question page, with every recording · Answer Watch · AEO Watch

Answer Watch records what one AI answer engine said on one date, nothing more. Each page names the engine and the model, carries the date the question was asked, and lists the brands that appeared in the answer in the order the engine gave them, with the sources it cited. It is a measurement, not a ranking, not a recommendation and not a claim about the world. Brands that did not appear in an answer are not named on any public page. Coverage: Claude (Anthropic) with web search. Other engines not included.