Forgejo if you want the community-run forge and Actions. Gitea if you already operate that stack. Pick one.

What about Pipelines?

Forgejo Actions or Woodpecker. Do not expect Bitbucket Pipelines YAML to run unchanged.

Stacks / Backend

Easy

Forgejo / Gitea

Git you host. Forgejo is a community git forge; Gitea is MIT — Bitbucket Cloud without the workspace seat.

The problem

Bitbucket Cloud meters users and then sells Pipelines minutes. You wanted repos, PRs, and Actions-shaped CI. Forgejo is the community forge (GPL-3.0) with Actions. Gitea is MIT if you want that lineage. This is not Bitbucket's Jira/Bamboo suite.

Replaces

Bitbucket Cloud

Replace Bitbucket Cloud

Estimated SaaS saved

$1,200

per year, small team, before lock-in

Start on Railway

Woodpecker if the pain is Pipelines, not the git host

Sponsor this stack Tip jar

Placeholder: Forgejo (or Gitea) + a volume for repos and a database. Actions runners want Docker — often a second box. CI pipelines can sit on /stacks/woodpecker-ci. No one-click template in this repo yet — Start on Railway.

The stack

Forgejo
Community git forge plus Actions
Gitea
MIT self-hosted git

Cost table

You stop paying	Typical / year	Self-host instead
Bitbucket Cloud Standard (small team)	$1,200	Forgejo or Gitea + a volume

Agent setup prompt

Replace Bitbucket Cloud with Forgejo (preferred) or Gitea.

- Database + a volume for repositories. Bind HTTP to 0.0.0.0:$PORT. Import one repo (mirror or migrate).
- Actions: add a runner only if you need CI on this box. CircleCI-shaped pipelines can live on /stacks/woodpecker-ci.
- Lock registration. Write AGENT_PROMPT.md.

Also as markdown: /stacks/forgejo-git.md

FAQ

Forgejo or Gitea?: Forgejo if you want the community-run forge and Actions. Gitea if you already operate that stack. Pick one.
What about Pipelines?: Forgejo Actions or Woodpecker. Do not expect Bitbucket Pipelines YAML to run unchanged.