# 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="https://1779874722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTw0qpCVzfrIXqS4FEg4T%2Fuploads%2Fgit-blob-3e22d8d37869fb0f0522dfc00133da5a4d78244d%2Fimage.png?alt=media" 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.