Forgejo alternatives
The highest-scoring alternative to Forgejo is Codeberg at 55/100 on the AgentReady, against 45/100 for Forgejo.
All scored in Git & Source Control.
| Score | Alternative | Compare |
|---|---|---|
| 55 | Codeberg | Forgejo vs Codeberg |
| 55 | GitHub | Forgejo vs GitHub |
| 53 | Bitbucket | Forgejo vs Bitbucket |
| 51 | Gitea | Forgejo vs Gitea |
| 50 | GitLab | Forgejo vs GitLab |
| 29 | SourceHut | Forgejo vs SourceHut |
What Codeberg does that Forgejo does not
Codeberg passes self-service signup, agent-compatible signup flow, fast time to first request, copyable quickstart, agent compatibility verified, and Forgejo 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
Forgejo fails llms.txt published, llms-full.txt / full agent docs, machine-readable metadata, structured api reference, openapi / spec quality, 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, fast time to first request, copyable quickstart, official typescript sdk, structured, predictable output, 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 Forgejo loses the points
| Pillar | Forgejo | What it measures |
|---|---|---|
| Discover | 80 | Can an agent find it at all: sitemap, robots, structured data. |
| Understand | 31 | Is there a spec, an llms.txt, a machine-readable description. |
| Adopt | 35 | Signup, keys, SDKs, and whether a human has to be involved. |
| Operate | 35 | Rate-limit headers, errors, status, and behaviour under load. |
Forgejo is weakest on understand at 31/100. Without a spec an agent has to guess at endpoints, and it guesses wrong. If that is the part your agent depends on, take the ranking above seriously; if it is not, Forgejo may still be the right pick.
What an agent runs into with Forgejo
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.
- 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.
- Ship an official TypeScript/JavaScript SDK on npm.
- Return X-RateLimit / Retry-After headers so agents pace themselves.
- Add /llms.txt so agents can find and read your capabilities.
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 Forgejo") over the MCP server, or GET /v1/categories/git.