License Regions in TrueParser are used for license and usage-metrics data mapping.
A License Region identifies where an application’s license-linked usage metadata is stored and routed.
The License Regions screen
You can view all available regions supported by the platform under the License Regions section in your dashboard.
This screen serves as a central registry to review active regions and identify their official Region Codes. In the details view, you will find:
- License Region Name: The customer-friendly region label (for example,
United States, Europe).
- Region Code: The identifier (for example,
us-east-1, eu-central-1) used during application setup.
What license region controls
When creating machine client applications, you must assign one License Region.
Important: License Region is for license and usage-metrics data routing. It is not your parsed output storage location.
How regions bind to applications
During the Application Creation flow, you select an active License Region (as covered in the App Setup and Config):
- Creation selection: You select a predefined region from the dropdown.
- Usage routing: The control plane maps the app to the corresponding regional licensing and usage-metrics data store.
- Token claims: Access tokens include routing claims such as
licenseRegionCode and dbCode.
- Validation path: Backend services use these claims to validate usage and entitlement context.
What license region does not control
License Region does not define where parsed output files are stored.
Output storage is configured separately per application through storage settings, where you provide your own S3 destination.
Architectural invariants
- Selection is permanent: License Region is set at app creation and cannot be edited later on an active app.
- Changing region: If you need a different License Region, create a new app in the target region, configure its S3 storage, then migrate API traffic to the new credentials.
