Plombir Git

A lightweight, self-hosted Git forge for teams where code is written by people and AI agents alike.

Rust License: AGPL-3.0-or-later

Built with codeindexer.com: two developers and AI agents took a 114,400-line fork to a forge you can run, in three months, by sweeping every class of defect until it was closed — how.

Plombir Git hosts repositories, issues, pull requests, code review, CI, a wiki and package registries — and treats an AI agent as a participant of its own: its own account, its own narrowed token, its own audit trail, while a person keeps the approval that opens the merge. One server process, in the same space as Gitea and Forgejo.

_{An agent opens a pull request under its own bot account and applies a review suggestion over MCP; a second person approves and merges it.}

Try it in one command

docker run --rm -p 8080:8080 -p 2222:2222 ghcr.io/nettechnologys/plombir-git:latest plombir-git trial

No secrets, config files or build. The log prints a setup link — open it, create the administrator account, and you have a forge at http://localhost:8080. Trial mode says so on every page and is not for production: with --rm the data goes with the container. To keep it, add -v plombir-git-trial:/data and end the command with --data-dir /data.

Then:

• Connect your agent — Claude Code, Codex or Cursor over MCP, with a bot account and a narrowed token, in two minutes: docs/agents.md.
• Bring your repositories over from GitHub, GitLab, Gitea or Forgejo: issues and pull requests keep their numbers, with their reviews, approvals, labels, milestones and releases, and the import receipt lists what came over and what could not. It is the first button on an empty dashboard.
• Deploy it for real with Docker Compose, TLS and backups: deploy/README.md.

Why Plombir Git

1. Agents work under their own name, and a person approves. MCP is built into the server, any user can create a bot account, its token can be narrowed to repositories and tools, and a bot's approval never opens a protected merge. Details
2. Release assets that can be verified outside the forge: in-toto / DSSE attestations signed with the instance's published key. Details
3. CI that runs what you wrote, or refuses by name: a strict subset of Gitea / GitHub Actions where an unsupported key fails the run instead of being dropped. Details and the honest comparison with Gitea

A look around

Pull request from an agent. The bot account is marked, and so is the person it works for.	Code review. Inline comments and suggestions; the agent applies one and answers in the thread.
CI. Stages, jobs and logs from .plombir-git-ci.yml, .gitea/workflows or .github/workflows.	Audit log. Every MCP tool call an agent makes is recorded.

The screenshots come from a local demo instance with made-up users and a made-up project. The whole agent loop is also an integration test and a terminal recording, docs/demo/agent-review.cast.

Documentation

Connect your agent	Bot account, narrowed token, Claude Code / Codex / Cursor configs
MCP reference	The stdio binary, MCP over HTTP, agent accounts, working alone with your bot
Production deployment	Docker Compose, reverse proxy, backups, upgrades and rollback
Install from source	Requirements, build, secrets and rotation, first repository
Using Git	SSH and HTTPS, pull and push mirrors, Git LFS
CI and Actions subset	Pipelines, workflows, and the runner
REST API and CLI	Endpoints and OpenAPI; every plombir-git subcommand
Features and stack	What each area does, and where its code lives
Why Plombir Git, in detail	The three reasons, the Gitea comparison, measured memory
How it is built	The recursive sweep, who does what, and what every change passes
Development, ARCHITECTURE.md, CONTRIBUTING.md	Repository layout, tests, crate boundaries

Who makes it

Plombir Git is made by NetTechnologys s.r.o.: Yahook and vadiksext, working with AI agents. Our own team already does its work in it.

A lot of work from every side went into making it hold up. Three months of the recursive sweep closed one class of defect after another, each with a test and a check that runs before every push. Outside the team, Rinat (hicaru) wrote a full code review and security audit, and Alexey Stupenkov (alexio777) sent 18 pull requests, most of them security hardening. Every outside finding was checked against the code before anything changed — how it is built.

Origin. Plombir Git is a fork of IronForge. See NOTICE for provenance and licensing details.

License

Plombir Git is free software under the GNU Affero General Public License v3.0 or later, © NetTechnologys s.r.o.. You may use, study, modify and share it. If you run a modified version for other people over a network, the AGPL asks you to offer them its source.

A commercial license without the AGPL obligations is available from the copyright holder. Contributions are accepted under the Contributor License Agreement. See NOTICE for the fork's upstream provenance and the MIT terms of the code that came from IronForge.