> For the complete documentation index, see [llms.txt](https://docs.decube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decube.io/security-and-infrastructure/deployment-methods/bring-your-own-cloud-byoc.md).

# Bring-Your-Own-Cloud (BYOC)

### Bring Your Own Cloud- BYOC Simplified Block Diagram

**Diagram: Bring Your Own Cloud - BYOC Simplified Block Diagram**

<figure><img src="/files/tgkvaGbhQSGF9JumAWax" alt=""><figcaption></figcaption></figure>

In the BYOC model, Decube’s data plane is fully deployed in the customer’s own cloud for complete control and compliance with data locality requirements.

#### Components:

* **Control Plane** (Decube-hosted)
* **Customer Cloud Environment**
  * Data Plane (deployed in customer's infrastructure)
    * Metadata API
    * Metadata Storage
    * Distributed Job Scheduler
    * Metadata Collector
    * Data Quality Monitoring
* **Customer Data Source**
  * Remains within the customer’s environment.

#### How it Works:

* All processing (metadata collection, quality monitoring) happens within the customer's cloud.
* Only essential metadata (e.g., configurations, license info) is synced back to Decube’s control plane.

#### Data Security:

* No sensitive metadata or raw data leaves the customer’s environment.
* This model is ideal for organizations with strict data governance or residency requirements.

To learn more about how data is handled refer to data policy.