SourceHut alternatives
The highest-scoring alternative to SourceHut is Codeberg at 55/100 on the AgentReady, against 29/100 for SourceHut.
All scored in Git & Source Control.
| Score | Alternative | Compare |
|---|---|---|
| 55 | Codeberg | SourceHut vs Codeberg |
| 55 | GitHub | SourceHut vs GitHub |
| 53 | Bitbucket | SourceHut vs Bitbucket |
| 51 | Gitea | SourceHut vs Gitea |
| 50 | GitLab | SourceHut vs GitLab |
| 45 | Forgejo | SourceHut vs Forgejo |
What Codeberg does that SourceHut does not
Codeberg passes search discoverable, clear product positioning, public docs discoverable, mcp discoverable, pricing understandable, self-service signup, agent-compatible signup flow, free trial or free allowance, fast time to first request, copyable quickstart, mcp integration available, agent compatibility verified, and SourceHut fails them. That is the whole of the gap between the two scores, so if none of those matter to your agent the ranking above overstates the difference.
Why people look for an alternative
SourceHut fails search discoverable, clear canonical domain, clear product positioning, public docs discoverable, llms.txt published, llms-full.txt / full agent docs, mcp discoverable, machine-readable metadata, structured api reference, openapi / spec quality, pricing understandable, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, self-service signup, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart, mcp integration available, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. Each one is a place an unattended run stops, which is usually what sends someone looking in the first place.
Where SourceHut loses the points
| Pillar | SourceHut | What it measures |
|---|---|---|
| Discover | 20 | Can an agent find it at all: sitemap, robots, structured data. |
| Understand | 23 | Is there a spec, an llms.txt, a machine-readable description. |
| Adopt | 25 | Signup, keys, SDKs, and whether a human has to be involved. |
| Operate | 47 | Rate-limit headers, errors, status, and behaviour under load. |
SourceHut is weakest on discover at 20/100. An agent that cannot find the docs never gets as far as the API. If that is the part your agent depends on, take the ranking above seriously; if it is not, SourceHut may still be the right pick.
What an agent runs into with SourceHut
These are the findings from the last audit on 2026-08-25. Each one is a place unattended software stops, which is the practical reason to look at the list above.
- Make signup self-serve; an agent cannot sit through a sales call.
- Ship an MCP server so agents can call you as a tool.
- Make docs reachable without auth or navigation gymnastics.
- Publish MCP install instructions so agents can discover the server.
- Publish an OpenAPI spec so agents can generate a client.
- Flesh out the OpenAPI: paths, schemas, and descriptions.
- Document error responses as an enum in your OpenAPI.
- Let agents create API keys programmatically.
What this category actually supports
Across the 7 products scored in Git & Source Control, host a git repo is offered by 71%.
An agent can get this list directly: resolve("alternative to SourceHut") over the MCP server, or GET /v1/categories/git.