Pantacor Hub Docs

Appearance

The Hub Cloud ​

This guide describes the Pantacor Hub Cloud — the parts that make up the platform, and the web UI you manage it with: what each screen is for and what you can do there. If you want the underlying ideas first (what a device, object, or trail is), start with How the platform works. For the HTTP API the UI calls, see the Services pages and the API Reference.

The full picture ​

Before diving into screens, it helps to see the whole system and where you — the user — touch it:

YouBrowserthis web UIpvr CLIterminal, scripts, CICloud (Pantacor Hub)hub — web UI serverserves the interface you're reading aboutapi — the Pantahub APIaccounts · devices · trails · objectspvr — repo serviceclone/push device state like git reposDevicePantavisorcontainer runtime on thehardware — pantavisor.ioBSP + your app containerschecks inYou set the goal in the cloud — the device pulls its way there.Browser and CLI edit the same trail through the same API;the device fetches new revisions and reports progress whenever it is online.

The parts, and how you interact with each:

  • The device runs Pantavisor — a lightweight runtime that boots the hardware into a set of containers (the BSP plus your applications) described by a single versioned state. You normally never talk to the device directly: it connects out to the API, registers itself (onboarding), fetches new revisions, and reports status and logs.
  • The cloud is three cooperating services: the Pantahub API (api.…) that owns accounts, devices, trails and objects; the Hub web UI (hub.…) — the screens this guide describes; and the pvr repo service (pvr.…) that serves device states as clonable repositories. The UI and repo service are fronts — every action ends up as an API call, so anything you click can be automated with a token.
  • The pvr CLI is your terminal-side tool: it clones a device's state as files, lets you edit and add apps locally, and posts the result back as a new revision — plus claiming, logs and fleet listing. See Updating devices with pvr.

Day to day you choose the front that fits: the browser for inspecting devices, one-off changes, and managing tokens; the CLI for repeatable, scriptable work and CI. Both drive the same trail — the device doesn't care which one you used.

The Hub is organized into sections you reach from the main navigation:

SectionWhat it's for
DevicesBrowse and manage the devices in your account.
AppsManage the apps and content you deploy to devices.
TokensCreate API and device tokens for automation and provisioning.
SettingsEdit your profile and global configuration.

Getting a device into the Hub ​

New to Pantacor? Start at Start a new device — it walks you through downloading an image, flashing it, and connecting the device to Wi-Fi so it registers with your Hub account. When you want the full picture of the ways devices can join (claiming, auto-join tokens, TLS verification), read How onboarding works.

Signing in ​

The Hub uses OAuth2 / PKCE for authentication. You sign in at /login (or sign up at /signup); a verification step confirms your email before the account is active. Once signed in you land on your dashboard at /u.