Merge-request governance for GitLab
MergePilot
MergePilot classifies GitLab merge requests by rule, approves the ones that qualify and keeps a Jira change-management ticket in step with each one. Risk scoring covers change windows, blackout periods, file footprint and size, and can block a merge request; secret and dependency scans run alongside, with DORA metrics and compliance reports on top.
What it does
- Rule-based classification of GitLab merge requests and auto-approval.
- Jira change-management tickets opened, validated and closed with the merge request.
- Risk scoring (change windows, blackout periods, file footprint, size) with optional blocking.
- Secret scanning (gitleaks) and dependency scanning (OSV).
- DORA metrics and compliance reports (CSV, PDF); full audit trail.
- Integrates with GitLab, Jira, LDAP/OAuth, Slack, Microsoft Teams and email.
- Self-hosted on Docker or Kubernetes (Helm).
Deployment
| Option | MergePilot |
|---|---|
| Self-hosted | Yes (Docker, Helm) |
| Air-gapped installs | — |
| Offline licence | — |
| Free tier | — |
See MergePilot on your own systems
Talk to the engineers who build it, or read the full documentation on the product site.