Virtual topics
A virtual topic is to a Kafka topic what a SQL view is to a table. It is a topic name that exists only on the gateway, backed by a physical topic and optionally filtered. Clients produce, consume, commit offsets and join groups on it like on any topic. Nothing is copied: partitions, offsets, retention and storage are the physical topic's.
Authentication
Every client gets its own Kafka identity on the gateway, while the cluster sees only one. Clients log in to kawa with standard Kafka SASL or a client certificate; kawa applies access control per client and talks to the brokers as a single service identity. Onboarding a client never touches the cluster: no SASL users, no principals, no broker ACLs.
Access control
Access control is Kafka ACLs per client, enforced at the gateway. Every client authenticates to kawa with its own identity; kawa checks each request against that client's ACLs and refuses it with the standard Kafka authorization error before it reaches a broker. The cluster only sees kawa's single service identity, so there are no per-client principals, ACLs or SASL users to manage on the brokers.
Governance
Governance enforces your naming conventions and topic standards at the gateway. Topic names, consumer group ids and transactional ids must follow your conventions, and topics must meet your sizing and config standards, or kawa refuses the request before it reaches a broker. Rules are CEL expressions, judged per principal and changed live: no broker plugins, no CreateTopicPolicy classes, no restarts.