Compare

Bitbucket vs Forgejo

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

What each one is

Bitbucket. Code and CI/CD platform powered by AI and the Atlassian platform that accelerates software delivery from idea to code to production, with seamless connection to Jira

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

Where Bitbucket is ahead

Bitbucket passes machine-readable metadata, and Forgejo does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: structured api reference. Forgejo misses it.

And on adopt, no mandatory sales call and official typescript sdk. Forgejo misses those.

Finally, on operate, rate-limit behavior predictable. Forgejo misses it.

Where Forgejo is ahead

Forgejo passes public docs discoverable, and Bitbucket does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: pricing understandable. Bitbucket misses it.

And on adopt, free trial or free allowance. Bitbucket misses it.

What neither does

Both fail llms.txt published, llms-full.txt / full agent docs, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, self-service signup, agent-compatible signup flow, programmatic credential creation, fast time to first request, copyable quickstart, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, agent compatibility verified. 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. Bitbucket misses public docs discoverable, llms.txt published, llms-full.txt / full agent docs; Forgejo misses llms.txt published, llms-full.txt / full agent docs, machine-readable metadata.

Understand. Bitbucket leads 38 to 31. Bitbucket misses openapi / spec quality, pricing understandable, 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. Bitbucket leads 50 to 35. Bitbucket misses self-service signup, agent-compatible signup flow, programmatic credential creation, free trial or free allowance, fast time to first request, copyable quickstart; 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 is whether an agent can run against it in production and recover when a call fails. Bitbucket leads 50 to 35. Bitbucket misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, agent compatibility verified; Forgejo misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

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

Signal by signal

Which to pick

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

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