Skip to main content
If a partner needs access to your Kafka topics, the usual approach is to replicate the data to a separate cluster. That works, but it means two copies to maintain and keep in sync. Partner Zones skip the copy. You share specific topics directly through Gateway, with controls over what the partner can see and do:
  • set up dedicated zones with customized access to Kafka topics
  • create a single source of truth because data isn’t duplicated
  • reduce operational costs, since you don’t have to keep data streams synchronized
  • track consumed and produced data with traffic analytics
Partner Zones overview

​
How it works

A Partner Zone is a filtered view of your Kafka cluster, served through Conduktor Gateway. Partners connect with their own credentials and see only what you’ve shared — topics appear under whatever names you choose to expose. Partners get a dedicated Kafka bootstrap endpoint and credentials. From their perspective, they connect to a standard Kafka cluster — no special client libraries needed.

​
Key capabilities

CapabilityDescription
Topic aliasingExpose internal topic names under partner-facing aliases
Scoped accessEach zone sees only its assigned topics — no cross-zone visibility
Bidirectional sharingPartners can produce to topics you allow, not just consume
Traffic analyticsMonitor bytes in/out, record counts, and consumer lag per zone
Credential isolationPartner credentials are independent — rotating one doesn’t affect others