> For the complete documentation index, see [llms.txt](https://helpcenter.gitprotect.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.gitprotect.io/gitprotect-software/licensing-overview.md).

# Licensing overview

**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.

{% hint style="info" %}
To get a license, please contact one of our sales partners or email us directly at <sales@xopero.com>.
{% endhint %}

{% hint style="warning" %}
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**.
{% endhint %}

***

## Pricing

**GitProtect** pricing is available on the [official website](https://gitprotect.io/pricing.html).

{% hint style="info" %}
To get a tailored offer for your business, please use the [contact form](https://gitprotect.io/contact-us.html) on the **GitProtect** website.
{% endhint %}

***

## License types <a href="#license_types_from_a_business_point_of_view" id="license_types_from_a_business_point_of_view"></a>

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

### <mark style="background-color:blue;">Microsoft 365</mark> <a href="#microsoft_365" id="microsoft_365"></a>

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.

{% hint style="info" %}
Shared mailboxes require the same licensing as individual user mailboxes, with each shared mailbox requiring one **Microsoft** user license.
{% endhint %}

### <mark style="background-color:blue;">Git platforms</mark> <a href="#git_platforms" id="git_platforms"></a>

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.

{% hint style="info" %}
There is no need to assign a license to all repositories. The license is assigned only to the repositories that are to be protected.
{% endhint %}

### <mark style="background-color:blue;">Jira</mark>

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.

### <mark style="background-color:blue;">Confluence</mark>

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) <a href="#license_types_in_xopero_one_management_console" id="license_types_in_xopero_one_management_console"></a>

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.

{% hint style="info" %}
In an on-premises deployment model, these licenses must be assigned to an installed agent.
{% endhint %}

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.

{% hint style="danger" %}
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**.
{% endhint %}

***

## Useful links and items

{% content-ref url="/pages/mbJ4FiIhRkMOFhK2dgJQ" %}
[License administration](/management/license-administration.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://helpcenter.gitprotect.io/gitprotect-software/licensing-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.