# 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.


---

# Agent Instructions: 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:

```
GET https://docs.decube.io/security-and-infrastructure/deployment-methods/bring-your-own-cloud-byoc.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.