Sign in

Moru vs GitHub: Clone the repo. See what comes with you.

On GitHub, the code is in git and the project around it lives on GitHub’s servers. On Moru, requests, reviews, decisions and CI results are signed git objects in the repository. Try it.

The clone test

A repository on GitHub
$ git clone https://github.com/acme/app
A clone of a GitHub repository brings the code and its branches. Issues, reviews, check results, approvals and accounts stay on GitHub’s servers.
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 GitHub?

Moru is a self-hosted git forge built for coding agents. GitHub keeps issues, reviews and approvals in its own database. Moru stores them as signed git objects inside the repository, so they move with the code. On Moru, agents work in throwaway scratch repositories with a token for one repository that expires in hours, and nothing lands until a person approves it. GitHub is the better fit if you depend on its ecosystem, hosted CI machines, code search or Windows. You can also use both: link a GitHub repository and approved changes arrive there as pull requests.

What this page says about GitHub was checked against GitHub’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 An agent’s token leaks

GitHub
Tokens can be limited to chosen repositories and permissions, and an app’s installation token lasts an hour. None can be limited to a branch: branch protection and rulesets do that.
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

02 An agent writes something terrible

GitHub
Copilot’s cloud agent pushes to its own copilot/ branch in your repository. Branch protection, rulesets and required reviews decide what reaches the default branch.
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

03 You rebase, and the review has to survive

GitHub
After a force push, comments on lines that changed are marked outdated, and the replaced commits drop out of the pull request’s commit list.
Moru
A change keeps its ID across revisions. Every revision stays reachable, and the conversation carries over. If you use jj, Moru keeps the change IDs jj already gave your commits.
change kpqzrvlm
  r1  3f9a1c  14 comments
  r2  b27e04  rebased onto main
  r3  5d4f19  review carried over

04 You want several agents to try the same task

GitHub
Agent HQ can give one issue to Copilot, Claude and Codex. Each returns draft pull requests for people to compare. GitHub doesn’t rank them.
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

GitHub
Artifact attestations cover build outputs. Who reviewed and approved a pull request is recorded in GitHub’s database.
Moru
Every revision carries a signed record of which agent made it, where it ran and what it was asked. CI results are signed records too, and both 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

GitHub
Workflows run on GitHub-hosted or self-hosted runners. There’s no official way to run one locally; third-party tools such as act fill the gap.
Moru
moru-runner ci run runs a workflow’s job in your working tree, without a node. Workflows in .github/workflows run as they are, and ci lock pins every action and image.
moru-runner ci lock
moru-runner ci run checks/test

07 You want to leave

GitHub
Issues, pull requests, reviews and comments come out as JSON, in a migration archive or through the API.
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 backup moru.tgz
moru-node --data ./new restore moru.tgz

Fair is fair

Where GitHub wins

Moru leaves some things out on purpose. If one of these is why you’re on GitHub, stay there, or use both.

Ecosystem
Years of apps, integrations and a marketplace. Moru has webhooks, a REST API and MCP, and few integrations so far.
Everyone has an account
Contributors are already signed in. On Moru they bring a Bluesky or other AT Protocol account, or get an account from your node.
Hosted CI machines
Moru runs CI on your own runners only. There are no machines to rent.
Code search
Moru doesn’t have it.
Merge queue
Moru doesn’t have one.
SSH
Moru speaks git over HTTPS only.
Windows
Moru’s nodes and runners run on Linux and macOS. Windows jobs in a GitHub workflow’s matrix are dropped.

Questions

Is Moru an alternative to GitHub?

For teams that want their own forge and work with coding agents, yes. Moru hosts git repositories, reviews, CI and access control, and you run it yourself. It doesn’t try to match GitHub’s ecosystem, hosted CI machines or code search.

Can I use Moru and GitHub together?

Yes. Import a repository from GitHub and it stays linked: Moru follows its branches, Bake-offs start from GitHub’s main, and approved changes go back as pull requests. Unlink it when you want the node to be its home.

Do my GitHub Actions workflows run on Moru?

Most do, as they are. A repository without its own .moru/workflows runs the files in .github/workflows on your runners, and each workflow gets a report saying whether it runs as is, runs with notes, or is refused and why.

Which coding agents work with Moru?

Claude Code, Codex, Gemini CLI, or any agent you can start from a command line. Each runner belongs to one person and runs their agents on their machine.

Where are issues and reviews stored in Moru?

In the git repository, under refs/moru/. Moru’s issues are requests: anyone signed in who can read a repository can file one, and someone with write access triages it. Each request, discussion, review, label, milestone and decision is a chain of signed commits. The node’s database is only an index, rebuilt from the repositories.

You don’t have to move everything

Import a repository from GitHub and it stays linked: agents work in Moru, and the changes you approve arrive on GitHub as pull requests.

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