Cloud control plane

The bridge from local graph to cloud GPU

Desktop and web share one trusted surface for cloud GPU nodes: authenticate, stage media on GPU volumes, enqueue jobs, stream progress and download artifacts, while your project and graph stay local.

01

Browser sign-in for desktop

In Preferences → Account, hit Sign in with browser. You approve the desktop in the browser; Triton then picks up a device Bearer from the live API. Only the token hash is stored server-side. That links billing and enables cloud AI nodes.

02

Direct volume uploads

Short-lived upload handles stream media straight to GPU volumes — not through your app server as base64.

03

Jobs + SSE progress

Queue on Postgres (pg-boss), poll status, or subscribe to server-sent progress for long GPU runs from desktop or web.

04

OpenAPI contract

Shared Zod schemas drive validation and docs. Desktop Pydantic models stay aligned with the same request and response shapes.

Get in early

Early Access builds go to the waitlist first, with the $99 Founder license until 1.0.