For teams
What exists today
Mergerie runs on one developer's machine, for that developer: a local Node + SQLite server, a web UI, and the claude or copilot CLI of that person. A team can already share the important part — review rules, verifiers and prompt templates live in a single database file that can be copied — but every developer runs their own instance, and the reports stay on their machine unless they publish them on the merge request.
What a team edition could be
Nothing below exists. It is a list of what companies on self-hosted GitLab have asked about, written down so you can say which ones matter to you.
- A shared server on your infrastructure — never a SaaS: the whole point is that code does not leave the company.
- Review rules, verifiers and prompt templates managed once, applied to everyone.
- A team dashboard: what is waiting for a decision, what is verified green, who is reviewing what.
- SSO (OIDC / SAML) and per-repository permissions.
- An audit trail: which review was published, by whom, from which report version.
- Automatic review and verification of every new merge request, with the verdict posted on the MR.
No date and no promise: the order and the existence of these items depend on who asks. The email below is the whole product process.
Tell me what you would need
An email, three lines: the size of the team, the forge and whether it is self-hosted, and what would make the tool usable for you. I answer every one.
Meanwhile: setting it up with you
If your team wants Mergerie running on its developers' machines, with review rules and verifiers written for your repositories, that is a day of work I do on site or remotely. Same address.