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

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

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 - my default pick for most agencies
2. GitHub Advanced Security mentioned
   Also note GitHub Advanced Security is a separate $49/user/month line item - don't promise clients security scanning assuming it's included.
3. Bitbucket mentioned
   Bitbucket - if your clients live in Jira
4. Jira mentioned
   Bitbucket - if your clients live in Jira
5. Confluence mentioned
   Cheapest of the three, and the Jira/Confluence integration is the real reason to pick it: branch-to-ticket linking works without glue code.
6. third-party mentioned
   Outside that, the ecosystem and third-party tooling are thinner than GitHub's.
7. GitLab mentioned
   GitLab - if you're selling DevOps, not just code
8. GitHub Team mentioned
   Premium is $29/user/month, Ultimate $99 (pricing (https://toolradar.com/tools/gitlab/pricing)) - roughly 7x GitHub Team.
9. US mentioned
   The self-managed option also matters when a client's contract says their source can't sit on US infrastructure.
10. Self-hosted mentioned
    Self-hosted: Forgejo (or Gitea)
11. Gitea mentioned
    Self-hosted: Forgejo (or Gitea)
12. Codeberg recommended
    Forgejo has become the more common recommendation in self-hosting communities, with non-profit governance under Codeberg e.V.

Sources the engine cited

The answer, as recorded

## GitHub - my default pick for most agencies Team is $4/user/month, Enterprise $21 ([pricing](https://toolradar.com/tools/github/pricing)). It wins on the thing agencies actually need most: every contractor, freelancer and client-side dev you'll ever onboard already knows it, so onboarding cost is zero. Actions covers CI for most client work, and repo transfers preserve history and issues, which is the handoff path you'll use over and over ([docs](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository)). The one agency-specific trap: outside collaborators on private repos consume a paid seat exactly like members ([docs](https://docs.github.com/en/billing/reference/github-license-users)). If you give 30 client stakeholders read access across 30 projects, you're paying for all of them. Budget for it or keep clients out of the repo and give them a staging URL instead. Also note GitHub Advanced Security is a separate $49/user/month line item - don't promise clients security scanning assuming it's included. ## Bitbucket - if your clients live in Jira Standard is $3.65/user/month, Premium $7.25 ([pricing](https://www.eesel.ai/blog/bitbucket-pricing)). Cheapest of the three, and the Jira/Confluence integration is the real reason to pick it: branch-to-ticket linking works without glue code. If you're an agency whose clients hand you a Jira board, this removes friction you'd otherwise eat every sprint. Outside that, the ecosystem and third-party tooling are thinner than GitHub's. ## GitLab - if you're selling DevOps, not just code Premium is $29/user/month, Ultimate $99 ([pricing](https://toolradar.com/tools/gitlab/pricing)) - roughly 7x GitHub Team. That's only defensible if you're consolidating: CI/CD, container registry, security scanning and project management in one bundle replaces several subscriptions. The self-managed option also matters when a client's contract says their source can't sit on US infrastructure. ## Self-hosted: Forgejo (or Gitea) Worth it in one specific case - a client with a contractual or regulatory requirement that code stays on their infrastructure. Both are lightweight enough to run on a small VPS. Forgejo has become the more common recommendation in self-hosting communities, with non-profit governance under Codeberg e.V. and faster community contribution throughput since 2024; Gitea is the commercially-backed original with the broader plugin ecosystem ([comparison](https://contabo.com/blog/gitea-vs-forgejo/), [2026 overview](https://www.techverdict.io/articles/self-hosted-git-2026)). Price the ongoing maintenance into the retainer - you're now the client's sysadmin. ## The structural decision that matters more than the vendor For an agency, pick one of two models up front: **One org per client, client pays.** You become a billing manager on an org they own ([docs](https://help.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client)). Clean handoff, no seat costs on you, no risk of cross-client access leaking. Best for retainers and larger clients. **One agency org, repos transferred at delivery.** Simpler day-to-day, but you carry the seat cost and the access-hygiene burden, and every offboarded contractor is a manual audit. Most agencies I'd advise start with the second and regret it around client fifteen. If your client count is heading past ten, go org-per-client now. **Sources:** - [GitHub pricing](https://toolradar.com/tools/github/pricing) - [GitLab pricing](https://toolradar.com/tools/gitlab/pricing) - [Bitbucket pricing](https://www.eesel.ai/blog/bitbucket-pricing) - [GitHub license/seat consumption](https://docs.github.com/en/billing/reference/github-license-users) - [Transferring a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository) - [Paying for an org on behalf of a client](https://help.github.com/en/github/setting-up-and-managing-billing-and-payments-on-github/creating-and-paying-for-an-organization-on-behalf-of-a-client) - [Gitea vs Forgejo](https://contabo.com/blog/gitea-vs-forgejo/) - [Self-hosted Git 2026](https://www.techverdict.io/articles/self-hosted-git-2026)

Near this answer

The same question, recorded on other dates: 2026-09-28, 2026-09-25, 2026-09-23, 2026-09-21, 2026-09-17, 2026-09-15, 2026-09-13, 2026-09-11, 2026-09-09, 2026-09-06.

code repository hosting, asked for other audiences: startups (asked 2026-09-30).

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.