ScaiGit
ScaiGit is the git forge of the ScaiLabs platform: repositories, pull requests, issues, releases, wikis and CI, run as one isolated instance per organisation. People sign in with ScaiKey, CI jobs run in disposable ScaiBunker microVMs, and AI agents work through a governed tool interface in which every action has a risk tier and the risky ones wait for a human.
What you get#
- Your own instance. Each customer organisation gets its own ScaiGit: its own web address, database, storage and runners, kept separate from every other customer's.
- Sign-in with ScaiKey. No separate passwords. Your ScaiKey groups decide which organisations and teams you belong to, and leaving ScaiKey removes your access within a minute.
- The familiar forge. Repositories, branches and tags, pull requests with reviews, issues, labels and milestones, releases, wikis and packages, over HTTPS and SSH.
- CI that cleans up after itself. Forgejo Actions workflows (GitHub Actions syntax) run each job in a fresh ScaiBunker microVM that is destroyed when the job ends.
- AI agents with guardrails. Agents use ScaiGit through a Model Context Protocol (MCP) interface. Reads are free; writes are tiered; destructive actions need a person's approval; everything is audited in ScaiLog.
- Code search across the repositories you can see, for people and agents.
Built on Forgejo#
ScaiGit's core is Forgejo, the community-run git forge, kept close to its stock release. ScaiLabs adds the platform pieces — identity, the agent interface, runners, search — as separate services that talk to the core over its public APIs. Our few changes to the core are published under the GPL like the core itself.
Where to go next#
- New here? Start with the quickstart.
- How ScaiGit is put together: concepts.
- Step by step: guides for SSH keys, CI, agents and approvals.
- Lookups: reference, including every agent tool and its tier.
- Something not working: troubleshooting.
- What changed: changelog.