Licensing overview
Overview of Xopero ONE licensing models, including license types, usage-based components, and key licensing principles.
Licensing in Xopero ONE 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 Xopero ONE 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 physical endpoints, servers, virtual machines, SaaS platforms, 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.
Pricing
Use the request form on the Xopero ONE website, and one of our representatives will contact you with information on available offers and pricing.
To get a tailored offer for your business, please email sales@xopero.com.
License types
Below you can find all license types available in Xopero ONE, categorized by protected resource type.
For information about Xopero Unified Protection (XUP) licensing model, please refer to this article.
Workstations & servers
Endpoint Agent โ licenses for securing physical endpoints running Windows, Linux, or macOS. One license is required per endpoint.
Server Agent โ licenses for securing servers (Windows and Linux), databases (Oracle, MySQL, Microsoft SQL Server, PostgreSQL, etc.), and NAS devices. One license is required per protected resource.
Virtual machines
Virtual Agent per VM โ licenses for securing virtual machines based on the number of VMs. It enables to secure systems directly from within the guest OS.
If you need to secure other virtualization platforms not natively supported by Xopero ONE (such as Proxmox, Xen, KVM, or Nutanix), you can still protect virtual machines directly from within the guest OS.
VMware per socket โ licenses for securing VMware environments based on the number of CPU sockets. This licensing model allows backup of unlimited number of virtual machines from the host level. All CPU sockets are counted, regardless of whether they are populated; therefore, both occupied and unoccupied sockets must be included in the total count.
If your environment is clustered, a license is required for each individual host, per socket.
Hyper-V per socket โ licenses for securing Hyper-V environments based on the number of CPU sockets. This licensing model allows backup of unlimited number of virtual machines from the host level. All CPU sockets are counted, regardless of whether they are populated; therefore, both occupied and unoccupied sockets must be included in the total count.
If your environment is clustered, a license is required for each individual host, per socket.
Microsoft 365
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.
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:
GitProtect Enterprise (on-premises) โ a license type that enables backup of all on-premises systems installed across the entire company.
GitProtect Enterprise (cloud) โ a license type that enables backup of all cloud-hosted systems across the entire company.
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
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
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, Xopero ONE 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:
Cloud worker โ agent responsible for running backup tasks in SaaS deployments. Each Xopero ONE environment is assigned one cloud worker.
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 Xopero ONE Management Service and enables copying its settings. A maximum of one license is available in the license package.
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 administrationLast updated
Was this helpful?

