Licensing
LabPod starts without a signed license file. In that state it resolves to a built-in 90-day trial:
| Trial field | Value |
|---|---|
| Users | root admin plus one non-root user |
| GPUs | Uncapped for evaluation |
| Fractional GPU | Enabled when the host supports HAMi or MIG |
| Resource limits | Enabled when the host supports cgroup v2 |
| Term | 90 days from the database first-run timestamp |
When the trial expires, LabPod does not lock you out or interrupt work in progress - login and already-running work are not abruptly cut off. Some actions become restricted until a signed license is installed. Install a license before the trial ends to avoid any disruption; contact LabPod support to get one.
Install a license
Section titled “Install a license”The local CLI handles request-code generation, verification, installation, and status display:
sudo labpod admin license showsudo labpod admin license requestsudo labpod admin license verify ./license.licsudo labpod admin license install ./license.lic# Run these as rootlabpod admin license showlabpod admin license requestlabpod admin license verify ./license.liclabpod admin license install ./license.licInstalled license files are stored at LABPOD_LICENSE_PATH, which defaults to
/var/lib/labpod/license.lic.
Feature gates
Section titled “Feature gates”Runtime toggles combine three checks:
- The license or trial permits the feature.
- The host can actually support it.
- The operator has the runtime setting enabled.
For example, fractional GPU is effective only when the entitlement permits it, the host has
HAMi-core configured or MIG slices available, and gpu_sharing_enabled is on.