> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lyceum.technology/llms.txt
> Use this file to discover all available pages before exploring further.

# Lyceum Cloud

> Run Python, Docker, notebooks, and dedicated inference on managed GPU infrastructure

## Overview

Lyceum Cloud is a managed compute platform for running code and serving models on cloud GPUs. The dashboard, CLI, and REST API all expose the same underlying capabilities, organised around a few core building blocks.

<Card title="Quickstart" icon="rocket" href="/docs/quickstart" horizontal>
  Create an account, install the CLI or VS Code extension, and run your first job.
</Card>

## What you can do

<Columns cols={2}>
  <Card title="Serverless runs" icon="play" href="/docs/serverless/runs">
    Submit Python scripts, Docker images, or Docker Compose stacks. Pay per second of execution.
  </Card>

  <Card title="VM instances" icon="server" href="/docs/instances/vms">
    Provision long-lived GPU VMs with SSH access for interactive work and custom environments.
  </Card>

  <Card title="Dedicated inference" icon="microchip" href="/docs/inference/dedicated">
    Deploy any Hugging Face model to a dedicated GPU endpoint with autoscaling.
  </Card>

  <Card title="Object storage" icon="database" href="/docs/configuration/storage">
    Per-user S3-compatible bucket for inputs, outputs, and shared datasets.
  </Card>
</Columns>

## Ways to access the platform

<Columns cols={3}>
  <Card title="Dashboard" icon="window" href="https://dashboard.lyceum.technology">
    Web UI for everything: launching runs and VMs, deploying models, managing storage, billing, and API keys.
  </Card>

  <Card title="CLI" icon="terminal" href="/docs/quickstart">
    The `lyceum` command-line tool for runs, VMs, inference, and storage from your terminal.
  </Card>

  <Card title="REST API" icon="code" href="/api-reference/introduction">
    Programmatic access to every dashboard feature. OpenAI-compatible inference endpoints.
  </Card>
</Columns>

## Authentication

Every request to the platform is authenticated with a bearer token in the `Authorization` header. Two token types are supported:

* **API keys**, long-lived tokens prefixed `lk_`, scoped to one [organization](/docs/account/organizations) at creation. Created and managed in [API Keys](/docs/configuration/api-keys). Use these for CLI, scripts, and integrations.
* **JWT tokens**, short-lived tokens issued by the dashboard login flow. Use these for testing in the browser or API playground. JWT users pick which org to act on with the `X-Org-Slug` header, or fall back to their default org.

<Card title="Generate an API key" icon="key" href="/docs/configuration/api-keys">
  Create your first API key from the dashboard.
</Card>