Product map

Cyberun has one platform and several ways to use it. Use this chooser to figure out which to read next.

​

Quick chooser

​

The surfaces, briefly

​

Cyberun Cloud — the dashboard

You want: a team to run AI workflows on GPU agents, see results in a browser, and connect external tools through API keys or MCP. Read: Cloud → Overview The entry point for most users. Sign in, create a team, connect an agent, run a task.

​

Run workflows on your own GPU

You want: to connect your own GPU machine into your team’s pool, making the team’s nodes, models, and workflows available locally, alongside whatever ComfyUI ecosystem you already have. Read: Connect an agent, or the Cyberun CLI if you live in a terminal. The agent pairs to Cloud and your GPU joins the team’s pool; tasks you didn’t submit may land on your machine (with your consent), and tasks you did submit can prefer your machine.

​

Cyberun Studio — the creator workspace

You want: to make narrative video where the same character, location, and props stay consistent across many shots, with a project model built around stages, beats, and takes rather than isolated clips. Read: Studio → Overview Studio is in private alpha. The first workspace, VideoMaker, covers the full pipeline end-to-end: script → world and assets → shots and takes → music, voice, sound effects → exported cut. The Story → World → Assets → Shots → Dubbing structure mirrors how a small film crew divides labour. Shares sign-in and the team model with Cyberun Cloud.

​

MCP & Skill — driving Cyberun from AI clients

You want: your AI client (Claude Code, Cursor, Windsurf, Codex CLI, VS Code 1.101+) to list workflows, submit tasks, and fetch results — without you wiring HTTP calls by hand. Read: MCP → Overview Cyberun ships an MCP server in the cloud that speaks Streamable HTTP (the current MCP standard). The Cyberun skill is a separate, lightweight thing: a markdown file your agent loads once so it knows the platform’s conventions.

​

Cyberun CLI — the terminal

You want: to drive your team’s workflows from a shell — submit a task, poll it, download the result — or wire Cyberun into CI, without leaving the terminal. Read: Cloud → CLI The cyberun binary signs in with cyberun auth login, runs workflows with cyberun run, and can turn the machine into an agent with cyberun agent serve. It ships on its own release track — install it from the download page.

​

Platform — self-host, federation, deployment

You want: to run Cyberun inside your own datacenter, your VPC, an air-gapped lab, or a sovereign cloud. Or you’re integrating against the platform from your own code and need to understand identity, license, and the gateway protocol. Read: Platform → Overview and the API reference. Aimed at operators and partners — multi-site Kubernetes federation, OIDC identity, license administration, agent runtime protocol.