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

# Bring Your Own Cloud

<video src="https://mintcdn.com/zeliot/YtqqDt49zRpgaxlx/videos/ZGoY5hvBUcWARUBdAICdD1g.mp4?fit=max&auto=format&n=YtqqDt49zRpgaxlx&q=85&s=356c1a03a02cee731a01dc099be431ef" controls data-path="videos/ZGoY5hvBUcWARUBdAICdD1g.mp4" />

Bring Your Own Cloud (BYOC) allows organizations to deploy Condense entirely within their own cloud environment while retaining complete ownership of their infrastructure and data.

Unlike multi-tenant SaaS deployments, every Condense component runs inside your AWS, Microsoft Azure, or Google Cloud account. Your streaming applications, Kafka clusters, connectors, data pipelines, storage, and networking remain under your control while Condense manages the platform lifecycle.

BYOC combines the operational simplicity of a fully managed streaming platform with the security, governance, and compliance required by enterprise deployments.

***

# Why BYOC : Trusted Deployment Model 

Many organizations cannot move operational data outside their cloud environment due to security, regulatory, or internal governance requirements.

BYOC enables these organizations to adopt a fully managed streaming platform without compromising data ownership or cloud security.

Key advantages include:

* Complete ownership of cloud infrastructure.
* Data remains inside your cloud account.
* Integration with existing networking and security policies.
* Native support for enterprise governance and compliance.
* No shared application infrastructure.

***

# How BYOC Works

Condense is deployed directly into your cloud subscription as a private deployment.

The platform provisions and manages the required infrastructure, including Kafka, Kubernetes, connectors, observability services, platform services, and development components, while all compute, storage, and networking resources remain within your cloud environment.

Platform upgrades, maintenance, monitoring, and lifecycle management are handled by Condense without requiring customers to operate the underlying streaming infrastructure.

<Columns cols={2}>
  <Column>
    CUSTOMER OWNS

    * Cloud Subscription
    * Kubernetes Cluster
    * Virtual Network
    * Storage
    * Compute
    * Databases
    * Networking
    * Data
    * IAM Policies
  </Column>

  <Column>
    ZELIOT MANAGES

    * Condense Platform
    * Apache Kafka
    * Platform Services
    * Updates & Patches
    * Monitoring
    * Health Checks
    * Scaling
    * Release Management
    * Security Updates
    * Support
  </Column>
</Columns>

***

# Supported Cloud Providers

Condense supports Bring Your Own Cloud deployments on:

* **Amazon Web Services (AWS)** using Amazon EKS
* **Microsoft Azure** using Azure Kubernetes Service (AKS)
* **Google Cloud Platform (GCP)** using Google Kubernetes Engine (GKE)

Each deployment follows the same Condense architecture while using native cloud networking, storage, container registry, and Kubernetes services.

***

## How Condense Enables BYOC 

<Card title="01 Deploy Inside your Private Cloud " icon="sparkles">
  Condense is deployed inside a private Kubernetes cluster within your existing cloud environment. Everything from Kafka to platform services runs within your private network.

  **Supported Platforms:**

  * Microsoft Azure (AKS)
  * Amazon Web Services (EKS)
  * Google Cloud Platform (GKE)
  * Redhat Openshift
</Card>

<Card title="02 Local Container Registry " icon="sparkles">
  Instead of downloading containers from external registries every time, Condense synchronizes only approved platform images into your local container registry

  **Benefits**:

  * Faster Deployments
  * No Unnecessary Internet Dependency
  * Image Version Control
  * Air-Gapped Friendly Deployments
</Card>

<Card title="03 Secure Private Networking " icon="sparkles">
  All platform communication happens inside your private virtual network. No production data traverses public infrastructure

  * The Deploymnet Includes:
  * Private Kubernetes Cluster
  * Cluster & Management Subnet
  * VPC / VNet Peering
  * Internal Service Communication
</Card>

<Card title="04 Built-In Streaming Platform" icon="sparkles">
  Every deployment includes all required platform components. Everything is deployed as cloud-native Kubernetes workloads

  Platform Dervices inlcluded  :

  * Apache Kafka
  * I/O Connectors
  * Observability
  * Release Management
  * Metering Services
  * Redis/PostgreSQL/MQTT
  * Command Services
  * Development Containers
</Card>

<Card title="05 Centralized Operations " icon="sparkles">
  Although every customer has an isolated deployment, Zeliot securely manages all deployments from a centralized ops platform. Customer workloads remain completely isolated

  * Health Monitoring
  * Version Management
  * Platform Upgrades
  * Security Patches
  * Diagnostics
  * Configuration Dashboard
  * Incident Management
  * Release Automation
</Card>

***

# Benefits

BYOC provides the flexibility of cloud-native deployment with the operational simplicity of a fully managed streaming platform.

Key benefits include:

* Complete data ownership.
* Enterprise-grade security.
* Cloud-native deployment.
* Automated platform upgrades.
* Fully managed Kafka.
* Integrated observability.
* Elastic scaling.
* Native cloud networking.
* Faster production deployments.
* Reduced operational overhead.

***