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

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

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
   GitHub (Team, ~$4/user/mo) - default pick for most agencies.
2. GitLab mentioned
   GitLab (Premium, ~$29/user/mo) - if CI and compliance are the point.
3. GitHub Actions mentioned
   GitHub Actions minutes on heavy pipelines can quietly erase the seat-price gap.
4. Atlassian Statuspage mentioned
   Bitbucket (Standard ~$3.65, Premium ~$7.25/user/mo) - only if you're already an Atlassian shop.
5. Jira mentioned
   The Jira/Confluence integration is genuinely tighter than anyone else's, and Premium is a single line item that includes advanced security and higher Pipelines minutes with no à la carte add-ons.
6. Confluence mentioned
   The Jira/Confluence integration is genuinely tighter than anyone else's, and Premium is a single line item that includes advanced security and higher Pipelines minutes with no à la carte add-ons.
7. Azure DevOps mentioned
   Azure DevOps - if your clients are Microsoft/Entra ID shops.
8. Forgejo mentioned
   Forgejo (self-hosted, free) - for clients who contractually can't use US SaaS.
9. SaaS mentioned
   Forgejo (self-hosted, free) - for clients who contractually can't use US SaaS.
10. Codeberg mentioned
    Community-governed under Codeberg e.V.
11. Gitea / Forgejo mentioned
    Prefer it over Gitea for new instances;
12. GitHub Team mentioned
    Standardize on GitHub Team, one org per client rather than one org with everything in it.

Sources the engine cited

The answer, as recorded

## The short version **GitHub (Team, ~$4/user/mo) - default pick for most agencies.** Cheapest realistic seat price of the big three, and the real agency advantage is client handoff: repo transfer between orgs is a first-class, one-click operation that preserves issues, PRs, stars, and sets up redirects, so when an engagement ends you hand the client a repo instead of a tarball. Also the platform your contractors and new hires already know, which cuts onboarding to zero. ([GitHub Docs - transferring a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository), [pricing comparison](https://www.getpricepulse.com/blog/github-vs-gitlab-vs-bitbucket-pricing-2026.html)) The gotcha to plan around: on a paid org, every **outside collaborator** on a private repo burns a paid seat. If you routinely give client stakeholders read access, budget for it or park those repos in the client's own free org and add yourselves as collaborators. ([GitHub community discussion #161271](https://github.com/orgs/community/discussions/161271), [managing outside collaborators](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators)) **GitLab (Premium, ~$29/user/mo) - if CI and compliance are the point.** Much higher sticker price, but CI is included in every paid tier with generous compute minutes, plus security scanning and project management bundled. GitHub Actions minutes on heavy pipelines can quietly erase the seat-price gap. Worth it if you're doing DevSecOps work or need per-project compliance evidence for regulated clients; overkill if you're shipping marketing sites. ([GitLab vs Bitbucket 2026](https://aiproductivity.ai/blog/gitlab-vs-bitbucket/)) **Bitbucket (Standard ~$3.65, Premium ~$7.25/user/mo) - only if you're already an Atlassian shop.** The Jira/Confluence integration is genuinely tighter than anyone else's, and Premium is a single line item that includes advanced security and higher Pipelines minutes with no à la carte add-ons. Outside that, the developer-mindshare gap versus GitHub is real and growing. ([CompareTiers](https://comparetiers.com/compare/bitbucket-vs-github)) **Azure DevOps - if your clients are Microsoft/Entra ID shops.** The most practical option when you need real portfolio and sprint planning next to repos and the client's identity already lives in Entra. ([Top 5 Git hosting platforms](https://guptadeepak.com/tools/top-5-git-hosting-platforms-2026/)) **Forgejo (self-hosted, free) - for clients who contractually can't use US SaaS.** Single Go binary, runs in ~512 MB, includes PRs, issues, package/container registry, LFS, and GitHub-Actions-compatible CI. Community-governed under Codeberg e.V. (a German non-profit), which is the specific thing that satisfies EU data-residency and sovereignty clauses. Prefer it over Gitea for new instances; GitLab CE self-managed wants ~16 GB RAM and 8 vCPUs to boot comfortably, so only take that on if you need the full suite. ([TechVerdict self-hosted Git 2026](https://www.techverdict.io/articles/self-hosted-git-2026), [Selfhostr comparison](https://selfhostr.com/comparatifs/gitea-vs-forgejo-vs-gitlab-2026/)) ## What I'd actually do Standardize on **GitHub Team**, one org per client rather than one org with everything in it. That keeps blast radius small, makes access reviews trivial, and means handoff is "transfer the repos, remove ourselves" instead of a migration project. Keep a separate internal org for your own tooling and templates. Add Forgejo only as the escape hatch for the one or two clients whose contracts demand it. Two caveats on the numbers above: the per-seat prices come from comparison blogs rather than vendor pricing pages, so confirm current figures with GitHub/GitLab/Atlassian directly before you commit a budget. And I'd weight CI minutes at least as heavily as seat price in that math - for most agencies it's the larger and less predictable line item. Sources: - [GitHub Docs - Transferring a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository) - [GitHub Docs - Managing outside collaborators](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators) - [GitHub community - per-seat charges for outside collaborators](https://github.com/orgs/community/discussions/161271) - [GitHub vs GitLab vs Bitbucket Pricing 2026](https://www.getpricepulse.com/blog/github-vs-gitlab-vs-bitbucket-pricing-2026.html) - [Bitbucket vs GitHub Pricing 2026 - CompareTiers](https://comparetiers.com/compare/bitbucket-vs-github) - [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/) - [Self-Hosted Git in 2026: Forgejo vs Gitea vs GitLab CE](https://www.techverdict.io/articles/self-hosted-git-2026) - [Gitea vs Forgejo vs GitLab 2026 - Selfhostr](https://selfhostr.com/comparatifs/gitea-vs-forgejo-vs-gitlab-2026/)

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.