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

# Running the Container

> Getting our container up-and-running takes minutes.

Running Datalab's containers requires **a Google Cloud service account key** to pull the container image.

If the terms of your agreement require a license, we'll also provide **a license key.**

# License-enabled containers

Copy your license key, download the service account key, and [run the script in this Github repository to get up-and-running](https://github.com/datalab-to/datalab-on-prem):

```shellscript theme={null}
export DATALAB_LICENSE_KEY=your-license-key
export SERVICE_ACCOUNT_KEY_FILE=path/to/key.json
./run-datalab-inference-container.sh
```

# Kubernetes deployment (Helm)

A Helm chart is available for deploying the container on Kubernetes clusters. Contact [support@datalab.to](mailto:support@datalab.to) to receive the chart and values reference for your deployment.

# Fully-airgapped containers

A license key is not required to run a fully-airgapped container. If the terms of your agreement require a fully-airgapped container, we will provide:

* Access to private registries that contain those images.
* A Google Cloud service account key to pull images.
* Directions for how to run the container.

# [www.datalab.to](http://www.datalab.to) must be reachable

Our on-prem license requires that [https://www.datalab.to](https://www.datalab.to) is reachable in order to:

1. Activate and register your license with our servers.
2. Send usage metrics.

# Usage data sent to Datalab

License activation and usage heartbeats **do not send private data to Datalab.**

Our intent is to ensure compliance with our license and to easily support customers when they run into problems.

The container sends the following to our servers:

1. On container startup we activate your license. In that request, we send information about your hardware and OS available in `/proc` and `/sys` (in the container, not on your host).
2. At regular intervals we send usage heartbeats that contain:
   1. The # of successful/failed inference requests completed since the last heartbeat
   2. The # of inference requests submitted to the container over a recent time window

# I need a fully-airgapped deployment

We also support fully-airgapped deployments that do not require a license. [Get started by filling out this form.](https://www.datalab.to/contact)

Please reach out to us at [support@datalab.to](mailto:support@datalab.to) if you have questions.

## Hardware Requirements

| Container Type  | GPU Required | Minimum VRAM | Recommended Use                             |
| --------------- | ------------ | ------------ | ------------------------------------------- |
| `marker`        | Yes (CUDA)   | 24 GB        | Standard document conversion with Surya OCR |
| `chandra`       | Yes (CUDA)   | 80 GB        | Full Chandra VLM for highest accuracy       |
| `chandra-small` | Yes (CUDA)   | 16 GB        | Smaller Chandra variants (2B/4B models)     |

## Health Check

Verify your container is running:

```bash theme={null}
curl http://localhost:8000/health_check
```

Expected response:

```json theme={null}
{"status": "healthy"}
```

## Next Steps

<CardGroup cols={2}>
  <Card title="On-Prem API" icon="code" href="/docs/on-prem/api">
    API reference for the on-prem container image.
  </Card>

  <Card title="On-Prem Overview" icon="building" href="/docs/on-prem/overview">
    Compare open-source and paid on-prem deployment options.
  </Card>

  <Card title="Cloud Quickstart" icon="rocket" href="/docs/welcome/quickstart">
    Try the cloud-hosted API for quick evaluation.
  </Card>

  <Card title="Error Codes" icon="circle-exclamation" href="/platform/errors">
    Understand HTTP error codes and troubleshooting steps.
  </Card>
</CardGroup>