Skip to main content

Licensing & pricing

Merge Pilot is licensed per installation: one license, activated online with a license key or offline with a signed license file, covers every company, user and repository on it. There is no public price list; prices are quoted for your organisation.

How the license works

One license for the installation

A platform admin activates the license under Settings, on the License tab. It applies to the whole installation: Merge Pilot does not count users, repositories or companies against it. All instances of an installation share one fingerprint, so they use a single activation.

Read the docs

Online activation

With the license API key saved, a license key is activated with the license server. Merge Pilot asks the server again when it starts, once in the last day before the expiry, every hour while the license is not valid, and when a platform admin selects Check now. The signed answer stays in force until the expiry day, also while the license server cannot be reached.

Read the docs

Offline license file

For networks without internet access, a signed license file is uploaded instead. Merge Pilot never contacts the license server for an offline license; the file is valid until the expiry day in it.

Read the docs

Plan and expiry

The License tab shows the mode (online or offline), whether the license is valid, its plan, its expiry day, when it was last checked and the installation's fingerprint. A license without an expiry day does not expire.

Read the docs

When a license expires

Announced ahead

Every active company is notified with the License expiring event 30, 7 and 1 days before the expiry, and once more when the license has expired and its grace period starts. In the last 7 days a banner shows the days left to everyone signed in.

Read the docs

Grace period

After the expiry, Merge Pilot keeps working as usual for a grace period, and every page says until when. It is 14 days by default; a platform admin sets it from 0 (none) to 90 days.

Read the docs

Without a valid license

Once the grace period is over, or when no license is installed, Merge Pilot refuses the webhooks of your VCS and tracker, so new merge requests are not processed, and a banner tells everyone signed in. Sign-in and the rest of Merge Pilot stay available, so a platform admin can add a license.

Read the docs

Renewal

A renewed online license is picked up by the check in the last day before the expiry, by the hourly check while the license is not valid, or at once with Check now. An offline license is renewed by uploading the new file.

Read the docs

Recorded

Activating, checking and removing the license, and saving the license API key, are recorded in the audit log.

Read the docs

Pricing

Merge Pilot has no public price list. Tell us about your environment and we will send you a quote.

Questions

Is there a free version?

No. Without a valid license Merge Pilot does not process merge requests. To see it on your own repositories, ask us for a demo.

Does licensing need internet access?

No. An offline license file is checked on your server, and Merge Pilot never contacts the license server for it.

What if the license server cannot be reached?

An online license stays valid until its expiry day on the last signed answer. If the server still cannot be reached once that day has passed, the grace period follows, and after it Merge Pilot is unlicensed until the server can be reached.

Does Merge Pilot count users or repositories?

No. The license is checked for the installation as a whole; Merge Pilot does not count users, repositories or companies against it.

Do several instances need separate activations?

No. The instances of one installation share its fingerprint and use one activation of the license.

See it on your own repositories

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