TL;DR
- 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.

**Trusted Deployment Model **
Your cloud. Your data. But the responsibility is ours.
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.
CUSTOMER OWNS
- Cloud Subscription
- Kubernetes Cluster
- Virtual Network
- Networking
- Storage
- Compute
- Databases
- Data
- IAM Policies
ZELIOT MANAGES
- Apache Kafka
- Platform Services
- Updates & Patches
- Monitoring
- Health Checks
- Scaling
- Release Management
- Security Updates
- Support