Every step is recorded with who did what and when, so the audit trail and the metrics come from the same place as the gate.
Merge Pilot, by CloudNativeWorks, is change management for GitLab and GitHub merge requests. A change policy decides which checks each merge request must pass and who must approve it; change approvals open in Jira or the built-in tracker, and the merge stays blocked until the policy is met for the latest commit.
A merge request opens
GitLab or GitHub tells Merge Pilot by webhook.
A policy covers it
The first active change policy that matches its branches, repository, paths, size, author or labels.
Checks run
Secrets, dependencies, licenses, CI, code review, work items and risk, as the policy asks.
A change approval opens
For changes that need one, in Jira or the built-in tracker, assigned to an approver or left to the approver pool, as the policy says.
Approvers decide
In the tracker or in Merge Pilot; never the author.
The gate opens
For the latest commit only: by default a new commit needs a new decision, unless the policy keeps the approval.
What it covers
Each capability has its own page, and the documentation explains every setting.
All features- Change policiesDecide which merge requests need a change approval, and which checks each kind of change must pass.Read the docs
- Approvals & separation of dutiesChange approvals in Jira or the built-in tracker, decided by the right people and never by the author.Read the docs
- Merge gateThe VCS itself refuses the merge until the policy is met, on GitLab and on GitHub.Read the docs
- Risk & change calendarScore every change by when, where and how much it changes, and hold risky ones.Read the docs
- Security scanningSecrets, vulnerable and unhealthy dependencies, dependency sources, licenses, CI configuration, container images, infrastructure files and commit signatures, checked on every change.Read the docs
- Vulnerability tracking & SBOMA living inventory of the vulnerabilities on every default branch, and a software bill of materials on demand.Read the docs
- Monitor mode & bulk onboardingWatch repositories first, see what change management would have done, then move them under it in bulk.Read the docs
- Direct changesPushes, force pushes and deleted branches that skipped change management are found and reported.Read the docs
- InsightsDORA metrics, a dashboard, a change calendar, My work, a compliance report and an audit log.Read the docs
- Built-in trackerA change approval tracker inside Merge Pilot, for teams without Jira.Read the docs
Fits the tools you already use
Integrations
GitLab (GitLab.com or self-managed) and GitHub (github.com or Enterprise Server 3.12 and newer) for code; Jira (Cloud, Server or Data Center) or the built-in tracker for change approvals; Slack, Microsoft Teams, e-mail and webhooks for notifications; OIDC, SAML and LDAP for sign-in.
All integrationsDeployment
Runs in your own infrastructure, as several instances for availability, and works in networks without internet access. Your code and your change decisions stay inside your network; package lookups can go to mirrors inside it.
DeploymentSee it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.

