InfoScale licensing covers the use rights for InfoScale, Arctera’s storage management and high-availability software for Linux, Unix and Windows. InfoScale descends from Veritas Storage Foundation and Cluster Server, whose old EULAs are still listed on infoscale.com.[7] The current terms are the Product Use Rights Document for InfoScale (version 2.6, InfoScale 9.1, GA 12 December 2025) and a companion document for InfoScale for Kubernetes. Both supplement the Arctera Software License Agreement and prevail over it where they conflict.[1][2] Within Cloud Software Group, InfoScale is its own business unit. Its Business Unit Terms point to infoscale.com/license-agreements for the product use rights.[4]
Editions
The InfoScale 9.1 PUR lists these products and meters:[1]
| Licensed software | Meter | Subscription | Perpetual |
|---|---|---|---|
| InfoScale Availability | Core Plus, Server | Yes | Yes |
| InfoScale Availability for SAP HANA DB | Cloud Instance | Yes | No |
| InfoScale Enterprise | Core Plus, Server | Yes | Yes |
| InfoScale Foundation | Core Plus, Server | Yes | Yes |
| InfoScale Storage | Core Plus, Server | Yes | Yes |
| InfoScale Enterprise OpenShift VE | Socket + Core | Yes | No |
Some features come only with subscription licences: SecureFS for SQL Server on Windows and for PostgreSQL on Linux, Secure Boot for Windows, Online Encryption for Windows and Linux, and VxFS Anomaly Detection.[1]
The InfoScale for Kubernetes PUR adds three editions, all on term licences:[2]
- InfoScale Storage for Kubernetes, on Core Plus, for on-premises Kubernetes clusters.
- InfoScale Enterprise for Kubernetes, on Core Plus.
- InfoScale Enterprise OpenShift VE Edition, on sockets.
In each case, total use across all clusters must not exceed the licensed quantity. A Developer Edition needs no License Instrument.[2]
The product versions also carry different grants. For InfoScale Availability and Enterprise, the PUR replaces the EULA licence grant with a grant for internal use at the licensed Use Levels plus one archival copy. Notably, it omits the EULA’s country restriction. For InfoScale Foundation and Storage, the replacement grant also includes cold disaster recovery rights.[1][3]
Metrics
- Core Plus. “the total number of number of Cores (based on processor - type) required for a hardware environment based on both the number and the type of Cores for such hardware”.[1] A Core is a processor execution core, “whether such Cores are virtual or physical”, and “Each “Core” where an Arctera product is deployed and/or running is required to be licensed.”[1]
- Server and Core licences. These cover a number of physical Servers, or Cores, for a given Tier and operating system platform. A Tier is “an Arctera defined classification of Server” that defines the hardware the software may run on.[1]
- Cloud Instance. One operating system installation in a cloud environment. On AWS or Azure, this is their basic unit of deployment for IaaS.[1]
- Socket pair. One OpenShift VE licence “for every 2 (two) CPU Sockets with a maximum of 128 Cores per pair”.[1]
Counting / floors
Core Plus
The Core Plus requirement is the number of cores in the hardware environment multiplied by the Core Coefficient for that processor type. Coefficients are listed in the Arctera InfoScale Core Coefficient table on SORT. The PUR’s own example uses 20 cores with a coefficient of 1.1, which requires 22 Core Plus licences.[1] The License Instrument states the number of Core Plus licences, based on the coefficient for the processor.[1] Catalog: Core Plus counts cores times the Core Coefficient.
Hardware refresh
A licence moved to new hardware is re-counted against the new hardware. If the new hardware needs more Core Plus licences than the old, “the customer must acquire additional Core Plus licenses to meet the Core Plus license requirements for the new hardware”.[1] The EULA treats a cross-grade to a new operating system, hardware tier or meter as replacing the old licence, which the customer must stop using.[3]
Cluster Server
Cluster Server (VCS) included with InfoScale may be used up to the number of InfoScale licences without extra licences. With InfoScale Storage, however, VCS “may be used solely for protecting and ensuring the availability of the filesystem components”. Adding other applications or agents to that configuration is not authorized.[1] Catalog: Cluster Server included with InfoScale has limited scope.
Virtualization & partitioning
In a virtual machine, the Core Plus requirement is “the total number of virtual Cores for such hardware multiplied by the applicable Virtual Core Coefficient”. In a cloud environment it is the cloud cores multiplied by the Cloud Core Coefficient.[1] For OpenShift VE, a worker node whose socket count or core count exceeds the pair threshold needs another licence.[1] Catalog: InfoScale in VMs and cloud: virtual or cloud cores times coefficient.
Cloud / BYOL
InfoScale may run in the cloud environments listed in its Software Compatibility Guide. Cloud use “accumulates” with on-premises use against the licensed Use Levels, and the customer must secure the cloud provider’s cooperation with Arctera audits or supply the provider’s usage reports.[1] The same accumulation rule applies to container orchestrators. Customers must report the cores deployed in containers when Arctera asks.[1] InfoScale for Kubernetes requires core counts both on premises and in the cloud, using the Core Plus method.[2] Catalog: InfoScale cloud and container use accumulates.
Licence keys
InfoScale can run without a key at first. For the first 60 days after installation it may run without a Standard License Key. After that, keyless use may continue “only if You obtain, install and use the Arctera License Management Service (“LMS”) on a Server to track Your keyless license”. LMS is included in the licence.[1] Customers may switch to a Standard License Key at any time. That key is a string assigned by the Arctera Enterprise Licensing System (ELS), obtained with the serial number on the License Instrument.[1] Without a License Instrument the customer is not authorized to use the software.[1] Catalog: InfoScale runs 60 days without a key, then needs LMS or a Standard License Key.
InfoScale for Kubernetes works differently. Its trial runs keyless for 60 days without support. Continued use then requires buying a subscription, installing InfoScale Operations Manager (IOM) and entering the Standard License Key there.[2] Catalog: InfoScale for Kubernetes trial is keyless for 60 days.
Disaster recovery and subscriptions
InfoScale Foundation and Storage customers with a current maintenance contract may install the software on cold DR equipment. It may be used there for up to 30 Testing Days of failover testing in any 12 months, and for up to 90 consecutive days of production after a Disaster, not at the same time as normal production. The DR copy must be the same version, and the right ends when maintenance lapses.[1] A subscription licence “shall terminate at the end of the applicable license term or period”.[1] Subscriptions are reviewed once a year. Excess usage is paid pro-rata, and the quantity cannot be reduced during the term.[5] Catalog: Cold DR copies require current support.
Programs
- Maintenance must cover 100% of InfoScale licences. Usage reports are automated, or manual reports are due once a year at least 90 days before the subscription anniversary.[4]
- Under the Arctera Product Life Cycle Policy, each release has a Primary Phase of typically 3 to 4 years from GA, then Extended and Sustaining phases. Essential Support is required throughout.[6]
Out of scope
This article does not cover InfoScale Operations Manager, Application Mobility Service, InfoScale Access appliances or the Arctera File System SDK terms in the PUR. Archived Storage Foundation and Cluster Server EULAs are listed on infoscale.com.[7] Common contract, audit and renewal rules are in Arctera licensing.