Licensing

GraphLab Boot is licensed per device and managed through the GraphLab Portal.

---

Portal areas: Licenses, Hardware, and Shop

The portal splits licensing into three top-level areas:

Area	Purpose
Licenses	Read-only inventory: device slots, platform + maintenance status, and all screen licenses.
Hardware	Owned platforms and display integrations; request a custom SoM not in the catalog.
Shop	Request-only ordering: device licenses, platform tiers (evaluation or commercial), new display integrations, and maintenance renewals.

See also Hardware and Shop for area-specific workflows.

License model

GraphLab Boot uses a three-tier portal licensing model plus per-device runtime licenses. Each tier unlocks the next step in the portal workflow.

Tier	What it covers	Portal action
Platform license	The SoM / silicon family (for example i.MX8MP). One entitlement per company per platform.	Order in Shop (evaluation 30 days or commercial). Custom SoM via Hardware → Request platform.
Display license	A display pipeline (interface, resolution, refresh). Many per company — each order creates a new integration.	Order in Shop → Display integration after the platform license is active.
Device license	Runtime entitlement for one physical device UUID. Two products: GraphLab Boot (commercial) and GraphLab Boot - Development (evaluation).	Request each product in Shop → Devices; company pool under Licenses; allocate to projects by environment.

Software maintenance (optional, per commercial platform license) covers ongoing platform software updates. Request renewal from Shop; GraphLab activates the maintenance period after review.

Evaluation vs commercial tiers

Platform and display licenses each have a tier: evaluation (development) or commercial (production). You order both tiers in Shop; the read-only status appears under Licenses.

Tier	Platform	Display integration
Evaluation	30-day evaluation from Shop (start evaluation). Expires automatically; GraphLab can extend. For bring-up and testing.	Order in Shop; tune porch timings on Hardware while active.
Commercial	Request commercial or upgrade from evaluation. Does not expire once active.	Upgrade from evaluation in Shop — existing config is kept and locked.

Porch timings and display settings

Porch timings (panel timing profile for the VPS / initstub.bin) belong to the display integration, not the boot config editor.

• Evaluation — edit porch timings under Hardware on each active display integration.
• Commercial — porch timings are fixed at upgrade time; only GraphLab can change them afterward.
• Boot config create/edit shows porch timings as read-only when the display integration is commercial.

Before upgrading a display to commercial, finalize porch timings in Hardware. The Shop upgrade page summarizes your configuration and explains the lock.

Device license products

Device licenses are sold as two separate products. They do not expire once granted. The Licenses page shows total slots, how many are assigned to projects, how many are unassigned, and how many are consumed by provisioned devices.

Product	Tier	Used by
GraphLab Boot	Commercial	Production projects only
GraphLab Boot - Development	Evaluation	Development projects only (including the onboarding evaluation workspace)

Project environment and hardware binding

Each project has an environment (Development or Production) chosen at creation. That environment controls which device license product the project may allocate and which platform/display tiers groups may use:

Environment	Device licenses	Platform / display / boot firmware
Development	GraphLab Boot - Development only	Evaluation or commercial
Production	GraphLab Boot only	Commercial only

Hardware is bound at the group level inside a project:

• Platform (SoM) — must match an active company platform license allowed for the project environment.
• Display integration — must match an active display license on that platform and tier.

Devices inherit platform, display, and default boot config from their group. See Projects and Groups.

GraphLab Boot Configs

Boot configs (custom initstub.bin builds with splash, boot UI, and status text) are also bound to hardware:

• You create a config for a specific platform + display license.
• Screen resolution and refresh rate come from the display license, not from the config editor.
• Porch timings come from the display integration (editable on evaluation via Hardware; locked on commercial). The MMIO init sequence is embedded in the built binary.
• A config can only be assigned as a group default (or device override) when it matches the group’s platform and display.

Typical portal workflow

1. Shop — buy platform evaluation (or request commercial) and order display integration(s).
2. Licenses — confirm entitlements are active after GraphLab approval.
3. Hardware — tune porch timings during evaluation if needed.
4. Create a project with Development or Production environment. See Projects.
5. Request GraphLab Boot and/or GraphLab Boot - Development device slots in Shop; allocate from your company pool to matching projects.
6. Create hardware groups and optionally assign a GraphLab Boot Config per group. See Groups.
7. Register devices in a group and download or CLI-provision license.bin. See Devices.
8. Shop — upgrade platform and display to commercial before production; renew maintenance as needed.

Per-device runtime license

Each device that runs GraphLab Boot still needs its own signed license.bin. The blob is bound to the device hardware UUID and cannot be transferred between devices.

Provisioning

When a device starts without a valid license, GraphLab Boot enters provisioning mode.

During startup a provisioning QR code is displayed on the screen. This QR code can be scanned and registered through the GraphLab Portal to generate a license for that specific device.

For developer workflows that provision a device directly from a workstation, see the CLI Provisioning guide.

Manual license download (without automatic provisioning)

If you do not use the automatic CLI provisioning flow, you can download the license file manually from the device page in the Portal.

1. Open Devices in the Portal and select your device.
2. Click Download license file on the device details page.
3. Save the downloaded binary as license.bin.
4. Copy license.bin to the device boot medium (for example the FAT boot partition).
5. Reboot the device and verify that the watermark is gone.

You can also click Copy provision URL on the same page to fetch the license through your own tooling. The endpoint returns the binary payload directly.

Until a valid license is installed, the system continues to boot but a visible watermark remains on the display.

Portal

The GraphLab Portal is used for:

• Licenses — read-only entitlement inventory
• Hardware — owned platforms/displays; evaluation porch timing tuning
• Shop — platform, display, device, and maintenance requests
• Group hardware binding (platform + display per group)
• GraphLab Boot Config library (per licensed display)
• Device registration and license generation

Company licensing

Device licenses live in your company pool as GraphLab Boot or GraphLab Boot - Development products. Assign capacity to projects that match each product’s environment, then provision individual devices from that allocation. New companies start without platform, display, or device licenses until GraphLab approves requests or assigns capacity during onboarding.

Open Licenses for a read-only overview of entitlements and maintenance status. Use Shop to request new licenses or upgrades, and Hardware for custom SoM requests.

Contact