If you're building distributed applications or working in cloud native development, you know that robust connectivity and API governance are the foundations for speed and scale. However, this also holds true in the realm of event streaming. Many top companies now depend on Apache Kafka and Event-Driven Architecture (EDA) for resilience and real-time capabilities. However, the security, governance, and productization tools and capabilities that are already available for APIs are frequently absent from the EDA world, particularly for Kafka.
The Kong Event Gateway is the missing link. It seamlessly extends the governance and lifecycle management used for synchronous APIs to Kafka event streams. It's time to stop treating your streams like plumbing and instead treat them as valuable data products — and we’ll be talking more about this at API Summit 2025.
We launched Event Gateway support for Kafka as beta back in April with great success, and we’ve made a ton of progress since then. The GA release is scheduled for October, and we're looking forward to showcasing everything new at API Summit. If you want to learn more, we highly recommend attending Summit, but we'll give you a sneak peek of what we've been working on in the sections below.
Register for API Summit 2025 now!
We’ll be talking all about how teams can use the Event Gateway for true event data productization at Summit.
But first, what is event data, or event API productization?
Event API productization entails transitioning from a service-centric to a consumer-centric view of streams, where each stream is a secure, well-defined product.
An Event Data Product must have:
Without a centralized control point, managing these data products results in a governance gap.
The Kong Event Gateway is designed to close this gap by implementing consistent controls at the Gateway layer so that they are easier to standardize across the business.
Kong Event Gateway, along with the rest of the Konnect platform, enables your organization to transform what you're already building (or plan to build) with Kafka into self-service, monetizable data products.
It starts with the Gateway, which serves as a central control point for Kafka clusters and topics, exposing them as virtual clusters with consistent security, reliability, and performance policies managed at the Gateway layer rather than the client-side.
These policies include:
With this kind of central control point, you're free to start opening up access to your event broker event data and publishing it as self-service AsyncAPI products in your Konnect Developer Portal. And who knows, maybe you’ll even be able to use OpenMeter to monetize that data…
You’ll have to learn more at API Summit!
Want to see Event data productization in action? Join us at API Summit, where Kong will unveil the latest in Kong Event Gateway and demonstrate how it can provide a strong foundation for your broader API and event streaming strategy.
In large organizations, platform architecture tends to be more historical artifact than intentional design. At the foundation of the stack sit monoliths that predate modern API standards; many of them are too risky or too costly to decommission full
Gartner's strategic planning assumption: by 2029, 50% of software application providers will be forced to share their context layer externally for third-party orchestrators to stay relevant. Today, that number is less than 2%. This isn't a gradual e
A Response to Gartner’s Latest Research Gartner's strategic planning assumption stops you in your tracks: by 2029, 50% of software application providers will be forced to share their context layer externally for third-party orchestrators to stay r
Your Kafka Doesn't Have to Live Behind a Wall When teams resort to VPC peering or PrivateLink to expose Kafka, they're not solving the problem — they're managing it, one network topology decision at a time. Every new external consumer adds compl
This is the pitch to the board and the C-suite. It must be brutally concise, focused entirely on your business outcomes, not the technology. If the first page doesn't articulate value, the strategy dies. Why? It immediately frames the initiative in
Why Risk Management Will Separate Agentic AI Winners from Agentic AI Casualties Let's be honest about what's happening inside most enterprises right now. Development teams are under intense pressure to ship AI features. The mandate from leadership
AI spending is exploding across the organization—but often not in the ways leadership approved or finance can track. Development teams spin up LLM connections to ship features faster. Data teams provision GPU clusters for experiments that get abando