Subscription units
In SHIP-HATS, subscription units define how resources are allocated for each tool in a subscription.
Depending on the tool, a unit can represent:
- user licences
- devices
- applications
- code analysis capacity
- service instances
The unit type determines how resources are counted and provisioned.
Subscription unit types
| Tool | Unit type | What it means |
|---|---|---|
| GitLab Ultimate | User licence | One licence per user |
| Atlassian (Jira & Confluence) | User licence | One licence per user |
| Atlassian Dedicated Site | Instance | One dedicated site |
| Sonatype (Nexus Repo & Nexus IQ) | User licence | One licence per user |
| Fortify on Demand | Application | One application scanned |
| Jira Service Management | Agent licence | One licence per agent |
| SonarQube Enterprise | LOC blocks | Blocks of lines of code that can be scanned |
| pCloudy Dedicated | Device | Dedicated Android or iOS device |
How units are used
- For tools that use user licences, each unit represents one licence assigned to a user
- For tools that use capacity or instances, units represent the amount of resource allocated
For example:
- 10 GitLab units = 10 users
- 1 Atlassian Dedicated Site unit = 1 site
- 100k LOC units = code analysis capacity
To learn how licences are assigned, see Provision licences to users.
Cost considerations
Some tools or variants may be provided at no cost, depending on the offering:
- pCloudy (Shared devices) — available without subscription units
- SonarQube Community Edition — available without subscription units
These offerings:
- do not consume subscription units
- may have usage or feature limitations compared to paid options
See SHIP-HATS pricing and billing model for details.
