What it is for
Merge Pilot decides which merge requests need a change approval, runs the checks the matching change policy asks for, opens the change approval in Jira or its built-in tracker, and keeps the merge blocked until the policy is met for the latest commit.
Policy, scanning and approval in one place
Instead of separate tools for change approval, security scanning and the VCS's own approval rules, one change policy decides which checks a change must pass and who must approve it.
Change policiesEnforced at the merge button
The gate lives in the VCS: a passing check on GitHub, the bot user's approval on GitLab. A new commit needs a new decision.
Merge gateNever the author
The author never approves their own change, and decisions made in the tracker count only when their maker may decide the change.
ApprovalsOne record
Every decision is recorded, so the audit trail, the compliance report and the metrics come from the same record as the gate.
InsightsWhy it runs in your infrastructure
Change decisions are sensitive: they touch your code, your approvals and your audit evidence. Merge Pilot is self-hosted, next to your GitLab, GitHub and Jira.
Your data stays with you
Your code, your change decisions and your audit trail stay inside your network.
DeploymentWithout internet access
The vulnerability and license sources can point at mirrors inside your network, and the license can be activated from an offline license file.
Read the docsSeveral instances
Several Merge Pilot instances run side by side and share the background work; when one stops, another takes over its unfinished jobs.
Read the docsSecrets encrypted
Connection tokens and other secrets are stored encrypted with AES-256-GCM.
Security & complianceContact
For a demo, a quote or any question about Merge Pilot, write to CloudNativeWorks.
See it on your own repositories
Ask for a demo on your own GitLab or GitHub repositories.
