Skip to main content

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.

A compute is any environment running expanse-daemon. A SLURM login node, a Nomad cluster, a Kubernetes namespace, a Databricks workspace, a YARN cluster, a cloud batch project, a SkyPilot-managed VM, and a standalone cloud box are all the same thing from Expanse’s point of view: one row on the Compute page in the Console.

​
Supported environments

TypeWhere the daemon runs
slurmThe login node of a SLURM cluster, including Slinky-managed SLURM on Kubernetes. Every job submitted with sbatch is captured automatically.
nomadA Nomad client node with access to the Nomad HTTP API. Captures allocation and task lifecycle telemetry automatically.
skypilotThe VM or cluster created by the SkyPilot task. Captures the task’s run command via expanse run --.
standaloneAny cloud VM, workstation, or dev box. Captures commands explicitly wrapped with expanse run --.
k8sInstalled via Helm into the namespace where workloads run. Captures every pod in that namespace, including pods owned by Volcano, Kueue, Argo Workflows, Flux, Ray, and Flyte.
databricksThe Databricks workspace or job bootstrap used for Databricks Jobs and Mosaic AI Training. Captures job runs from the driver before user code starts.
yarnThe edge, gateway, or ResourceManager-adjacent host for Apache Hadoop YARN clusters, including AWS EMR, Google Dataproc, Azure HDInsight, and Cloudera CDP. Captures applications submitted to YARN.
cloud-batchThe account, project, or workspace that owns managed batch and training jobs across AWS Batch, AWS SageMaker Training Jobs, Azure Batch, Azure ML Jobs, Google Batch, and Vertex AI Custom Training. Captures submitted jobs through the managed-service control plane.

​
Registering a compute

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.

​
Compute states

Every compute is in one of these states:
StateMeaning
pendingRegistered but the daemon has not connected yet.
activeDaemon is heartbeating.
degradedHeartbeat has been missing for a short window.
offlineHeartbeat has been missing long enough to consider the compute gone.
revokedThe compute key was revoked or the compute was removed.
Historical data for an offline or revoked compute stays queryable in the Console.