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

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

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
   For most agencies: GitHub Team
2. GitHub Team mentioned
   For most agencies: GitHub Team
3. Bitbucket mentioned
   Bitbucket - if you bill against Jira
4. Jira mentioned
   Bitbucket - if you bill against Jira
5. Confluence mentioned
   The real argument is the Atlassian tie-in: if you're already tracking client work in Jira and writing docs in Confluence, commits linking to tickets automatically is worth more than Bitbucket's weaker code review UI costs you.
6. GitLab Premium mentioned
   GitLab Premium - if clients ask compliance questions
7. third-party mentioned
   It's also the only one of the three where self-hosting the same product is a supported path, which helps when a client's contract forbids third-party code storage.
8. Azure mentioned
   Azure DevOps - for .NET shops and tiny teams
9. Azure DevOps mentioned
   Azure DevOps - for .NET shops and tiny teams
10. Gitea mentioned
    Gitea or Forgejo - self-hosted, narrow use case
11. Forgejo mentioned
    Gitea or Forgejo - self-hosted, narrow use case

Sources the engine cited

The answer, as recorded

## For most agencies: **GitHub Team** Start here unless you have a specific reason not to. ~$4/user/month, and the deciding factor for agency work isn't features - it's that your contractors and your clients' in-house devs already have accounts and know the review flow. Zero onboarding friction on every new engagement. Repo transfer is a first-class operation, so handoff at project end is a few clicks and the client inherits history, issues, and PRs intact. Watch one thing: **outside collaborators consume a paid seat**, counted once per person no matter how many repos they touch - so a client stakeholder who wants read access costs you money. ([GitHub per-user pricing](https://docs.github.com/en/billing/managing-the-plan-for-your-github-account/about-per-user-pricing), [transferring a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository)) ## **Bitbucket** - if you bill against Jira ~$3.65/user/month Standard, $7.25 Premium - the cheapest of the big three. The real argument is the Atlassian tie-in: if you're already tracking client work in Jira and writing docs in Confluence, commits linking to tickets automatically is worth more than Bitbucket's weaker code review UI costs you. Also the best fit if a client mandates Jira and you'd otherwise be paying two vendors. ([pricing comparison](https://www.getpricepulse.com/blog/github-vs-gitlab-vs-bitbucket-pricing-2026.html), [Bitbucket vs GitHub](https://tech-insider.org/bitbucket-vs-github-2026/)) ## **GitLab Premium** - if clients ask compliance questions ~$29/user/month, which looks brutal next to the others, but it bundles security scanning, dependency checks, and compliance/governance tooling you'd otherwise buy separately. That matters specifically when you serve regulated clients (health, fintech, public sector) and need to show SAST results and audit trails in a deliverable. It's also the only one of the three where self-hosting the same product is a supported path, which helps when a client's contract forbids third-party code storage. Skip it otherwise - you're paying 7x for features you won't invoice for. ([GitLab vs Bitbucket](https://aiproductivity.ai/blog/gitlab-vs-bitbucket/), [platform comparison](https://guptadeepak.com/tools/top-5-git-hosting-platforms-2026/)) ## **Azure DevOps** - for .NET shops and tiny teams Free for 5 users with unlimited private repos, 1,800 CI minutes, plus unlimited self-hosted build minutes; $6/user/month after that. Genuinely the best free tier for a small agency, and the obvious pick if your clients are Microsoft-stack enterprises where procurement already approved Azure. The repo experience is the weakest of the four, though. ([Azure DevOps pricing](https://azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services/)) ## **Gitea** or **Forgejo** - self-hosted, narrow use case Single binary, cheap to run, no per-seat cost - attractive when you have many client repos and lots of read-only stakeholders, since seat pricing is what kills agency margins. But you become the one responsible for backups, uptime, and the 2am restore when a client needs their code. Worth it only if you have someone who actually wants to own that, or a client contract that requires code stay on your infrastructure. ([self-hosted options](https://rhodecode.com/blog/170/best-self-hosted-source-code-management-platforms-in-2026)) --- **My recommendation:** GitHub Team, one org for your agency, one repo per client project, transfer the repo out at handoff. Give client stakeholders read access only where they'll genuinely use it, since each one is a seat. Revisit only if a client's compliance requirements force your hand. One caveat on the numbers: published per-seat pricing on these moved around in 2026 and secondary sources disagree (I saw GitHub's paid tier quoted as both $4 and $21 - the latter is Enterprise Cloud, not Team). Confirm current rates on the vendor pricing pages before you build a budget on them.

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.