Create a secure, flexible and unified interface to your Kafka cluster for all of your Kafka consumers and producers — no matter where how they're running.
A Kafka-native proxy unifies and secures Kafka access across real-time data consumers and producers. By decoupling clients from Kafka internals, it accelerates onboarding, enables multi-tenancy and provides better observability.
Support event-driven integration with external partners and third-parties with secure, publicly reachable Kafka end/entry-points that have custom DNS names.
Logically segment a single Kafka cluster to enable multiple independent client groups to operate in isolation.
Deploy a custom DNS name inside both primary and secondary regions to support seamless disaster recovery with a simple DNS record update.
Support event-driven integration with external partners andthird-parties with secure, publicly reachable Kafka end/entry-points that have custom DNS names.
Logically segment a single Kafka cluster to enable multipleindependent client groups to operate in isolation.
Deploy a custom DNS name inside both primary andsecondary regions to support seamless disaster recovery with a simple DNS record update
Zilla Plus is a Kafka-native proxy that simplifies and secures access to your Kafka cluster. Deployed at the edge, it creates publicly accessible entry points that external clients can use to connect, publish, and subscribe—without exposing your brokers directly. Zilla Plus also supports cluster virtualization, enabling multiple isolated client groups to share the same physical Kafka infrastructure while operating independently.
While Public Access is a feature of MSK, it exposes brokers directly to the public internet and lacks support for custom domain names.
A custom domain name not only helps align your public Kafka endpoints with your own domain, it provides a static DNS name should it become necessary to recreate the Kafka cluster behind the scenes. It also allows you to expose a cluster using only a single Elastic IP address, which simplifies local firewall policies and eases client integrations. A single Zilla Plus deployment can support multiple custom domains and run in front of multiple Kafka clusters.
Virtual Clusters allow for the logical segregation of a single physical Kafka cluster into multiple virtual clusters through configuration. This enables multiple segmented groups of clients to operate within the same Kafka environment while maintaining isolation. Zilla Plus doesn't require any changes to the existing Kafka cluster, making it easy to implement Virtual Clusters with minimal effort.
AWS Shield and AWS WAF can be activated on the Network Load Balancer that is deployed alongside Zilla Plus proxies, protecting its endpoints against DDoS and network layer (layer 3), transport layer (layer 4), and application layer (layer 7) attacks.
Zilla proxies are stateless and only require a single Network Load Balancer. This reduces both the complexity and costs of scaling out.
Zilla Plus works with your Kafka platform of choices and offers dedicate partner versions for seamless setup
“Zilla Plus reduced our lead time for integration development and rollout. We can now dedicate more time to designing our Kafka topics and schema, which would have been otherwise spent building a middleware layer for integrating 3rd party external networks into our AWS VPCs.”
