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

# NeoChamber documentation

> Turn a GPU fleet into a cloud business you own — sold under your brand, deployed your way.

NeoChamber is the software layer between GPU hardware and the customers renting
it. You already own the hard part — power, facilities, and the GPUs. NeoChamber
adds the fleet observability, multi-tenancy, and commerce surface that turns
that hardware into a cloud business, sold under **your** brand.

There are two ways to read these docs, depending on which side of the platform
you are on.

<CardGroup cols={2}>
  <Card title="I own GPUs" icon="server" href="/operators/overview">
    Set up a private, branded, multi-tenant GPU cloud: choose a deployment
    model, enroll your fleet, create tenants, and run it day to day.
  </Card>

  <Card title="I rent GPUs" icon="user" href="/customers/overview">
    Get your account, rent whole nodes from your provider's pool, and watch
    every GPU you pay for with live telemetry and logs.
  </Card>
</CardGroup>

## What the platform actually does today

<CardGroup cols={2}>
  <Card title="Fleet observability" icon="chart-line">
    GPU utilization, VRAM, thermals, power, ECC and Xid faults from every node
    at 15-second resolution — plus per-node log search with fault highlighting.
  </Card>

  <Card title="Hard multi-tenancy" icon="shield-check">
    Customer tenants isolated server-side, with two automated leak tests running
    in CI on every change.
  </Card>

  <Card title="Self-service rental" icon="cart-shopping">
    Customers rent whole nodes by GPU model from your live availability and
    release them when they are done.
  </Card>

  <Card title="Your brand, your metal" icon="palette">
    Your name and logo on your console, deployed managed, into your own cloud
    account, or on your own hardware.
  </Card>
</CardGroup>

## Three consoles, one platform

| Console        | Path       | Who signs in                                                            |
| -------------- | ---------- | ----------------------------------------------------------------------- |
| **Operator**   | `/admin`   | You — one independent datacenter, its fleet, tenants, and capacity pool |
| **Customer**   | `/console` | Your customers — only the machines their tenant rents                   |
| **Chamber HQ** | `/chamber` | The deployment's super admin, across operators                          |

Neither of the first two can reach past its own line. That boundary is enforced
on the server from the session, never from anything the browser sends — see
[Isolation](/platform/isolation).

<Note>
  Everything in these docs is labeled for what it is. Features marked **LIVE** are
  running in production today. Features marked **SOON** or **ROADMAP** appear in
  the product as visible, disabled previews — never a silent gap. See
  [How we label things](/platform/conventions).
</Note>

## Where to go next

<CardGroup cols={3}>
  <Card title="How it works" icon="diagram-project" href="/platform/how-it-works">
    Operators, tenants, nodes, and agents — the four nouns everything else is built from.
  </Card>

  <Card title="Deployment models" icon="cloud" href="/platform/deployment-models">
    Managed, sovereign, or on-prem — and what changes between them.
  </Card>

  <Card title="Data residency" icon="location-dot" href="/platform/data-residency">
    Component by component, where every byte lives.
  </Card>
</CardGroup>