Sign in

Moru vs GitLab: Clone the project. See what comes with you.

On GitLab, the code is in git and the project around it lives in PostgreSQL. On Moru, requests, reviews, decisions and CI results are signed git objects in the repository, and the node is one container. Try it.

The clone test

A project on GitLab
$ git clone https://gitlab.com/acme/app
A clone of a GitLab project brings the code, its branches and the commits of its merge requests. Issues, threads, approvals and pipeline results stay in GitLab’s PostgreSQL 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 GitLab?

Moru is a self-hosted git forge built for coding agents. GitLab keeps issues, merge request threads and approvals in PostgreSQL. Moru stores them as signed git objects inside the repository, so they move with the code, and a node is one container with a SQLite index instead of PostgreSQL, Redis and Sidekiq. 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. GitLab is the better fit if you want one product for planning, registries and security scanning, hosted CI machines, code search or Windows.

What this page says about GitLab was checked against GitLab’s documentation on .

What happens when…

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

Eight things that go wrong, or get tedious, on a team that runs its own forge and works with agents. Pick who you are.

01 You have to run it yourself

GitLab
Self-managed GitLab is NGINX, Workhorse, Puma, Sidekiq, Redis, Gitaly and PostgreSQL, the only supported database. GitLab’s baseline for a single node is 8 vCPU and 16 GB of memory.
Moru
A node is one container image: the node binary with its web UI built in, plus git. Everything it keeps is in one data directory, its database is a SQLite index it can rebuild from the repositories, and it backs up while it runs.
docker run -d -v moru-data:/data -p 7070:7070 \
  ghcr.io/webstonehq/moru-node:latest
moru-node backup moru.tgz

02 An agent’s token leaks

GitLab
Project access tokens and fine-grained personal access tokens can be limited to one project and chosen permissions. They last up to 365 days unless an administrator changes the limit. Branch limits come from protected branches, not the token.
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

GitLab
GitLab Duo’s flows and external agents such as Claude Code and Codex run in a CI/CD pipeline and push to duo/ branches in your project, then open a merge request. Protected branches and approval rules 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

04 You rebase, and the review has to survive

GitLab
Every push adds a diff version you can compare with earlier ones, and threads on lines that changed become outdated. On Premium and Ultimate, approvals are removed when new changes arrive, by default. An export keeps only the latest diff.
Moru
A change keeps its ID across revisions. Every revision stays reachable in git, 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

05 You want several agents to try the same task

GitLab
Duo agents can work in parallel, but GitLab’s documentation describes no way to give one issue 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

06 Someone asks who made this, and who checked it

GitLab
GitLab verifies signed commits and signs the ones it makes itself. Runners can write SLSA provenance next to build artifacts. Who approved a merge request is recorded in GitLab’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      ✓

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

GitLab
gitlab-runner exec was removed in GitLab 17.0. The pipeline editor validates and simulates a pipeline, but there’s no official way to run a job locally. GitHub Actions workflows have to be rewritten for GitLab CI/CD.
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

08 You want to leave

GitLab
A project export is a .tar.gz of NDJSON with issues, merge requests, comments and approvers. It leaves out job logs and artifacts, CI/CD variables and the number of approvals required.
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 GitLab wins

GitLab does far more than Moru, and some of it you may need. If one of these is why you’re on GitLab, stay there.

One product for everything
Planning, package and container registries, security scanning and a CI/CD component catalog, with more in the paid tiers. Moru is a forge, CI and agents, and stops there.
Hosted CI machines
GitLab.com offers hosted Linux, macOS and Windows (beta) runners. Moru runs CI on your own runners only.
Imports from GitHub with history
GitLab brings over GitHub issues, pull requests and reviews. Moru links a GitHub repository instead of copying its issues.
Code search
Exact code search, on Premium and Ultimate. Moru doesn’t have it.
Merge trains
On Premium and Ultimate. Moru doesn’t have a merge queue.
SSH
Moru speaks git over HTTPS only.
Windows
Moru’s nodes and runners run on Linux and macOS.

Questions

Is Moru an alternative to self-managed GitLab?

For teams that want their own forge and work with coding agents, yes. Moru hosts git repositories, reviews, CI and access control in one container with no database server. It doesn’t try to match GitLab’s planning tools, registries, security scanning or hosted runners.

Does Moru need PostgreSQL or Redis?

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

Can I bring a GitLab project to Moru?

Its code, yes: moru-node import-repo copies a repository from any git URL, with its branches and tags. Issues and merge requests stay on GitLab; Moru doesn’t import them.

Does .gitlab-ci.yml run on Moru?

No. Moru runs its own workflows from .moru/workflows, or GitHub Actions workflows from .github/workflows, on your runners.

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, with their own subscription or API key.

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 GitLab

Import a repository’s code from GitLab, give agents a request, and see what review looks like when it lives in the repository. Nothing on GitLab changes.

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