Docs menu
Start
- Quick start
- Access tokens: GitHub, Gitea, GitLab
- Run your AI agent through it
- Choose what gets checked
- Let your agent ask the gate (MCP)
Setup in depth
Policy and frames
- Choosing what the gate checks
- Frames and kits
- Groups and whitelist
- Excluding paths from scans
- Writing your own frames
Operate
- Day-to-day operations
- Notifications and Auto-PR
- Multiple agents
- Audit log analyzer and agent comparison
- Agent stats API
Server
Security
Extend
Help
Frame reference
nimblegate docs
Docs for nimblegate, the self-hosted git gateway that puts guardrails on AI coding agents: quick start, agent setup, access tokens, and a page for every check.
Try the live demoA real dashboard over sample data. Nothing to install.0 min
Quick startDocker, one repo, and your first blocked push.10 min
Full setup guideBare metal, LAN, TLS, other git hosts, and the why behind each step.Reference
Pick where it runs
The gateway needs one always-on Linux machine that your agents can push to but can't log into. Any of these works:
A small cloud serverPaste your SSH key, get a cloud-init file, create a small VPS with it. It boots hardened and running.1 paste, ~5 min boot
Docker on a box you haveA NAS, a Raspberry Pi or any Linux machine on your network. Images for amd64 and arm64.10 min
Proxmox containerA Debian LXC on your own Proxmox host, with every command marked by where it runs.Step by step
Bare metal for productionOne binary under systemd, with a separate relay user that holds the upstream credential.Reference