New: the hosted MCP server is live. Connect your agent in one command.Read the docs →
StackResolve logoStackResolve

Compare

Codeberg vs Forgejo

Codeberg scores higher on the AgentReady, 55/100 against 45/100. They differ on 7 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Codeberg. Codeberg is a non-profit Git hosting platform maintained by Codeberg e.V., based in Berlin, Germany.

Forgejo. Forgejo is a self-hosted lightweight software forge.

Where Codeberg is ahead

Codeberg passes self-service signup, agent-compatible signup flow, fast time to first request and copyable quickstart, and Forgejo does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.

It also holds operate: agent compatibility verified. Forgejo misses it.

Where Forgejo is ahead

Forgejo passes clear canonical domain, and Codeberg does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds adopt: official python sdk. Codeberg misses it.

What neither does

Both fail 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, no mandatory sales call, programmatic credential creation, official typescript sdk, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover. Forgejo leads 80 to 73. Codeberg misses clear canonical domain, llms.txt published, llms-full.txt / full agent docs, machine-readable metadata; Forgejo misses llms.txt published, llms-full.txt / full agent docs, machine-readable metadata.

Understand. Both sit at 31/100 here. Codeberg misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Forgejo misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt is whether an agent can get a key and make its first successful call without a human in the loop. Codeberg leads 62 to 35. Codeberg misses no mandatory sales call, programmatic credential creation, official typescript sdk, official python sdk; Forgejo misses self-service signup, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk.

Operate. Codeberg leads 53 to 35. Codeberg misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable; Forgejo misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

Codeberg does not publish a machine-readable starting price and has a free tier. Forgejo does not publish one and has a free tier.

Signal by signal

SignalCodebergForgejo
AgentReady5545
Discovery7380
Understanding3131
Adoption6235
Operability5335
Public APIYesYes
MCP serverYesYes
OpenAPI specUnknownUnknown
CLIYesYes
llms.txtNoUnknown
Self-serve signupYesUnknown
Free tierYesYes

Which to pick

Codeberg clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Codeberg and Forgejo. Alternatives to each: Codeberg, Forgejo.

An agent can fetch this as data: POST /v1/compare {"slugs": ["codeberg", "forgejo"]}