User-Based Licensing

Previously, Arm development tools and models have been provided with either Node-Locked (NL) or Floating (FL) licenses. Arm are now migrating to User-based Licensing. User-based Licensing is a new licensing implementation that provide two license management models:

Arm Cloud License Server

where your license entitlements are hosted on an Arm-managed server. Client user devices enable licenses using activation codes that are managed on the Arm User-based licensing portal by your administrator. If you have relatively few users, this is usually the easiest and fastest way of providing licenses for your users.

Local License Server

A local license server where your license entitlements are managed on a local machine managed by your administrator. This model is more suitable if you have many users or your users have no access to the internet.

UBL guides
If you are new to UBL, we recommend using the resources in this order:

Overview Guide

New Guide with Overview Content. Note contains topic for Node-Locked and Floating (FL) licenses.

View the guide

Administration Guide

The User-based Licensing Administration Guide provides in-depth information on how you can implement either licensing models.

View the guide

Licensing User Guide

The User-based Licensing User Guide provides Information on how users can license their Arm Development tools.

View the guide

Subscription Renewal for Arm Developer Store User-Based Licenses Guide

This guide explains what happens when a subscription renews, when you may need to take action, and what to expect if a subscription fails to renew, expires, or is cancelled.

View the guide
Frequently Asked Questions

What are the advantages of user-based licensing?

There are many advantages, including: simplified requirements capture, straightforward business model, improved performance for build and test, increased flexibility, the ability to exploit infrastructure and cloud deployments to the full and streamlined tools deployment. User-based licensing is designed to improve efficiency and effectiveness by giving users to the right tools at the right time.

How do I calculate how many success kits are needed?

It’s just the number of users you have. If you currently use our tools with floating licenses, we can provide a Python script that can analyse the diagnostic log created by your license server. This gives a comprehensive summary of your usage.

Which tools are compatible with user-based licensing?

User-based licensing needs new licensing technology to be integrated into our tools. Note that the following tools are not compatible with user-based licensing: any release of any tool made before April 2022, the existing compiler functional safety branches AC5.04, AC5.06, AC6.6 and MDK, PK51, DK251, PK166, ARTX-16.

Loading component...

Downloads

Loading component...

Loading component...