Application Package Licensing

Understand how Application Package licensing works in DeGirum AI Hub, including automatic license fetch, Workspace eligibility, and billing based on peak active usage.

Application Package licensing in AI Hub is designed to be automatic and Workspace-based. When you run an Application Package on a device, the package uses the Workspace Token installed on that device to fetch and activate a license, without any manual license keys. This page walks through the requirements to run an Application Package, what happens at launch, and how active licenses are counted for billing.

Key ideas

• Licenses are Workspace-scoped. Each license is associated with a specific Workspace.

• Tokens drive licensing. The device running an Application Package must have a Workspace Token installed for the Workspace that the package is licensed under.

• No manual license keys. Licenses are fetched and activated automatically when the Application Package runs.

• Billing uses peak active usage. A Workspace is billed based on the highest number of licenses activated (or renewed) during a billing period.

Workspace eligibility for licensing

By default:

• Pro Workspaces can generate Application Package licenses.

• Enterprise Workspaces can generate Application Package licenses.

Exception:

• In some cases, Free Workspaces can be temporarily enabled to generate Application Package licenses during a trial period.

If a Workspace is not entitled (or not trial-enabled), devices using that Workspace Token cannot fetch licenses for Application Packages tied to that Workspace.

Requirements to run an Application Package on a device

To run an application package on a device, the user must:

1. Have access to the Application Package in AI Hub (typically through Workspace access and permissions).

2. Install a Workspace Token on the target device that belongs to the Workspace the Application Package is licensed under.

A simple way to think about it:

• The Application Package belongs to a Workspace.

• The device must use a token from that same Workspace.

What happens when you run an Application Package

When you launch an Application Package on a device:

1. The application Package reads the Workspace Token installed on that device.

2. It attempts to fetch and activate a license automatically from AI Hub for that Workspace.

3. If successful, the Application Package runs normally.

If the token is missing or not entitled

The Application Package cannot fetch a license if any of the following are true:

• No Workspace Token is installed on the device.

• The installed token belongs to a different Workspace than the one the Application Package is licensed under.

• The Workspace is not entitled (or not trial-enabled) for Application Package licensing.

• The token or user does not have permission in that Workspace to use Application Package licensing.

In these cases, the Application Package fails to start and the user sees an error indicating they do not have permission or the Workspace is not entitled.

Billing and counting active licenses

Licensing is billed at the Workspace level. During each billing period, AI Hub tracks:

• The maximum number of licenses that were activated or renewed for that Workspace.

That peak active count is what the Workspace is billed for during the period.

Example: peak active usage

If a Workspace had:

• 3 devices running the Application Package early in the month,

• later 7 devices running at the same time,

• then it dropped back to 2 devices,

the billing basis for that period is 7.

License renewal

Once an Application Package license is activated on a device, it is renewed periodically (approximately every 10 days) as long as the Application Package continues to run on that device using a valid Workspace Token. If the device can’t reach AI Hub during a renewal window, the Application Package may eventually fail to renew and raise a licensing error until connectivity (and permissions) are restored.

How licenses stop being counted

There is no manual deactivation step.

To stop a device from being counted:

• Do not run the Application Package on that device for a full billing cycle.

After a full billing cycle of inactivity, the device’s license is automatically no longer counted toward active usage.

Why licensing works this way

This design is intentional:

• No manual activation flow: Users do not need to generate keys or track which machine used which key.

• Fewer support issues: Tokens and automatic license fetch reduce misconfiguration and lost-key scenarios.

• Usage-based fairness over time: Billing reflects actual usage over time rather than licenses requested in the past.

• Scales cleanly: Teams can add or remove devices without extra license management steps.

Troubleshooting checklist

If you see a licensing error, check:

• Is the Workspace plan Pro or Enterprise, or a trial-enabled Free Workspace?

• Is a Workspace Token installed on the device?

• Is the token for the same Workspace as the Application Package?

• Does the token and user have permission in that Workspace to use Application Package licensing?