Forgejo Runner

Forgejo Runner is a self-hosted continuous integration / continuous deployment (CI/CD) runner that executes automated Forgejo Actions workflows, letting you…

  • Development
  • Other
  • Productivity
  • Tools & Utilities
Forgejo Runner is a self-hosted continuous integration / continuous deployment (CI/CD) runner that executes automated Forgejo Actions workflows, letting you run build, test, and deploy jobs for your repositories on a Forgejo instance (defaulting to Codeberg).

Platform availability

Available on 4 of 10 platforms

  • Unraid
  • TrueNAS
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

60/100 Good

Maintained
65last commit 131 days ago
Popular
3556 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
502 GB minimum RAM
Security check
85no serious findings, CI

Availability: platform listings confirmed today, links checked today

GitHub stars
56
Open issues
4
Last commit
2026-07-13
Latest release
v12.13.0
License
MIT
Activity
stale

Checked yesterday - source: GitHub (Crown0815/Forgejo-runner-windows-builder)

Resources & Compatibility

Minimum requirements: 2 GB RAM, 1 CPU core(s).

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set credentials for private images When a job uses a private container image, put the registry username and password in the container credentials block for that job. Without this, the runner cannot pull the image and the job stops before any step runs. source
  • Keep logins in secrets If your runner needs registry or database passwords, save them as repository secrets (saved password variables) and refer to them by name instead of writing them into workflow files. Without this, the login can be exposed and your jobs can fail when the secret is missing or rotated. source
  • Match service names in commands If you add a helper service such as a database, use the service key you gave it as the host name in your commands. If the names do not match, the command cannot find the service and the job fails. source
  • Pre-built Windows binary Use the pre-built Windows binary for straightforward Windows installation without manual compilation. source

Fetched 44 days ago - each note links to its source

Alternatives (7)

  • Gerrit - Gerrit is an open-source, web-based code review and project management platform for Git repositories that enables development teams to coll…
  • GitBucket - GitBucket is a self-hosted Git web platform built in Scala that provides a lightweight GitHub-compatible repository, issue, pull request, a…
  • GitHub - Web-based Git hosting service facilitating collaboration, with features like issue tracking, social networking, and wikis for project manag…
  • GitLab - GitLab is a self-hosted Git repository server and software delivery platform for individuals and teams to privately plan, version, build, t…
  • RhodeCode - RhodeCode is a self-hosted code review and repository management platform for Git, Subversion, and Mercurial.
  • SourceForge - Open source community and software directory offering code hosting, analytics, version control, project management, and access to over 50,0…
  • gitness - Gitness is an open-source, self-hosted development platform for code hosting and automated continuous integration, offering small teams and…

Checked 52 days ago - source: AlternativeTo

Common questions

Can multiple Forgejo Runner installations connect to the same Forgejo instance?

Yes, multiple runner installations can connect to a single Forgejo instance to distribute jobs across available compute resources.

What security risk is associated with running Forgejo Runner?

Forgejo Runner performs remote code execution, which poses significant security threats to the host and network it operates upon.

Why does a job using a private container image stop before any step runs?

The runner cannot pull the image unless the job includes the registry username and password in its container credentials block.

Why can't a job find a helper service such as a database?

Use the service key you assigned to the service as the hostname in your commands; mismatched names prevent the command from finding the service.

How can workflows target a specific runner?

Use custom labels to target specific runners, such as labels for Windows-specific jobs.

Answers sourced from forgejo.org, forgejo.org, github.com

Community

Collected 49 days ago - public community threads