GitHub Actions Alternative, Self-Hosted

Rithub is a self-hosted alternative to GitHub Actions — push a .gitea/workflows/*.yml file and a runner you control picks it up, runs it, and reports status, with no shared-minutes limit and no third party holding your CI logs.

Why teams look for a GitHub Actions alternative

What Rithub's self-hosted CI gives you

How it was verified

  1. A runner was registered against the live Rithub instance and confirmed online with labels [ubuntu-latest ubuntu-22.04 ubuntu-24.04].
  2. A real repository was pushed with a .gitea/workflows/ci.yml containing a runs-on: ubuntu-latest job.
  3. Polling the run's API endpoint showed status go queued → running → success in under a minute.

Frequently asked questions

Is there a self-hosted alternative to GitHub Actions?
Yes — Rithub runs the same workflow format on a runner you control.

Do I need to rewrite my workflows?
Usually just rename the folder to .gitea/workflows; most workflow syntax carries over.

Why self-hosted instead of GitHub-hosted minutes?
No shared-minutes limit, full control of the runner's hardware and toolchain.

Has this actually been tested, not just enabled?
Yes — a real workflow run went queued → running → success on a registered runner, verified via the API.

See repositories already running on Rithub

Want an account? Email [email protected] to request access.