Sold by
Zilla Plus Gateway for Amazon MSK (AMI)
A Kafka-native gateway that provides a secure, governed access layer in front of your MSK cluster. Zilla Plus abstracts brokers, enforces policies, & translates protocols to safely expose data streams to apps, services, & external partners.
Reviews (2)
YeshwanthKumar Sundar
Centralized workflow tracking has improved coordination and currently streamlines daily operations
Reviewed on May 19, 2026
Review provided by PeerSpot
What is our primary use case?
I am mainly using Zilla Plus for workflow management activities.
What is most valuable?
Zilla Plus helps with process coordination by giving better visibility and tracking across workflows and operational activities. It allows teams to monitor task progress, manage dependencies, and ensure the different activities stay aligned without relying heavily on manual follow-ups. In day-to-day operations, it helps coordinate activities between teams by centralizing updates and status information in one place. This improves communication, reduces delays, and makes it clear to identify bottlenecks.
Zilla Plus is very helpful for improving operational visibility and accountability. Since task and workflow status are centralized, it becomes easier to track ownership, follow progress, and ensure activities are completed on time. This reduces dependency on manual coordination through emails or chats and also helped during incident handling and operational reviews because teams can quickly understand the current state of activities and prioritize actions more effectively.
Overall, Zilla Plus fits into a visibility layer that improves efficiency and team collaboration. It also improves operational visibility and accountability. It helps us streamline collaboration between more organized workflows, where it gives you better visibility and tracking across the workflows and operational activities. It also allows the teams to monitor task progress, manage dependencies, and ensure that different activities stay aligned. For example, it helped coordinate between teams by centralizing updates.
The feature that stands out most to me in Zilla Plus is centralized visibility and workflow tracking. Having a single place to monitor task, process status, and operational activities makes coordination much easier across teams. Instead of relying on multiple tools or manual follow-ups, everyone has clear visibility into what is happening and what needs attention.
This has the biggest day-to-day impact because Zilla Plus improves communication, reduces delays, and helps identify bottlenecks quickly, making overall operations more efficient and organized.
What needs improvement?
When it comes to the improvement of Zilla Plus, one area is dashboard customization and reporting flexibility. More advanced options for creating tailored views and reports would help different teams analyze workflows more effectively. Another improvement would be deeper integration with external tools and platforms; expanding integration capabilities with project management, communication, and monitoring tools would make workflows even more seamless.
More automation and intelligent recommendation would be valuable for Zilla Plus. For example, automatically identifying the bottlenecks or suggesting the workflow optimization based on usage patterns.
For how long have I used the solution?
I have been using Zilla Plus for the past one and a half years as part of operational and workflow management activities.
What do I think about the stability of the solution?
Zilla Plus is very stable.
What do I think about the scalability of the solution?
Scalability for Zilla Plus is very good. We deployed it on Kubernetes, and it is very good in scalability when compared to the users that we have in our team.
How are customer service and support?
The customer support for Zilla Plus is very good. It is a ticket-based system where we will raise the tickets and the support engineer will help us to resolve our issues through the ticketing system.
Which solution did I use previously and why did I switch?
Zilla Plus is the first solution that we are using.
How was the initial setup?
Zilla Plus is a very good tool if you are currently using manual tracking methods like spreadsheets, email coordination, and basic product management tools. It is a very good option for better workflow visibility, centralized tracking, and improved coordination across teams.
What about the implementation team?
We have not evaluated other options before choosing Zilla Plus.
What was our ROI?
In terms of measurable outcomes, we observed around 25 to 30% of improvement in operational efficiency, 20 to 25% reduction in coordination delays, and faster tracking and resolution of workflow-related issues.
We have seen the return on investment with Zilla Plus. Overall, it is a very flexible tool, enough to scale with organizational needs. Though for a larger environment, cost can increase, but the integration is very good and supportive. It is also relatively manageable because deployment and onboarding were straightforward without requiring heavy infrastructure investment. We saw a 25 to 30% improvement in operational efficiency, a 20 to 25% reduction in coordination delays, and another benefit was faster issue resolution and workflow completion time.
What's my experience with pricing, setup cost, and licensing?
Overall, it is an amazing experience with the sales team for Zilla Plus. The cost and licensing we are getting it in a discounted manner and we felt reasonable and scalable for enterprise usage. Zilla Plus follows the subscription or enterprise licensing model, where pricing generally depends on factors such as number of users, workflow scale, integration, and support requirements.
Which other solutions did I evaluate?
We have not evaluated other options before choosing Zilla Plus.
What other advice do I have?
Zilla Plus is a solid platform for workflow coordination, operational visibility, and improving team efficiency. The reason it is not fully rated is because there is still room for improvement in areas such as advanced customization, integration, and automation capabilities. Overall, it is a reliable and useful solution for managing operational workflows effectively. It is a very good tool. I have given this review a rating of 8.
Shweta I
Secure Kafka access across cloud environments has simplified streaming integration work
Reviewed on May 13, 2026
Review from a verified AWS customer
What is our primary use case?
I am using Zilla Plus and have been working with it for the past few months, mainly around MSK serverless and connectivity and secure across VPC access use cases.
One of my main use cases that I have explored is using Zilla Plus to securely connect an application to Amazon MSK Serverless. For example, in a streaming integration setup, Zilla Plus acts as a Kafka-native proxy to simplify secure connectivity between a client application and MSK without exposing brokers publicly.
What is most valuable?
What I appreciate most in Zilla Plus is that it simplifies secure Kafka connectivity while keeping the architecture scalable and cloud-native. It helps reduce operational complexity compared to managing custom networking.
In my opinion, the best features Zilla Plus offers include secure across VPC, support for REST, SCC, and Kafka protocols together, custom domains, and TLS security supports.
Another feature is the support for multiple protocols, including REST and Kafka through a single gateway layer.
Zilla Plus has helped simplify secure Kafka connectivity and reduce the effort required to manage cross-VPC networking and authentication configuration. I also saw benefits in terms of scalability and reduced infrastructure complexity.
What needs improvement?
Zilla Plus could improve in simplifying the initial setup and onboarding experience, especially for teams that are newer to Kafka and MSK serverless architecture and configuration templates.
I monitor dashboards and more out-of-the-box analytic traffic visibility and performance insights would also add value for operational teams.
Another improvement that would be valuable is deeper support for deployment and configuration, especially for multi-environment setup.
For how long have I used the solution?
I have been working in my current field for three years.
What do I think about the stability of the solution?
In my experience, Zilla Plus has been stable for the use cases I explored, including secure Kafka connectivity and communication with Amazon MSK serverless. The architecture handled workloads reliably and integrated well within a cloud-native AWS environment.
What do I think about the scalability of the solution?
One noticeable improvement was the reduction in time spent managing and troubleshooting across VPC Kafka connectivity. I also observed better scalability in handling streaming traffic because the architecture was more lightweight and cloud-native, which reduced operational complexity and improved overall reliability.
Zilla Plus in my experience has scaled well for cloud-native streaming workloads. Its lightweight and stateless architecture make it easier to handle increased Kafka traffic and multiple client connections without adding significant operational complexity.
How are customer service and support?
The customer support has been good overall from my experience. The team was responsive during setup and integration-related queries, especially around MSK connectivity and configuration guidance.
Which solution did I use previously and why did I switch?
Before exploring Zilla Plus, the setup relied more on custom networking, configuration, and direct Kafka connectivity management and manual handling of access patterns across the environment. The switch to Zilla Plus was mainly driven by the need for a more secure, scalable, and easier-to-manage solution for cross-VPC Kafka access with authentication. It reduced the operational complexity and simplified integration management compared to maintaining a custom configuration.
I looked at a few alternative approaches before exploring Zilla Plus, including native Kafka networking setups, such as AWS PrivateLink based on custom implementation and other API gateway solutions commonly used for secure Kafka connectivity.
How was the initial setup?
Access through the AWS Marketplace made deployment and integration with existing AWS services more streamlined and convenient for the team.
What was our ROI?
I saw a measurable operational benefit after using Zilla Plus. For example, reduced time spent on networking, faster onboarding for a new integration environment, lower operational costs, and improved scalability and reliability for real-time data streaming workloads without significantly increasing infrastructure complexity.
What's my experience with pricing, setup cost, and licensing?
The setup cost was reasonable compared to the operational benefits. It provides secure Kafka connectivity and cross-VPC access, so I can work with enterprises natively, especially considering the reduction in custom infrastructure and maintenance effort, with clear pricing that is more flexible for smaller teams.
What other advice do I have?
My advice would be to clearly define your Kafka connectivity and secure and scalable requirements before implementation. Zilla Plus is valuable for teams looking to simplify secure Kafka access with IAM authentication while reducing custom networking complexity. I also recommend investing some time in understanding the architecture deployment patterns early on so that it makes the setup and long-term management much smoother.
Overall, Zilla Plus stands out as a strong solution for secure and scalable Kafka connectivity in cloud-native environments, especially for AWS MSK serverless use cases. I appreciate the focus on security, such as IAM integration and simplified cross-VPC access, and I am excited to see how the platform continues to evolve with improved deployment automation features. I would rate this solution an 8 overall.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)