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

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

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 recommended
   GitHub (Team, ~$4/user/mo) - My default recommendation.
2. Bitbucket mentioned
   Bitbucket (~$3.30-3.65/user/mo Standard, $16.50 flat for ≤5 users) - The value pick, and the obvious answer if you already run Jira for client work.
3. Jira mentioned
   Bitbucket (~$3.30-3.65/user/mo Standard, $16.50 flat for ≤5 users) - The value pick, and the obvious answer if you already run Jira for client work.
4. GitLab mentioned
   GitLab (Free tier, or Premium at ~$29/user/mo) - I'd use the Free tier here, not Premium.
5. Forgejo mentioned
   Forgejo or Gitea, self-hosted - Worth a serious look if seat costs are eating you alive.
6. Gitea mentioned
   Forgejo or Gitea, self-hosted - Worth a serious look if seat costs are eating you alive.
7. Codeberg mentioned
   Forgejo is community-owned under Codeberg e.V.
8. Azure DevOps mentioned
   Azure DevOps - Only if your clients are Microsoft/.NET shops with Entra ID and that's the gravity you live in.
9. Microsoft mentioned
   Azure DevOps - Only if your clients are Microsoft/.NET shops with Entra ID and that's the gravity you live in.
10. Entra ID mentioned
    Azure DevOps - Only if your clients are Microsoft/.NET shops with Entra ID and that's the gravity you live in.
11. GitHub Team mentioned
    What I'd actually do: GitHub Team as the home for all client code, one repo per client, and a hard rule that clients get access only at handoff or via a transferred repo rather than as standing seats.

Sources the engine cited

The answer, as recorded

For an agency, the deciding factors aren't really "which Git," they're: how cheap are seats when you're juggling dozens of client repos, how cleanly you can scope a client to *one* repo, and how painless the handoff is when a project ends. Here's how I'd rank them. **1. GitHub (Team, ~$4/user/mo)** - My default recommendation. One org, one repo per client, teams per project, and handoff is trivial: transfer the repo to the client's org and the history, issues, and PRs go with it. Actions is the CI everyone already knows how to write, and the ecosystem means any contractor you hire is productive on day one. The one trap: adding a client as an **outside collaborator on a private repo consumes a paid seat**, so budget for client reviewers, not just your own devs. ([pricing](https://guptadeepak.com/tools/top-5-git-hosting-platforms-2026/), [outside collaborator billing](https://docs.github.com/en/[email protected]/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization)) **2. Bitbucket (~$3.30-3.65/user/mo Standard, $16.50 flat for ≤5 users)** - The value pick, and the obvious answer if you already run Jira for client work. The Jira↔branch/PR linking is genuinely better than any GitHub integration, which matters when you're billing against tickets. Flat pricing under 5 users is great for a small shop. Weaker ecosystem and Pipelines is less pleasant than Actions. ([pricing comparison](https://tech-insider.org/sv/github-vs-gitlab-vs-bitbucket-2026/)) **3. GitLab (Free tier, or Premium at ~$29/user/mo)** - I'd use the **Free** tier here, not Premium. Nested groups are the best structure in the market for agencies - a group per client, subgroups per project, permissions inherited - and you get CI, registry, and issue boards in one tool. Premium at $29/seat is hard to justify for an agency unless you need the compliance and approval controls; it bundles 10,000 CI minutes and security scanning, which is a real value story for enterprise, less so for client sites. ([pricing](https://guptadeepak.com/tools/top-5-git-hosting-platforms-2026/)) **4. Forgejo or Gitea, self-hosted** - Worth a serious look if seat costs are eating you alive. Both run in 200-512MB RAM on a $5-15 VPS, so you get unlimited repos and unlimited client "reviewer" accounts for a fixed monthly cost - which flips the economics completely when you have 40 clients who each want read access. CI is GitHub-Actions-compatible, so workflows port over. Forgejo is community-owned under Codeberg e.V. and GPL; Gitea is MIT with a commercial edition. Pick one deliberately - after years of divergence, migrating between them is no longer trivial. The cost is that you now operate backups and upgrades, and you can't hand a client a familiar URL. ([comparison](https://selfhosting.sh/best/git-hosting/), [resource requirements](https://tech-insider.org/?p=20561)) **5. Azure DevOps** - Only if your clients are Microsoft/.NET shops with Entra ID and that's the gravity you live in. I'd skip Beanstalk despite it marketing itself at web agencies - the ease-of-use pitch doesn't compensate for a thin ecosystem in 2026. **What I'd actually do:** GitHub Team as the home for all client code, one repo per client, and a hard rule that clients get access only at handoff or via a transferred repo rather than as standing seats. If your client-access seat count climbs past roughly 15-20, self-host Forgejo alongside it for the read-only client mirrors and keep active development on GitHub. Sources: - [Top 5 Git hosting platforms 2026](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/) - [GitHub docs: outside collaborators](https://docs.github.com/en/[email protected]/organizations/managing-user-access-to-your-organizations-repositories/managing-outside-collaborators/adding-outside-collaborators-to-repositories-in-your-organization) - [Best self-hosted Git platforms 2026](https://selfhosting.sh/best/git-hosting/) - [Gitea vs Forgejo vs GitLab CE resource comparison](https://tech-insider.org/?p=20561) - [Best Git hosting services 2026](https://www.itechguides.com/best/git-hosting-services/)

Near this answer

The same question, recorded on other dates: 2026-10-09, 2026-10-07, 2026-10-04, 2026-10-02, 2026-09-30, 2026-09-28, 2026-09-25, 2026-09-23, 2026-09-21, 2026-09-17, 2026-09-15.

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

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.