Technical Support Analyst at a tech vendor with 10,001+ employees
Real User
Top 20
Jan 16, 2026
My main use case for Tyk is for internal API gateway. For a banking customer, I have internal APIs and external APIs, where internal APIs are mostly on Kubernetes. For internal API gateway, we have developed some security frameworks within Tyk, which is how we use Tyk only for internal APIs. This setup is Kubernetes native, which is good, and even the custom plugin development for validating the token is something we use a lot.
The common elements of the use case are a medium to a high volume of API calls, generally in a Microsoft-based environment, and occasionally Amazon. Implemented on the public cloud primarily for financial institutions. Serving retail clients with a reasonably complicated system architecture involving legacy technology and a variety of more modern administration services and systems. Then, the full customer service frontend, where we've got the design interface plugged into the customer journey flows, makes those somewhat dynamic with a standard render forward from the CNA.
We are a solution provider and Tyk is one of the solutions that we implement for our customers. It is an API gateway and management system that is the single entry point for all of the microservices.
Solution Architect (Africa Regions) at a financial services firm with 10,001+ employees
Real User
Jul 18, 2019
What we have been trying to do is reveal APIs for some businesses that we're trying to create that still use some of our legacy platforms and incorporate the newer technologies that we're trying to bring on.
I am a back and front end developer and I have a great experience with Tyk Management. We mainly use it to manage our APIs. We have API introductions for our customers.
Tyk is an open source API Gateway that is fast and scalable, an API management platform featuring an API gateway, analytics, developer portal and dashboard.
Available in three flavours to best suit your architecture and governance. We offer full cloud or on-premises options, and the best of both worlds with our unique hybrid model.
www.tyk.io
My main use case for Tyk is for internal API gateway. For a banking customer, I have internal APIs and external APIs, where internal APIs are mostly on Kubernetes. For internal API gateway, we have developed some security frameworks within Tyk, which is how we use Tyk only for internal APIs. This setup is Kubernetes native, which is good, and even the custom plugin development for validating the token is something we use a lot.
The common elements of the use case are a medium to a high volume of API calls, generally in a Microsoft-based environment, and occasionally Amazon. Implemented on the public cloud primarily for financial institutions. Serving retail clients with a reasonably complicated system architecture involving legacy technology and a variety of more modern administration services and systems. Then, the full customer service frontend, where we've got the design interface plugged into the customer journey flows, makes those somewhat dynamic with a standard render forward from the CNA.
We use this solution to measure, and eventually scale our application programming interfaces.
We are a solution provider and Tyk is one of the solutions that we implement for our customers. It is an API gateway and management system that is the single entry point for all of the microservices.
What we have been trying to do is reveal APIs for some businesses that we're trying to create that still use some of our legacy platforms and incorporate the newer technologies that we're trying to bring on.
I am a back and front end developer and I have a great experience with Tyk Management. We mainly use it to manage our APIs. We have API introductions for our customers.