What does AI recommend for code repository hosting (agencies)? Checked 2026-10-22

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

Coverage: Claude (Anthropic) with web search. Other engines not included.

The question asked, verbatim: best code repository hosting for agencies. This page records one answer on one date. It is a measurement, not a ranking and not a recommendation.

Brands named, in the order the engine gave

1. per-seat mentioned
   For an agency the deciding factors aren't really features - they're per-seat cost when you have freelancers cycling in, how cleanly you can hand a repo to a client at the end of an engagement, and whether clients can be given access without becoming billable users.
2. GitHub mentioned
   GitHub (Team, ~$4/user/mo;
3. Bitbucket mentioned
   Bitbucket (Standard $3.30-3.65/user/mo, Premium ~$7.25) - The cheapest of the big three, and the right pick if your agency already runs Jira and Confluence for client project management.
4. Jira mentioned
   Bitbucket (Standard $3.30-3.65/user/mo, Premium ~$7.25) - The cheapest of the big three, and the right pick if your agency already runs Jira and Confluence for client project management.
5. Confluence mentioned
   Bitbucket (Standard $3.30-3.65/user/mo, Premium ~$7.25) - The cheapest of the big three, and the right pick if your agency already runs Jira and Confluence for client project management.
6. GitLab mentioned
   GitLab (Free tier, or Premium $29/user/mo) - Worth it in exactly one case: clients in regulated sectors who demand the code sits on infrastructure you or they control.
7. Beanstalk mentioned
   Beanstalk (from ~$15/mo) - Niche but a real fit for web shops doing WordPress/Shopify/PHP work: built-in deploy-to-staging-and-production with rollback, no CI config files to write, and it still speaks Subversion for legacy client codebases.
8. Niche mentioned
   Beanstalk (from ~$15/mo) - Niche but a real fit for web shops doing WordPress/Shopify/PHP work: built-in deploy-to-staging-and-production with rollback, no CI config files to write, and it still speaks Subversion for legacy client codebases.
9. WordPress mentioned
   Beanstalk (from ~$15/mo) - Niche but a real fit for web shops doing WordPress/Shopify/PHP work: built-in deploy-to-staging-and-production with rollback, no CI config files to write, and it still speaks Subversion for legacy client codebases.
10. Shopify mentioned
    Beanstalk (from ~$15/mo) - Niche but a real fit for web shops doing WordPress/Shopify/PHP work: built-in deploy-to-staging-and-production with rollback, no CI config files to write, and it still speaks Subversion for legacy client codebases.
11. Gitea / Forgejo mentioned
    Gitea / Forgejo (free, self-hosted) - Run it on a $10 VPS.
12. Forgejo mentioned
    Gitea / Forgejo (free, self-hosted) - Run it on a $10 VPS.
13. Run mentioned
    Gitea / Forgejo (free, self-hosted) - Run it on a $10 VPS.
14. GitHub Team mentioned
    What I'd actually do: GitHub Team as the agency's home, one org, one repo per client, clients added as outside collaborators rather than members so they don't hit your bill.

Sources the engine cited

The answer, as recorded

For an agency the deciding factors aren't really features - they're per-seat cost when you have freelancers cycling in, how cleanly you can hand a repo to a client at the end of an engagement, and whether clients can be given access without becoming billable users. Here's how I'd rank them: **1. GitHub (Team, ~$4/user/mo; Enterprise ~$21)** - The default, and for good reason. Unlimited private repos, outside-collaborator model that lets you give a client read access to one repo without paying for a full seat, and `Settings → Transfer ownership` makes handoff a two-minute job at the end of a contract. Actions is the CI everyone already knows, so a new contractor is productive on day one. Also the place clients' own in-house devs will expect the code to live when you leave. ([pricing comparison](https://www.getmonetizely.com/articles/which-version-control-platform-should-you-choose-github-vs-gitlab-vs-bitbucket-pricing-comparison)) **2. Bitbucket (Standard $3.30-3.65/user/mo, Premium ~$7.25)** - The cheapest of the big three, and the right pick if your agency already runs Jira and Confluence for client project management. Branch-to-ticket linking is native rather than bolted on, which matters when you're billing time against tickets. Weaker CI ecosystem than Actions, and fewer devs have used it. ([Atlassian comparison](https://www.atlassian.com/software/bitbucket/comparison/bitbucket-vs-gitlab)) ([pricing](https://www.getmonetizely.com/articles/which-version-control-platform-should-you-choose-github-vs-gitlab-vs-bitbucket-pricing-comparison)) **3. GitLab (Free tier, or Premium $29/user/mo)** - Worth it in exactly one case: clients in regulated sectors who demand the code sits on infrastructure you or they control. The self-managed edition gives you that, and you get SCM, CI, security scanning, and planning in one product so you're not stitching vendors together. At $29/seat it's expensive for a small shop, but the free self-hosted tier is genuinely capable if you have someone to run it. ([GitLab pricing 2026](https://www.activepieces.com/blog/gitlab-pricing-in-2026-what-teams-pay.md)) **4. Beanstalk (from ~$15/mo)** - Niche but a real fit for web shops doing WordPress/Shopify/PHP work: built-in deploy-to-staging-and-production with rollback, no CI config files to write, and it still speaks Subversion for legacy client codebases. Dated UI and users report speed complaints on Git; don't pick it if you need serious CI. ([Capterra reviews](https://www.capterra.com/p/212834/Beanstalk/)) **5. Gitea / Forgejo (free, self-hosted)** - Run it on a $10 VPS. The move when you have dozens of small client repos and per-seat pricing is eating you alive, or when a client wants the whole repo handed over as a server they own. You're the sysadmin, and there's no managed CI worth relying on. **What I'd actually do:** GitHub Team as the agency's home, one org, one repo per client, clients added as outside collaborators rather than members so they don't hit your bill. Transfer the repo into the client's own org at project close and keep yourself as a collaborator if you're on retainer. Add Bitbucket only if Jira is already your billing backbone, and GitLab self-managed only when a contract requires it. One thing worth nailing down in the contract regardless of platform: the repo is only one of the five things a client actually needs to own at handoff - domain registrar, analytics, and the billing method behind any paid dependencies travel with it, and those are the ones that get forgotten. ([handover checklist](https://ecommercefastlane.com/who-owns-your-shopify-store-code-agency-handover-checklist/)) Sources: - [Which Version Control Platform Should You Choose? GitHub vs GitLab vs Bitbucket Pricing Comparison](https://www.getmonetizely.com/articles/which-version-control-platform-should-you-choose-github-vs-gitlab-vs-bitbucket-pricing-comparison) - [GitLab Pricing in 2026: What Teams Pay](https://www.activepieces.com/blog/gitlab-pricing-in-2026-what-teams-pay.md) - [Bitbucket vs GitLab - Atlassian](https://www.atlassian.com/software/bitbucket/comparison/bitbucket-vs-gitlab) - [Beanstalk Pricing & Reviews - Capterra](https://www.capterra.com/p/212834/Beanstalk/) - [The Best Git Hosting Services in 2026 - iTechGuides](https://www.itechguides.com/best/git-hosting-services/) - [Who Owns Your Store Code? The Handover Checklist Most Brands Skip](https://ecommercefastlane.com/who-owns-your-shopify-store-code-agency-handover-checklist/)

Recorded 2026-10-22 through Claude (Anthropic) with web search, model claude-opus-5. Permanent address: /answers/s/code-repository-hosting-agencies-2026-10-22

Sources cited across the 22 recorded answers to this question

Alphabetical. A domain with a dated record links to it; the record says how often and when. Is one of these your site? Its record lists every recorded answer that cited it and carries the alert for the next citation.

activepieces.com · aiproductivity.ai · aloa.co · atlassian.com · azure.microsoft.com · blog.elest.io · capterra.com · comparetiers.com · contabo.com · costbench.com · dasroot.net · docs.github.com · ecommercefastlane.com · eesel.ai · en.wikipedia.org · forgejo.org · getmonetizely.com · getpricepulse.com · gforge.com · github.blog · github.com · gitnux.org · gitprotect.io · guptadeepak.com · help.github.com · itechguides.com · northflank.com · openalternative.co · pkgpulse.com · rhodecode.com · saascompared.com · saaspricepulse.com · saastruecost.com · selfhosting.sh · selfhostr.com · serverspan.com · sliplane.io · stackscored.com · tech-insider.org · techverdict.io · toolradar.com · valebyte.com · viasocket.com

Earlier recordings of this question

• asked 2026-10-20
• asked 2026-10-19
• asked 2026-10-17
• asked 2026-10-14
• asked 2026-10-12
• asked 2026-10-11
• asked 2026-10-09
• asked 2026-10-07
• asked 2026-10-04
• asked 2026-10-02
• asked 2026-09-30
• asked 2026-09-28
• asked 2026-09-25
• asked 2026-09-23
• asked 2026-09-21
• asked 2026-09-17
• asked 2026-09-15
• asked 2026-09-13
• asked 2026-09-11
• asked 2026-09-09
• asked 2026-09-06

Markdown edition · all recorded answers · weekly source index · 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.