Forgejo / Gitea Actions
Actions-compatible CI inside a self-hosted forge.
91
sovereigntyForgejo and Gitea both ship a CI runner that speaks the GitHub Actions workflow format, so a large share of existing `.github/workflows` files run unchanged — including many marketplace actions, which are just repositories. That compatibility is the point: it is the only option here where migration can be a copy rather than a rewrite. The trade is that you are adopting a whole forge, not just a build system, so it suits teams already considering moving off GitHub entirely rather than teams that only want cheaper minutes.
OPEN SOURCEMIT (Gitea) / GPL-3.0 (Forgejo)SELF-HOSTLOCAL-FIRST
LicenseMIT (Gitea) / GPL-3.0 (Forgejo)
PricingFree and open source; self-hosted on your own hardware.
Open sourceYes
Self-hostableYes
Local-first dataYes
What it does well
- +Workflow syntax is Actions-compatible — existing YAML often runs as-is
- +Many GitHub marketplace actions work because they are just repos
- +Comes with the git host, issues and packages in one binary
- +Forgejo is GPL-3.0 and community-governed under Codeberg
Where it falls short
- −Adopting it sensibly means moving your repositories too
- −Compatibility is high but not total — GitHub-specific contexts break
- −Smaller runner ecosystem; scaling out is manual work
- −Two similar projects with a contentious shared history to understand
Forgejo / Gitea Actions as an alternative to
Where Forgejo / Gitea Actions shows up in our comparisons, and how it ranked.
Forgejo / Gitea Actions head-to-head
Straight comparisons against the tools people weigh it against.