Get Support

Have a question, found a bug, or need help integrating GitGuard? We're here to help. Fill out the form below and our team will get back to you promptly.

Submit a Request

All fields are required unless marked optional.

Frequently Asked Questions

Common questions about GitGuard's features, integrations, and compliance capabilities.

GitGuard integrates directly through the GitLab Duo Agent Platform. Once enabled, it automatically monitors merge requests in your repositories. It hooks into your CI/CD pipeline via webhooks, analyzes code changes against your defined compliance policies, and posts inline comments with citations directly on the merge request. No code changes or additional infrastructure required.
GitGuard supports SOC 2, HIPAA, PCI-DSS, GDPR, SOX, and ISO 27001 out of the box. You can also define custom compliance policies tailored to your organization's specific requirements. Policies are written in a simple YAML format and can be versioned alongside your code.
When GitGuard detects a critical or high-severity compliance violation, it can automatically trigger a voice call to your designated on-call team members. The call provides a summary of the violation, the affected merge request, and specific policy citations. This ensures urgent issues are never missed, even outside of working hours. Voice escalation is powered by Twilio and is fully configurable.
GitGuard works with GitLab Premium and Ultimate tiers, as it leverages the GitLab Duo Agent Platform which is available on these plans. Both self-managed and GitLab.com (SaaS) instances are supported. The core webhook-based analysis features can work with Free tier projects, but the full Duo Agent integration requires Premium or above.
GitGuard sends only the relevant code diffs (the changes in a merge request) to Anthropic's Claude API for analysis. Your full codebase is never transmitted. All API communication is encrypted in transit via TLS. We do not store your code beyond the duration of the analysis. You can also configure GitGuard to redact sensitive patterns (API keys, secrets) before analysis.
Compliance policies are defined in a .gitguard.yml file at the root of your repository. You can specify which frameworks to enforce, set severity thresholds, define custom rules with regex patterns, configure notification channels, and set up escalation workflows. Changes to policies are version-controlled and take effect on the next merge request.