# Share Kafka Topics with Partners or Other Teams

One company produces, another consumes, and neither ever touches your Kafka cluster. An external partner gets its own isolated virtual cluster with friendly topic names, the Gateway rejects their produce until it meets your standards, and a second partner receives only the records you chose to share. Shown with external partners; the same configuration isolates internal teams.

## What You'll Learn

- Give each partner an isolated virtual cluster where your internal topics appear under friendly alias names
- Enforce producer standards like LZ4 compression and idempotence at the proxy, with the fix spelled out in the error
- Filter what each consumer sees with a SQL topic view at read time, and watch a record flow end to end