The capabilities
Change policies
Decide which merge requests need a change approval, and which checks each kind of change must pass.
Learn moreRead the docsApprovals & separation of duties
Change approvals in Jira or the built-in tracker, decided by the right people and never by the author.
Learn moreRead the docsMerge gate
The VCS itself refuses the merge until the policy is met, on GitLab and on GitHub.
Learn moreRead the docsRisk & change calendar
Score every change by when, where and how much it changes, and hold risky ones.
Learn moreRead the docsSecurity scanning
Secrets, vulnerable and unhealthy dependencies, dependency sources, licenses, CI configuration, container images, infrastructure files and commit signatures, checked on every change.
Learn moreRead the docsVulnerability tracking & SBOM
A living inventory of the vulnerabilities on every default branch, and a software bill of materials on demand.
Learn moreRead the docsMonitor mode & bulk onboarding
Watch repositories first, see what change management would have done, then move them under it in bulk.
Learn moreRead the docsDirect changes
Pushes, force pushes and deleted branches that skipped change management are found and reported.
Learn moreRead the docsInsights
DORA metrics, a dashboard, a change calendar, My work, a compliance report and an audit log.
Learn moreRead the docsBuilt-in tracker
A change approval tracker inside Merge Pilot, for teams without Jira.
Learn moreRead the docsSee it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.
