Assistant Manager at a government with 201-500 employees
Real User
Top 10
Dec 30, 2025
I use Kong Konnect most often as a current gateway. A specific example of how I use Kong Konnect as a current gateway involves onboarding microservices into Kong Konnect where we pass the host map pattern and pass the endpoint in the route path. This is how we are configuring our setup.
API Technical Architect at Independent API Consultant
Real User
Top 5
Oct 28, 2025
I have experience with both Apigee and Kong API Gateway. I have migrated from Apigee to Kong Konnect for organizations. I am working currently with Kong Konnect SaaS Enterprise, which is the SaaS version of Kong. I have also worked on Kong Gateway Enterprise. With Kong Konnect, AWS is the provider by default. However, the gateway runtime can be installed anywhere, the Kong Gatewa runtime also called the Kong Data Plane is platform agnostic. It does not have to be in AWS. It can be in Azure or on-prem as well.
IT Soulutoin Expert at a tech vendor with 10,001+ employees
Real User
Top 10
Apr 25, 2025
I use Kong Konnect ( /products/kong-konnect-reviews ) as an API Gateway or API management solution. I have several use cases, including securing internal APIs within Siemens network by deploying Kong Gateway on Amazon EKS ( /products/amazon-eks-reviews ). This acts as an API management layer to expose other internal services such as logging and Jira ( /products/jira-reviews ) APIs. Additionally, I utilize it for external use cases by deploying an API Gateway for consumers accessing services from the internet. My aim is to create a federated API management platform where various business units can still use their preferred choice of gateways while maintaining a central federation layer to control security and logging policies.
Kong Konnect facilitates efficient management and integration of APIs, providing a streamlined experience for developers to manage their services with high scalability. Kong Konnect is a comprehensive platform tailored for API development and management. It offers an intuitive interface that simplifies the process of connecting, managing, and securing APIs. Organizations benefit from its scalable architecture, ensuring it meets diverse operational demands and optimizes service delivery,...
I use Kong Konnect most often as a current gateway. A specific example of how I use Kong Konnect as a current gateway involves onboarding microservices into Kong Konnect where we pass the host map pattern and pass the endpoint in the route path. This is how we are configuring our setup.
I have experience with both Apigee and Kong API Gateway. I have migrated from Apigee to Kong Konnect for organizations. I am working currently with Kong Konnect SaaS Enterprise, which is the SaaS version of Kong. I have also worked on Kong Gateway Enterprise. With Kong Konnect, AWS is the provider by default. However, the gateway runtime can be installed anywhere, the Kong Gatewa runtime also called the Kong Data Plane is platform agnostic. It does not have to be in AWS. It can be in Azure or on-prem as well.
The clients mainly were using Proofpoint for email security, which is the primary use case. We have used Proofpoint for email security.
I use Kong Konnect ( /products/kong-konnect-reviews ) as an API Gateway or API management solution. I have several use cases, including securing internal APIs within Siemens network by deploying Kong Gateway on Amazon EKS ( /products/amazon-eks-reviews ). This acts as an API management layer to expose other internal services such as logging and Jira ( /products/jira-reviews ) APIs. Additionally, I utilize it for external use cases by deploying an API Gateway for consumers accessing services from the internet. My aim is to create a federated API management platform where various business units can still use their preferred choice of gateways while maintaining a central federation layer to control security and logging policies.