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

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

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, one org per client) - the default, and what I'd pick absent a reason not to.
2. Jira mentioned
   Bitbucket - if your agency runs on Jira/Confluence, or seats are the binding constraint.
3. Confluence mentioned
   Bitbucket - if your agency runs on Jira/Confluence, or seats are the binding constraint.
4. GitLab mentioned
   GitLab - if you're selling compliance, or you need one tool instead of five.
5. GitHub Team mentioned
   Premium is $29/user/month, which is ~7x GitHub Team, but it bundles CI minutes (10k/mo), security/dependency scanning, and planning with no add-ons.
6. Self-hosted Forgejo mentioned
   Self-hosted Forgejo (or Gitea) - if you have many low-value repos and no appetite for per-seat creep.
7. Forgejo mentioned
   Self-hosted Forgejo (or Gitea) - if you have many low-value repos and no appetite for per-seat creep.
8. Gitea mentioned
   Self-hosted Forgejo (or Gitea) - if you have many low-value repos and no appetite for per-seat creep.
9. per-seat mentioned
   Self-hosted Forgejo (or Gitea) - if you have many low-value repos and no appetite for per-seat creep.
10. Codeberg mentioned
    Forgejo is governed by the Codeberg non-profit and GPL-licensed;

Sources the engine cited

The answer, as recorded

## My picks, in order **1. GitHub (Team, one org per client) - the default, and what I'd pick absent a reason not to.** $4/user/month on Team, and crucially it's built for exactly the agency pattern: GitHub lets partners create and pay for an org *on behalf of a client*, then transfer ownership to the client at handoff and stay on as **billing manager** so you can still manage the subscription. That's the cleanest exit story in the business - the client ends up owning their code, and you don't have to migrate anything. Outside collaborators are billed once per person across the whole org (not per repo), so bringing in a freelance subcontractor on three client repos costs one seat. Also the best place to be for hiring and for client developers who already know the tools. **2. Bitbucket - if your agency runs on Jira/Confluence, or seats are the binding constraint.** Cheapest of the three at $3.65/user/month, and the Jira/Confluence integration is native rather than bolted on. If your PM layer is already Atlassian and clients live in Jira, the ticket↔branch↔deploy traceability you get for free is worth real money on fixed-bid work. Weaker ecosystem and CI story than GitHub; I'd only choose it for the Atlassian reason. **3. GitLab - if you're selling compliance, or you need one tool instead of five.** Premium is $29/user/month, which is ~7x GitHub Team, but it bundles CI minutes (10k/mo), security/dependency scanning, and planning with no add-ons. For agencies doing regulated-industry work (health, fintech, public sector) where the client asks for SAST/dependency-scan evidence, this is the one that answers the questionnaire out of the box. Overkill and overpriced for a general web/product shop. **4. Self-hosted Forgejo (or Gitea) - if you have many low-value repos and no appetite for per-seat creep.** Forgejo is the community default for new self-hosted installs in 2026; it idles around 170-512MB RAM, so a $5-15/month VPS holds your entire code estate with **no per-seat fee** and full data ownership. Forgejo is governed by the Codeberg non-profit and GPL-licensed; Gitea is MIT with a commercial edition and a for-profit parent - pick Forgejo unless you specifically want Gitea's commercial support. The catch for agencies is real: you own uptime, backups, and the handoff, and "we'll host your repo on our box" is a harder sell to an enterprise client than "it's in your own GitHub org." I'd use this for internal tooling and archived engagements, not for active client work. ## The thing that actually matters more than the platform For agency work, structure beats product choice: **one org/workspace per client, billed to the client where possible, with you as an invited member.** It makes offboarding a two-click transfer instead of a migration project, keeps one client's breach from touching another's code, and means a non-renewal doesn't leave you hosting someone else's IP. GitHub supports this pattern most explicitly, which is the main reason it's my #1. One caveat on research: several "best Git hosting 2026" listicles rank a product called "GitForge" at #1. I couldn't verify it as a real, established platform - it reads like SEO filler. Don't buy on the strength of those rankings. Sources: - [GitHub Docs - Creating and paying for an organization on behalf of a client](https://docs.github.com/en/billing/how-tos/manage-for-client/create-client-org) - [GitHub Docs - About outside collaborators](https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization) - [Top 5 Git hosting platforms 2026 (pricing comparison)](https://guptadeepak.com/tools/top-5-git-hosting-platforms-2026/) - [GitHub vs GitLab vs Bitbucket 2026](https://tech-insider.org/sv/github-vs-gitlab-vs-bitbucket-2026/) - [Gitea vs Forgejo 2026: picking a self-hosted Git server](https://valebyte.com/en/blog/gitea-vs-forgejo-2026-picking-a-self-hosted-git-server/) - [5 Forgejo alternatives / self-hosting resource notes](https://sliplane.io/blog/5-awesome-forgejo-alternatives) - [The Best Git Hosting Services in 2026](https://www.itechguides.com/best/git-hosting-services/)

Near this answer

The same question, recorded on other dates: 2026-10-19, 2026-10-17, 2026-10-14, 2026-10-12, 2026-10-11, 2026-10-09, 2026-10-07, 2026-10-04, 2026-10-02, 2026-09-30, 2026-09-28.

code repository hosting, asked for other audiences: startups (asked 2026-10-20).

Other categories with a recorded answer: api management platforms, application performance monitoring, ci cd platforms, content management systems.

Markdown edition · JSON record · 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.