Skip to main content

Everything between opening a merge request and merging it

Merge Pilot turns your change management process into rules the VCS enforces, and records every decision on the way.

The capabilities

Change policies

Decide which merge requests need a change approval, and which checks each kind of change must pass.

Learn moreRead the docs

Approvals & 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 docs

Merge gate

The VCS itself refuses the merge until the policy is met, on GitLab and on GitHub.

Learn moreRead the docs

Risk & change calendar

Score every change by when, where and how much it changes, and hold risky ones.

Learn moreRead the docs

Security 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 docs

Vulnerability tracking & SBOM

A living inventory of the vulnerabilities on every default branch, and a software bill of materials on demand.

Learn moreRead the docs

Monitor mode & bulk onboarding

Watch repositories first, see what change management would have done, then move them under it in bulk.

Learn moreRead the docs

Direct changes

Pushes, force pushes and deleted branches that skipped change management are found and reported.

Learn moreRead the docs

Insights

DORA metrics, a dashboard, a change calendar, My work, a compliance report and an audit log.

Learn moreRead the docs

Built-in tracker

A change approval tracker inside Merge Pilot, for teams without Jira.

Learn moreRead the docs

See it on your own repositories

Ask for a demo on your own GitLab or GitHub repositories.