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

# Data Planes

> The compute locations where Domino runs your workloads, one per region or cloud, selected by the hardware tier you pick when you launch a workspace, job, app, or endpoint.

A Data Plane is a compute location where Domino runs your workloads. A single Domino deployment can have more than one Data Plane, in different regions or clouds, so you can run work close to the data it needs or inside a region or cloud that your requirements dictate.

## How it works

* **Hardware tier**: the compute configuration you pick when you launch a workload. Each hardware tier is attached to one Data Plane, so choosing a tier also chooses where the workload runs.
* **Control Plane**: the Domino services and user interface that schedule and manage work across every Data Plane.

```mermaid theme={null}
%%{init: {"flowchart": {"wrappingWidth": 400}}}%%
flowchart TB
  W["You launch a workspace,<br/>job, app, or endpoint"] --> CP["Control Plane<br/>schedules and manages work"]
  CP -->|"tier in the local<br/>Data Plane"| L
  CP -->|"tier in a remote<br/>Data Plane"| R
  subgraph DP["Data Planes"]
    L["Local<br/>namespace in the<br/>Control Plane cluster"]
    R["Remote<br/>separate Kubernetes cluster in<br/>another region, cloud, or on-premises"]
  end
  DP ~~~ spacer[" "]
  style spacer fill:none,stroke:none
```

Data might be available only in certain Data Planes, because of geographic access restrictions or the cost of moving data between data centers. Your Domino administrator configures the Data Planes and hardware tiers, and associates external data volumes (EDVs) with the Data Planes that can reach them.

## Local and remote Data Planes

* A **local Data Plane** is a namespace within the same Kubernetes cluster as the Domino Control Plane, often called the `compute` namespace.
* A **remote Data Plane** is a namespace in a separate Kubernetes cluster from the Control Plane.

[Starburst and Trino data sources](/cloud/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-starburst-trino) are available only in the local Data Plane; every other type of data source works in both. Datasets are available in remote Data Planes that an administrator has configured for them, but [Domino CLI](/cloud/reference/cli/install-the-cli) access to Datasets works only in the local Data Plane.

For large data sets, EDVs are the primary way to access data across Data Planes, because they carry a first-class notion of data locality. Mount the EDVs that are configured for the Data Plane your execution runs in.

## Hybrid deployments

A deployment whose Data Planes span multiple clouds, regions, or on-premises infrastructure runs as Domino Nexus: remote Data Planes attached to a single Control Plane. For the architecture, see [Nexus hybrid architecture](/cloud/admin/architecture-and-deployment/architecture/nexus-hybrid-architecture).

## Use a Data Plane

Launch a [workspace](/cloud/platform-capabilities/core-concepts/workspaces/launch-a-workspace), [job](/cloud/platform-capabilities/core-concepts/jobs), [app](/cloud/platform-capabilities/features/apps), or [endpoint](/cloud/platform-capabilities/features/model-deployment) with a hardware tier from the Data Plane you need. In a hybrid deployment, the launch dialog groups hardware tiers by Data Plane, and the `Local` group runs the workload in the Control Plane cluster.

<Frame>
  <img src="https://mintcdn.com/dominodatalab-e871cec4/bDC0dBpHGmhipTiA/images/data-planes/launch-workspace-hardware-tiers.png?fit=max&auto=format&n=bDC0dBpHGmhipTiA&q=85&s=f4cf40d635e839ab3fde772805e07de1" alt="The Launch New Workspace dialog showing the hardware tier selector, with tiers grouped by Data Plane: CLOUD / US-EAST, CLOUD / US-WEST, CLOUD / EMEA, and ON PREM / EUROPE." width="1032" height="950" data-path="images/data-planes/launch-workspace-hardware-tiers.png" />
</Frame>

You can also [mount EDVs](/cloud/platform-capabilities/core-concepts/data/external-volumes/use-a-mounted-volume) that are configured for specific Data Planes, and launch [compute clusters](/cloud/platform-capabilities/features/compute-clusters-hpc) alongside your executions.

## Related

* [External data volumes](/cloud/platform-capabilities/core-concepts/data/external-volumes/index)
* [Nexus hybrid architecture](/cloud/admin/architecture-and-deployment/architecture/nexus-hybrid-architecture)
* [Manage Data Planes](/cloud/admin/platform-configuration/manage-data-planes) for administrators
* [Deployment options](/cloud/platform-overview/deployment-options)


## Related topics

- [Datasets administration](/cloud/admin/data-administration/datasets.md)
- [Glossary](/cloud/reference/glossary.md)
- [Manage Data Planes](/cloud/admin/platform-configuration/manage-data-planes/index.md)
- [Archive a Data Plane](/cloud/admin/platform-configuration/manage-data-planes/archive-data-plane.md)