# Lessons on the Git server

- **Owning the forge closes the loop.** Code → CI → registry → cluster, all in one network you control.
- **Light is fine.** A single Go binary forge is plenty for a lab (and many small teams), and it's a joy to operate.
- **Lean on the API.** It's the seam where automation plugs in — runner registration, repo creation, CI secrets. Treat the forge as something you script, not just click.
- **It still ships logs centrally.** Even the Git server's logs land in Loki, so it's observable like every other box.