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

# Deployment models

> Managed, sovereign, or on-prem — and exactly what changes between them.

Choose this first: it determines where your data lives and who operates the
stack. Everything else in the operator guide is the same in all three.

<CardGroup cols={3}>
  <Card title="Managed" icon="bolt">
    **LIVE** · Fastest launch · NeoChamber operates
  </Card>

  <Card title="Sovereign / dedicated" icon="building-lock">
    **LIVE** · Your cloud account · your jurisdiction
  </Card>

  <Card title="On-prem / air-gapped" icon="server">
    **ROADMAP** · Your metal · no public cloud
  </Card>
</CardGroup>

## Managed <Badge color="green" size="sm">LIVE</Badge>

NeoChamber deploys, hosts, and operates the full stack. You get an operator
invite and start enrolling servers the same day.

* Zero infrastructure on your side beyond the GPU servers themselves
* Pure 5% revenue share — no license, no per-seat fees, no integration charges
* NeoChamber runs upgrades, backups, and the operational drills

## Sovereign / dedicated <Badge color="green" size="sm">LIVE</Badge>

The entire platform deploys into **your own cloud account and region**, from
Terraform and documented setup. Control data, metrics, and logs never leave your
account or your chosen jurisdiction.

* Every cloud resource defined in Terraform; the console is code
* Region-pinned data stores, and **no shared control plane**
* Operated by NeoChamber's forward-deployed engineers, or by your own team from
  the runbook

<Note>
  In a sovereign deployment the Chamber HQ console runs inside *your* deployment.
  That matters for one specific setting — the platform brand name your customers
  see — which is held by whoever owns its super-admin account. See
  [Branding](/operators/branding).
</Note>

## On-prem / air-gapped <Badge color="orange" size="sm">ROADMAP</Badge>

The architecture is built for this: agents speak plain HTTPS to one ingest API
that owns all store access, so the managed metric and log backends swap for
self-hosted equivalents behind the same contract — **agents never change**.

* Designed-in backend swap (self-hosted metrics and log stores)
* Outbound-443-only agents already fit strict egress policies
* Scoping now with design partners — [talk to us](mailto:charles@usechamber.com)

## What changes, and what does not

|                       | Managed                 | Sovereign                 | On-prem       |
| --------------------- | ----------------------- | ------------------------- | ------------- |
| Console and APIs      | NeoChamber's deployment | Your cloud account        | Your hardware |
| Telemetry and logs    | NeoChamber's deployment | Your account, your region | Your hardware |
| Who operates it       | NeoChamber              | You or NeoChamber         | You           |
| Agent install command | Identical               | Identical                 | Identical     |
| Isolation guarantees  | Identical               | Identical                 | Identical     |
| Commercial terms      | 5% revenue share        | 5% revenue share          | Talk to us    |

The operator and customer workflows are byte-for-byte the same across models.
Only the address of your console and the owner of the infrastructure change.