Event gateways are becoming a popular answer to a real problem in event-driven architecture: the lack of a clear control plane.
But they should not be understood as API gateways for events. Events have different failure modes. Ownership is less visible. Compatibility changes over time. Policies are harder to enforce without coupling producers and consumers again. Observability depends on more than traffic flowing through a single point.
This talk examines where event gateways are useful, where brokers, schema registries, catalogs, and portals already cover part of the problem, and where the gateway metaphor starts to break down.
The focus is not another infrastructure layer. The focus is which governance capabilities event-driven systems actually need, and how AsyncAPI can help describe them.