We use this solution as a way to expose our internal APIs, both internally in Kubernetes and for private cloud of our own.

Within Kong Gateway Enterprise, we utilize Kong Ingress and the Com API Gateway. It offers a wide range of plugins that we leverage, including OIDC, Rate Limiting, Lambda functions, and more. We also configure multiple deployments and utilize plugins like the OIDC Registration plugin for authentication and authorization. Additionally, we ensure schema validation for incoming requests and utilize security scanning. Kong Gateway provides a Request Transformer plugin that allows us to add or remove header values as needed.

We use Kong for our API gateway, handling all public traffic. It is an open-source tool, and even though we are a startup, it provides us with stability without incurring high costs initially.

I use it as a gateway for our APIs. We have several hundred APIs here, so we use Kong Gateway Enterprise to manage and monitor them. In this application platform, we prefer to use the Kong Enterprise UI instead of the Kong Community Edition GUI.

My company gave Kong Enterprise to only one company in the manufacturing sector, and now we are in talks with another manufacturing company.

Kong Enterprise is very useful, especially for IoT applications. Palo Alto Networks is also good for IoT applications. Kong Enterprise has a great licensing model. I am scanning capabilities, making it a good tool for infrastructures.

It serves as an API gateway and microservices management platform, facilitating the creation, deployment, and oversight of APIs and microservices. It serves as a solution for measuring requests, managing upstreams, and handling internal APIs within the bank.

My company uses Kong Enterprise for ISC, so if we need data in one place or one application, we use the solution to retrieve the data with the help of REST API.

We had worked for a client from the travel industry who wanted to propose an API manager. They had built microservices on Java and another integration tool. They wanted to apply policies, register their APIs in the API manager, and enforce policies and plugins, like client ID, client secret, throttling, rate limiting, and protocol transformation. The client wanted to apply these things to their APIs.

We use the solution for managing microservices and in-built APIs.

I lead the integration practices in my organization and have been working in integration for the past 16 years, managing API integrations with various API manager tools such as Kong Enterprise.

We are primarily using Kong for the API gateway functionality. For example, we've had a couple of mobile applications with outbound traffic where we would use the Kong Enterprise gateway to expose the API by applying authorization, authentication, and other security policies.

We have also used Kong for role-based access control mechanism (RBAC) and integrated it with our enterprise directory in order provide it with this form of access control.

There was another particular use case in which we performed some customization, as well. In that scenario, we wrote a Lua script on top of Kong to add an AppDynamics plugin to our web server, for observability and monitoring purposes. 

Kong has been used over a large user base, not only because it's an enterprise application, but also because the mobile applications we worked with were B2C-based in the retail industry, so the number of users was quite high.

The product seems to be good, especially in terms of API creation and management. The tool is seamlessly easy to use, and offers ease of configuration and management. The tool has some very good options for infusing some API security parts. The tool also offers some readily available connectors as well. From an overall perspective, I am handling both B2B integrations and cloud integrations. In our company, we had multiple products in place of Kong Gateway Enterprise.

We use it to provide API services to our clients.

I use the solution in my company since we build our own products by using Spring Boot, Python and FastAPI. We mainly use the tool to monitor and provide security on top of those APIs.

Our primary use case for this solution is API management.

We deploy this solution to our customers who are enterprise companies. We are partners with Kong and I'm the director of engineering. 

We have several microservices that are secure using Kong Enterprise. Our microservices are managed through Kong Enterprise API management.

We have integrated with IDP to secure it. We use multiple plugins that are bundled with Kong Enterprise.

Our e-commerce customers use Kong Enterprise.

My company is a financial company involved in credit card processing. We use the solution for internal IT secure gateway. 

Kong Enterprise was used for standard API gateway use cases for Microarchitecture.

A central API gateway solution.

Our primary use case of this solution was a secure API Gateway hosted on public cloud infrastructure. The  manageability, deployment architecture options and scalability were key considerations. Kong is great at organising our API ecosystem and providing the required manageability, scalability observability and  security.

I'm the vice president of technology and architecture and we are customers of Kong Enterprise. 

We define our enterprise architect and Kong has been selected as an API integration layer solution. We deploy in some of the markets if they're ready to go, and some of the markets are not really ready because we have 10 different markets at the moment. It's an API integration layer so that we can expedite our microservices to the market.

We mostly use this as an intrusion prevention system.