> ## 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.

# Cyberun Platform

> The deployment and engineering surface that underpins Cyberun Cloud. Architecture, dependencies, identity, license, agents, operations.

**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](/cloud/overview) 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](/platform/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.

## Where to read next

Pick by the question you arrived with.

<CardGroup cols={2}>
  <Card title="Architecture" icon="diagram-project" href="/platform/architecture">
    The components a deployment exposes, and how clients reach
    them.
  </Card>

  <Card title="Requirements" icon="list-checks" href="/platform/requirements">
    What you need to provide — database, object store, cache,
    message bus, agent-host expectations.
  </Card>

  <Card title="Deployment patterns" icon="layer-group" href="/platform/deployment-patterns">
    Sovereign on-prem, hyperscaler escape, mixed control plane,
    single-site managed. Criteria for picking.
  </Card>

  <Card title="Identity" icon="id-badge" href="/platform/identity">
    Credential families, the OIDC issuer, external IdP options.
  </Card>

  <Card title="License administration" icon="file-shield" href="/platform/license">
    What the license carries, expiry behavior, renewal,
    air-gapped outline.
  </Card>

  <Card title="Feature catalog" icon="toggle-right" href="/platform/feature-catalog">
    Every deployment-toggleable capability, its license key,
    and the enterprise-template default.
  </Card>

  <Card title="Agents" icon="microchip" href="/platform/agents">
    Install agents on Linux, macOS, Windows. Service locations,
    log paths, all flags.
  </Card>

  <Card title="Connections and tunnels" icon="route" href="/platform/gateway-and-tunnels">
    How agents reach the gateway and how the gateway proxies
    per-agent services.
  </Card>

  <Card title="Observability" icon="activity" href="/platform/observability">
    Logging, OpenTelemetry traces, streamed task events.
  </Card>

  <Card title="Upgrades" icon="arrow-up-circle" href="/platform/upgrades">
    Release streams, version policy, license interaction across
    majors.
  </Card>

  <Card title="Self-host" icon="building" href="/platform/self-host">
    What's public, what's partner-led today, what to bring to
    the first conversation.
  </Card>

  <Card title="API reference" icon="terminal" href="/api-reference/introduction">
    The full HTTP surface, generated from the OpenAPI spec.
  </Card>
</CardGroup>

## 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](/platform/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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.