Documentation
Secure Git Bridge documentation and operating paths.
Use these public guides to understand the supported workflow. Customer-specific activation, billing, licensing, and troubleshooting belong in the authenticated account and Support path.
Start here
- Get Started — install Secure Git Bridge, add a repository, connect AI, and review the first patch.
- How It Works — understand the trust and repository boundary.
- Security — protected files, data flow, patch authority, signing, and vulnerability reporting.
- Release Verification — version, build, package SHA-256, and release provenance.
Commercial and account documentation
- Pricing — Free, Pro, Team, and Enterprise paths.
- Teams — membership, team policy, administration, and member activation.
- Customer account — devices, billing, activation, and authenticated support.
Developer security guides
- Secure AI coding assistant access to Git repositories — vendor-neutral guidance for repository access, protected files, review, isolation, and auditability.
- Secure ChatGPT access to a Git repository — the current ChatGPT-specific workflow and security model.
- Secure Claude Desktop access to Git repositories — install the Secure Git Bridge Claude connector once, then bind repositories in SSGB.
- Secure GitHub Copilot access to Git repositories — one VS Code MCP connector with repository binding controlled in SSGB.
- Secure Cursor access to Git repositories — one Cursor MCP connector with repository binding controlled in SSGB.
- Secure Gemini access to Git repositories — one user-scope Gemini MCP connector with repository binding controlled in SSGB.
Need help?
Existing customers should sign in to the customer account for account-scoped support. Security concerns can be sent to security@securegitbridge.com.