Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cyberun.cloud/llms.txt

Use this file to discover all available pages before exploring further.

Platform is the deployment and engineering surface of Cyberun. Cloud is the product users sign in to; Platform is what runs underneath it. It is also what gets deployed when an organisation runs Cyberun inside its own datacenter, VPC, or air-gapped environment. This tab is for the operators and partners who deploy, operate, or integrate against the platform. End-user product documentation lives in the Cloud tab.

​
What the platform gives you

  • One API surface across every environment. The same REST endpoints and the same agent gateway show up whether the deployment runs on bare metal, a hyperscaler, or in an air-gapped lab. Clients written against the API don’t care which.
  • Identity that fits the organisation. A self-hosted OIDC issuer signs the platform’s tokens. External identity providers can federate in alongside it.
  • Agents you can place anywhere. The agent runtime connects outbound to a gateway and runs tool workflows (ComfyUI, Nerfstudio). Same binary across operating systems and execution modes.
  • A license that gates capabilities deliberately. Identity surfaces, workload features, and capacity quotas are entries in the license file you own and refresh — see Feature catalog.
  • A path to multi-site. When a deployment needs to span sites, the platform scales horizontally — more clusters joined into one mesh, identity and routing extend, no service rewrites.
Pick by the question you arrived with.

Architecture

The components a deployment exposes, and how clients reach them.

Requirements

What you need to provide — database, object store, cache, message bus, agent-host expectations.

Deployment patterns

Sovereign on-prem, hyperscaler escape, mixed control plane, single-site managed. Criteria for picking.

Identity

Credential families, the OIDC issuer, external IdP options.

License administration

What the license carries, expiry behavior, renewal, air-gapped outline.

Feature catalog

Every deployment-toggleable capability, its license key, and the enterprise-template default.

Agents

Install agents on Linux, macOS, Windows. Service locations, log paths, all flags.

Connections and tunnels

How agents reach the gateway and how the gateway proxies per-agent services.

Observability

Logging, OpenTelemetry traces, streamed task events.

Upgrades

Release streams, version policy, license interaction across majors.

Self-host

What’s public, what’s partner-led today, what to bring to the first conversation.

API reference

The full HTTP surface, generated from the OpenAPI spec.

​
In development

Some operator material is being prepared for public release. Until each page lands, the content is partner-led — see Self-host → In development for the current list and reach out for the partner reference. Public production-sizing reference numbers, an air-gapped runbook, a backup/DR guide, and external-IdP integration recipes are the next pages slated to land.