Event Gateway
A protocol-native Gateway built for governance, security, and cost-efficient use of KafkaThe event gateway is composed of two core branches: protocol mediation using the Kong Gateway and native event processing using the Kong Native Event Proxy.
Protocol Mediation
Protocol mediation enables HTTP clients to produce to and consume from event streams using Kong Gateway.
This includes functionality such as producing to and consuming from Kafka topics via http-get or SSE.
In Kong Gateway, we provide multiple plugins to produce and consume data for Kafka, as well as a Kafka logging plugin.
Kong Native Event Proxy (Beta)
KNEP is a proxy for the native Kafka protocol that sits between native consumers and producers, and backend Kafka clusters. It supports features such as cluster virtualization, authentication mediation, and encryption of message payloads and keys.
Through its extensible policy engine, you can augment, optimize, and secure your Kafka deployments with customized business logic to transform, encrypt, and observe Kafka messages.
The Kong Native Event Proxy supports many policies such as encryption, cluster virtualization, message filtering, and more.
Frequently asked questions about KNEP
Are OS-specific distributions currently supported?
During the beta of Kong Native Event Proxy, we will only provide support for Docker images. If you have OS specific requirements, please share with the Kong team.
How is KNEP deployed?
The KNEP Data Planes are self-managed and deployed by you, the user. The KNEP Control Plane is part of the Kong Konnect platform.
How can I get access to the Kong Native Event Proxy?
If you’re an existing Kong customer or prospect, please fill out the beta participation form and we will reach out to you.
I am interested in using KNEP but don’t have a Konnect account - how do I get started?
Start by filling out the beta participation form. Once we get in touch, we’ll provide instructions on how to set up a Konnect account and enable KNEP for your organization.