Skip to main content

Runs in your infrastructure

Merge Pilot is installed in your own environment, next to your GitLab, GitHub and Jira. Your code, your change decisions and your audit trail stay inside your network.

Built for enterprise environments

Self-hosted

Runs in your data centre or your private cloud, alongside self-managed GitLab, GitHub Enterprise Server or Jira, or with their cloud editions.

Highly available

Several Merge Pilot instances run side by side: background work is shared between them and scheduled tasks run on one at a time. When an instance stops, its unfinished jobs are taken over by another.

Read the docs

Without internet access

The vulnerability and license sources (OSV.dev, deps.dev) and the exploitation feeds (CISA KEV, FIRST EPSS) can each point at a mirror inside your network; the exploitation feeds, and the NVD and CIRCL lookups for the severity of CVEs that OSV.dev does not rate, can be turned off. Only package names, versions and advisory IDs are looked up; your code never leaves. The license can be activated from an offline license file.

Read the docs

Fair to your VCS

A share of each VCS account's API rate limit is kept for live merge request events: history imports, bulk operations and periodic checks wait for the limit to reset instead of using it up.

Read the docs

Getting started

Contact us to plan Merge Pilot in your environment: your VCS and tracker editions, your identity provider and your network.

See it on your own repositories

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