> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/operate/phase-1-provision-data-plane/overview.md).
# Overview
A **DataOS Data Plane** is the customer-controlled runtime where DataOS workloads execute and customer data is processed.
It provides the compute foundation for running data workloads close to your data sources and connects to the DataOS Control Plane for platform coordination, governance, metadata, and observability.
### What runs in the Data Plane
The Data Plane runs DataOS workloads such as:
* **Data Products**
* **Lakehouse workloads**
* **Workflow orchestration jobs**
* **Spark jobs**
* **Services and workers**
* **Data processing and transformation workloads**
* **Customer-facing or internal data applications**
These workloads connect to your approved data sources, process data, and serve outputs according to the policies and configurations you define through DataOS.
### Customer-controlled runtime
The Data Plane runs in a customer-controlled environment. You retain control over the infrastructure, network, identities, access policies, connected data sources, and data custody model.
Customer data processing happens inside this runtime boundary. Modern does not need to hold or store customer data for Data Plane workload execution.
### Connectivity at a glance
The Data Plane connects securely to the DataOS Control Plane to support workload coordination, metadata exchange, telemetry, and lifecycle management.
The connectivity pattern depends on the deployment model. For cloud-specific access paths, credentials, manifests, and operational commands, see the relevant deployment guide.
***
## Choose your cloud
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://v2.dataos.info/operate/phase-1-provision-data-plane/overview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.