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

# Architecture

<Card title="TL;DR" icon="sparkles">
  * Condense uses a three-tier architecture: the cloud provider you deploy from, Zeliot's consol (the Central Tower), and the Condense Core that runs inside your own account.
  * The data plane runs entirely inside your own cloud account. Your event data never leaves it, and Zeliot has no  access to it.
  * The Condense Console only orchestrates: it manages deployments, user authentication, release updates, and health monitoring. Your data does not flow through it.
  * The same architecture deploys on Microsoft Azure, AWS, and Google Cloud. Only the provider's building blocks change names (AKS, EKS, GKE).
  * Everything that touches your data, from Kafka to connectors to transforms, runs inside a private Kubernetes cluster in your own VPC.
</Card>

Condense is structured as an integrated platform in which data integration, event streaming, stream processing, application execution, and platform operations work together as parts of a common architecture. The architecture is built around a managed Kafka-based streaming foundation and extends upward into processing and application capabilities, while the platform provides the infrastructure and operational controls required to run these workloads in production.

<Frame>
  <img src="https://mintcdn.com/zeliot/2Ir_1XmKGIjx3B7T/images/image-124.png?fit=max&auto=format&n=2Ir_1XmKGIjx3B7T&q=85&s=161bcc0833d66dacd0c4d02a51301b1c" alt="Image" width="1560" height="928" data-path="images/image-124.png" />
</Frame>

The Condense architecture can be understood through the following layers:

```text theme={null}
┌──────────────────────────────────────────────────────────────┐
│                  Applications & Services                     │
│             Real-Time Applications • APIs                   │
├──────────────────────────────────────────────────────────────┤
│                 Application Development                      │
│          IDE • Code Repository • Custom Logic               │
├──────────────────────────────────────────────────────────────┤
│                    Stream Processing                         │
│       Transforms • Enrichment • Filtering • Routing         │
├──────────────────────────────────────────────────────────────┤
│                     Condense Kafka                           │
│       Managed Kafka • Topics • Schemas • Streaming           │
├──────────────────────────────────────────────────────────────┤
│                    Data Integration                          │
│      Device • Database • Cloud • API • Enterprise            │
└──────────────────────────────────────────────────────────────┘
              │                              │
              └──────────────────────────────┘
                             │
              Platform Operations & Controls
          Deployment • Scaling • Observability
                 Security • Governance
```

## \*\*Trusted Deployment Model \*\*

### **Your cloud. Your data. But the responsibility is ours.**<br />

Condense follows a fully managed Bring Your Own Cloud (BYOC) architecture where every component is deployed inside your Azure, AWS, or Google Cloud environment. Unlike SaaS platforms where data leaves your environment, Condense operates entirely within your cloud subscription.

<Columns cols={2}>
  <Column>
    <Card title="CUSTOMER OWNS" icon="sparkles">
      * Cloud Subscription
      * Kubernetes Cluster
      * Virtual Network
      * Networking
      * Storage
      * Compute
      * Databases
      * Data
      * IAM Policies
    </Card>
  </Column>

  <Column>
    <Card title="ZELIOT MANAGES" icon="sparkles">
      * Apache Kafka
      * Platform Services
      * Updates & Patches
      * Monitoring
      * Health Checks
      * Scaling
      * Release Management
      * Security Updates
      * Support
    </Card>
  </Column>
</Columns>

Instead of a shared SaaS environment, Condense runs as a fully isolated deployment inside your cloud account. Your devices talk to your cluster. Your data stays in your VPC. Zeliot operates the platform without requiring any transactional data access.