Ctrlk
🏠︎ HOME@ WEBSITE↘ FREE TRIAL✉︎ CONTACT SUPPORT
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Licensing overview

Overview of GitProtect licensing models, including license types, usage-based components, and key licensing principles.

Licensing in GitProtect defines how product usage rights are assigned and managed within an organization, covering subscription scope, activated instances, and available feature sets depending on the selected plan.

General information

Licenses are required to use GitProtect for backup and recovery. They define how data protection is enabled across different environments and workloads and are assigned based on the type and number of protected resources. Depending on the deployment scenario, licenses cover SaaS platforms, Microsoft 365 organizations, and repositories, ensuring that each protected element is properly accounted for within the licensing model.

To get a license, please contact one of our sales partners or email us directly at sales@xopero.com.

Cancellation and extension of a GitProtect license purchased through a marketplace (e.g., Atlassian Marketplace) are handled and billed directly by the marketplace, without GitProtect's involvement. If you encounter any issues with the transaction or marketplace functionality, please contact the respective marketplace's support team first.

Pricing

GitProtect pricing is available on the official website.

To get a tailored offer for your business, please use the contact form on the GitProtect website.

License types

Below you can find all license types available in GitProtect, categorized by protected resource type.

Microsoft 365

  1. Microsoft 365 — licenses for protecting Microsoft Exchange data (including individual mailboxes, calendars, contacts) and OneDrive, assigned based on the number of Microsoft 365 user accounts.

  2. Microsoft 365 PRO — licenses for protecting Microsoft Exchange data (including individual mailboxes, shared mailboxes, calendars, contacts), OneDrive, and SharePoint. Assigned based on the number of Microsoft 365 user accounts.

Shared mailboxes require the same licensing as individual user mailboxes, with each shared mailbox requiring one Microsoft user license.

Git platforms

Licenses for protecting Git repositories (Azure DevOps, Bitbucket, GitHub, GitLab), assigned based on the number of repositories:

  1. GitProtect Enterprise (on-premises) — a license type that enables backup of all on-premises systems installed across the entire company.

  2. GitProtect Enterprise (cloud) — a license type that enables backup of all cloud-hosted systems across the entire company.

  3. GitProtect PRO (cloud) — a license type that enables backup of the entire organization. It is designed for individuals, startups, and small teams.

There is no need to assign a license to all repositories. The license is assigned only to the repositories that are to be protected.

Jira

  1. Jira — protection for cloud-hosted Jira instances, assigned based on the number of users; the license must cover all users in the protected Jira instance.

Confluence

  1. Confluence — protection for cloud-hosted Confluence instances, assigned based on the number of users; the license must cover all users in the protected Confluence instance.

Backup agents (workers)

In addition to standard licenses, GitProtect provides supplementary free backup agent (worker) licenses used to initiate specific operations and processes within the software, depending on the use case or deployment scenario.

In an on-premises deployment model, these licenses must be assigned to an installed agent.

Free worker licenses allow you to manage storage, restore backups, and back up resources locally, when combined with a dedicated Microsoft 365, Git, Jira, or Confluence license:

  1. Cloud worker — agent responsible for running backup tasks in SaaS deployments. Each GitProtect environment is assigned one cloud worker.

  2. Local worker — licenses for an agent responsible for running backup tasks in on-premises deployments. It allows the agent to be run on the same host as GitProtect Management Service and enables copying its settings. A maximum of one license is available in the license package.

  3. Feature worker — licenses for an agent responsible for running backup tasks for Microsoft 365, Git platforms, Jira, and Confluence. It is always included in the license package in unlimited quantities.

Backup agents are used for process management and data restoration (e.g., restoring cloud platform data). A device assigned a free worker license cannot perform backups of its own local resources.

Useful links and items

License administration

Last updated

Was this helpful?