Sign in

Moru vs Forgejo: Just as light to run. More in the clone.

Forgejo and Gitea run from one binary on SQLite, and so does Moru. The difference is where the project lives: in their database, or signed in the repository. Try it.

The clone test

A repository on Forgejo
$ git clone https://git.example.com/acme/app.git
A clone of a Forgejo or Gitea repository brings the code, its branches and the commits of its pull requests. Issues, reviews, approvals and Actions results stay in the server’s SQL database.
A repository on Moru
$ git clone https://moruforge.com/git/acme/app.git
A clone of a Moru repository brings the code, and with one more fetch every request (Moru’s issues), discussion, label, milestone, Bake-off, revision, identity and access record, signed. They still verify after the repository moves.

The short answer

How is Moru different from Forgejo and Gitea?

Moru is a self-hosted git forge built for coding agents. Forgejo, and Gitea it was forked from, keep issues, reviews and approvals in a SQL database next to the repositories. Moru stores them as signed git objects inside the repository, so they move with the code and verify offline. On Moru, agents work in throwaway scratch repositories with a token for one repository that expires in hours, and several agents can try the same request in a Bake-off. Forgejo and Gitea are the better fit if you need package registries, code search, SSH or migrations from other forges with their issues.

What this page says about Forgejo was checked against Forgejo’s and Gitea’s documentation on .

What happens when…

Nobody switches forges over a feature list. They switch after a bad day.

Seven things that go wrong, or get tedious, on a team that works with agents. Pick who you are.

01 You back it up, and then you need the backup

Forgejo
Both keep the repositories on disk and everything people do around them in a SQL database: SQLite by default, or MariaDB, MySQL or PostgreSQL. forgejo dump and gitea dump zip the two together.
Moru
Everything that matters is in the repositories, signed. The node’s SQLite database is an index it can rebuild from them, and moru-node backup is safe while the node runs.
moru-node backup moru.tgz
moru-node --data ./new restore moru.tgz

02 An agent’s token leaks

Forgejo
Since Forgejo 15, a token can be limited to a list of repositories, with read or write on code and issues. Neither project’s documentation mentions tokens that expire, or that are limited to a branch.
Moru
The agent’s token names the agent, the person it works for, one repository, the scratch repository and refs it may push, and what it may do. It expires after 4 hours by default and is checked on every push and API call.
agent      did:key:z6Mk…q4
for        did:plc:alice…
repo       acme/app
push to    scratch/01JC8…
expires    in 3h 52m

03 An agent writes something terrible

Forgejo
Forgejo has no features for agents: an agent pushes with a token like any script. Gitea Enterprise sells agents as an add-on, bot accounts that work through Gitea Actions with short-lived tokens.
Moru
The agent never writes to your repository. It works in a throwaway scratch repository, only the change it submits crosses over, and nothing merges until a person approves it.
scratch/01JC8….git   push ✓
  └─ submit kpqzrvlm  → acme/app
                        waiting for your review

04 You want several agents to try the same task

Forgejo
Neither documents a way to give one task to several agents and compare what comes back.
Moru
A Bake-off: up to eight agents, any mix, get the same request. Reviewer agents rank what comes back with their reasons, and you pick one, or overrule them.
1st  claude-opus    kpqzrvlm  +64 −9
2nd  codex          wmtyxopl  +112 −31
3rd  gemini         zrnvoxkm  +18 −2

05 Someone asks who made this, and who checked it

Forgejo
Both verify signed commits and can sign the merge commits they make, for example only for approved merges into a protected branch. The approvals themselves aren’t signed: they’re recorded in the database.
Moru
Every revision carries a signed record of which agent made it, where it ran and what it was asked. Approvals and CI results are signed records too, and all of them verify offline.
moru-node verify acme/app kpqzrvlm
r3  agent-run  did:key:z6Mk…q4  ✓
r3  ci-run     checks/test      ✓

06 CI breaks and you want to debug it on your machine

Forgejo
Both runners run a workflow locally: forgejo-runner exec and gitea-runner exec. Forgejo Actions aims to feel familiar to GitHub Actions users, not to be compatible; Gitea aims to be compatible.
Moru
moru-runner ci run does the same, and ci lock pins every action and image. Workflows in .github/workflows run as they are, and each gets a report: runs as is, runs with notes, or refused and why.
moru-runner ci lock
moru-runner ci run checks/test

07 You want to leave

Forgejo
forgejo dump-repo writes a repository’s issues, pull requests, comments, labels, milestones and releases to files, and restore-repo loads them into another Forgejo.
Moru
Clone the repository, back the node up, or import the repository into another node. The review history comes along and still verifies.
moru-node import-repo acme/app \
  https://old.example.com/git/acme/app.git

Fair is fair

Where Forgejo wins

Forgejo and Gitea are mature forges with features Moru leaves out. If one of these is why you chose them, stay.

Migrations from other forges
Forgejo brings repositories over with their issues and pull requests, and Forgejo 17 brings reviews from Bitbucket Data Center. Moru links GitHub repositories and copies code from any git URL.
Package registries
Forgejo hosts 23 kinds of package, from Cargo and npm to containers. Moru hosts none.
Code search
An optional indexer: Bleve or Elasticsearch, and Zoekt on Forgejo. Moru doesn’t have code search.
SSH
Both have a built-in SSH server. Moru speaks git over HTTPS only.
Windows
Gitea ships Windows binaries. Forgejo dropped Windows in 2024, and Moru runs on Linux and macOS.
Federation, on its way
Forgejo’s ActivityPub federation is experimental. Moru doesn’t federate.

Questions

Is Moru an alternative to Forgejo or Gitea?

For teams that work with coding agents, yes. All three are light to run. Moru keeps reviews and decisions signed in the repository, and gives agents scratch repositories, short-lived tokens and Bake-offs. It doesn’t have package registries, code search or SSH.

Do Forgejo Actions workflows run on Moru?

Moru reads .moru/workflows and .github/workflows, not .forgejo/workflows or .gitea/workflows. Moved to .github/workflows, a workflow is checked like a GitHub one: it runs as is, runs with notes, or is refused with the reason.

Can I bring a Forgejo or Gitea repository to Moru?

Its code, yes: moru-node import-repo copies a repository from any git URL, with its branches and tags. Issues and pull requests don’t come across.

Does Moru need a database server?

No. A node keeps everything in one data directory: the git repositories, its keys, and a SQLite index it can rebuild from the repositories.

Where are reviews stored in Moru?

In the git repository, under refs/moru/. Each request, discussion, review and decision is a chain of signed commits. The node’s database is only an index, rebuilt from the repositories.

Try it next to Forgejo

Import a repository’s code, give agents a request, and see what review looks like when it lives in the repository. Your Forgejo stays as it is.

Command menu
Search for a page, repository, change or request, or run a command