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

# Computes

> What a compute is and what Expanse supports.

A **compute** is any environment running `expanse-daemon`. A SLURM cluster, a Nomad cluster, and a Kubernetes cluster are all the same thing from Expanse's point of view: one row on the Compute page in the Console.

## Supported environments

| Type                           | Where the daemon runs                                                                                                                                                                                                             |
| ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `slurm`                        | The controller node of a SLURM cluster. Every job (`sbatch`, `srun`, `salloc`) is captured automatically via scheduler prolog/epilog hooks.                                                                                       |
| [`nomad`](/integrations/nomad) | A Nomad client node with access to the Nomad HTTP API. Captures allocation and task lifecycle telemetry automatically.                                                                                                            |
| `kubernetes`                   | Installed via Helm. Watches all non-system namespaces by default (or a configured namespace list) and captures every pod in the watched namespaces, including pods owned by Volcano, Kueue, Argo Workflows, Flux, Ray, and Flyte. |

## Registering a compute

```bash theme={"dark"}
expanse compute register
```

The command asks what kind of compute you're registering and prints the install command or bootstrap snippet to run on the target. The compute appears in the Console within a minute of the daemon starting.

For the full registration walkthrough, see the [Quickstart](/quickstart).

## Compute states

Every compute is in one of these states:

| State      | Meaning                                                              |
| ---------- | -------------------------------------------------------------------- |
| `pending`  | Registered but the daemon has not connected yet.                     |
| `active`   | Daemon is heartbeating.                                              |
| `degraded` | Heartbeat has been missing for a short window.                       |
| `offline`  | Heartbeat has been missing long enough to consider the compute gone. |
| `revoked`  | The compute key was revoked or the compute was removed.              |

Historical data for an offline or revoked compute stays queryable in the Console.