Shipping every week, on every device

A technician asks a question by voice mid-procedure. The answer is grounded in the published steps and the reference PDFs attached to the guide — not the open internet — hardened against prompt injection and spoken back through text-to-speech.

A Fail verdict opens the camera; the shot is stamped and attached to the step, then appears in the inspection PDF. An aim-before-you-shoot viewfinder is in device test.

Pairing that survives restart, voice verdicts from a fixed grammar, reference PDFs, anchored holograms, and Remote Assist calls with see-through camera video into Teams.

One verdict bar on Quest 3 and iPad: Previous · Pass · Fail · Skip · Next. Fail asks for a comment and a photo (and up to 60 s of video on iPad) and raises an Issue with a priority. Skip hides itself on strictly ordered procedures.

Safety mode locks Next until the step has a verdict and stops the sidebar from jumping ahead. Authors choose ordered or free step order per guide and configure which statuses a step accepts.

The PDF carries every verdict, comment, priority, photo thumbnail, both signatures and your tenant logo. Admins drill from Reports into sessions, issues and photos; Insights shows engagement over time.

Operator and a second technician or supervisor sign on the iPad with a finger or Apple Pencil, printed names alongside; the signatures render on the PDF.

Assign a procedure to a site and an asset, move it OPEN → IN PROGRESS → CLOSED or FAILED, attach notes and photos, and read KPIs. Mirrored to the headset API.

Attach OEM PDFs at guide level once; they open mid-step on Quest 3, HoloLens 2, iPad and the web, and are frozen into each published version.

Next, back, repeat, go to step N, Pass, Fail, Skip, dictate the issue, take photo — all by voice, gloves on.

The expert marks up the operator's view in Teams, screenshots, pastes it into the GPYB console — and it appears in front of the technician within seconds.

Pairing and operator login, guide playback with images, video, 3D and narration, reference PDFs, verdicts with photo and video evidence, sign-off, Work Orders tab, tenant logo.

Your logo, name and primary colour across the web app, register page, PDFs and iPad. Admins invite users with single-use links. The web app installs as a PWA.

Nested folders, grid and list views, rename and move, video poster frames, and Unity packages as first-class assets.

Sessions bound to the request tenant, abandoned sessions closed, CSV formula-injection neutralised, uniform 404s on file endpoints.

Tenant isolation end to end, tenants.gpyb.ai with TOTP two-factor and an audit log for every superadmin action, and a license server that gates SDK boots.

Direct calls into a Teams user over ACS federation, Invite (the backend creates a Teams meeting and emails the expert a join link), or a stored meeting link — per tenant, with contacts that can include external guests.

Passthrough plus holograms captured from the compositor and sent into the Teams call so the expert sees the real part and the guidance on it.

@gpyb/portal-sdk with a clone-and-brand Next.js template, the com.gpyb.sdk.xr Unity package, @gpyb/ipad-sdk and shared @gpyb/api-types. The first external tenant runs its own branded portal, Quest and iPad apps on them.

Deep Industrial Blue and Safety Orange tokens, Storybook, and an accessibility baseline across the web app.