A LinkedIn post from Kong Inc highlights challenges platform teams face when providing external access to Apache Kafka event streams at scale. The post notes that Kafka is typically designed for internal, private network environments, making secure partner access non-trivial and risky if handled through ad-hoc network changes.
Claim 30% Off TipRanks
- Unlock hedge fund-level data and powerful investing tools for smarter, sharper decisions
- Discover top-performing stock ideas and upgrade to a portfolio of market leaders with Smart Investor Picks
According to the post, a recent blog by a Kong product manager outlines best practices for external Kafka connectivity with an emphasis on security and scalability. The post also points to Kong’s Event Gateway as a potential tool for addressing these integration issues and enabling more controlled exposure of Kafka streams to external stakeholders.
For investors, this focus suggests Kong is positioning its Event Gateway around a concrete, high-value infrastructure problem faced by enterprise platform teams. If the product gains adoption among Kafka-heavy organizations, it could strengthen Kong’s role in API and event-driven architectures, support higher-margin platform revenue, and deepen its integration footprint within large accounts.
Strategically, addressing external Kafka access may expand Kong’s relevance beyond traditional API management into event streaming governance and security. This could enhance competitive differentiation versus other integration and gateway vendors and potentially open cross-sell opportunities where customers are already standardizing on Kafka for mission-critical data flows.