> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduktor.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Kafka data sharing with partners
> Share Kafka topics with external partners without data duplication using Conduktor Partner Zones.
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**
**From our blog:** [The Kafka data sharing ladder](https://www.conduktor.io/blog/the-data-sharing-ladder) Where Partner Zones sit on the four-level path from internal streaming to external data exchange.
## 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.
```mermaid theme={null}
flowchart TD
K[Your Kafka cluster] --> GW[Conduktor Gateway]
GW --> A[Partner Zone A]
GW --> B[Partner Zone B]
A -. "orders-public, inventory-summary" .-> PA([Partner A connects here])
B -. "shipment-events" .-> PB([Partner B connects here])
```
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
| Capability | Description |
| --------------------- | ------------------------------------------------------------------------ |
| Topic aliasing | Expose internal topic names under partner-facing aliases |
| Scoped access | Each zone sees only its assigned topics — no cross-zone visibility |
| Bidirectional sharing | Partners can produce to topics you allow, not just consume |
| Traffic analytics | Monitor bytes in/out, record counts, and consumer lag per zone |
| Credential isolation | Partner credentials are independent — rotating one doesn't affect others |
## Related resources
* [Get started with Partner Zones](/guide/use-cases/third-party-data)
* [Configure Partner Zone traffic analytics](/guide/tutorials/configure-partner-zone-traffic-analytics)
* [View resource reference](/guide/reference/console-reference#partner-zones)
* [Give us feedback/request a feature](https://conduktor.io/roadmap)