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.
Tyk Cloud, Hybrid & Self Managed API Management
Tyk Technologies LtdExternal reviews
41 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Internal API gateway has improved security frameworks and now provides unified API visibility
What is our primary use case?
What is most valuable?
The best features Tyk offers are highly customizable options, effective traffic management, and security, making it easy to configure and use.
The customizability of Tyk is evident in our validation of the token—specifically with our internal identity and access management. There were challenges on the network side and in managing token validity and the public key, but Tyk allowed us to configure these aspects effectively. I believe those are the standard out-of-the-box capabilities provided by Tyk that we are using, particularly regarding traffic management and security.
Tyk has positively impacted my organization by providing standard API management capabilities, such as a single view for all APIs, discoverability, and role-based access control for overseeing who can see which APIs.
What needs improvement?
Tyk can improve in terms of AI capabilities, and the developer portal could benefit from enhancements such as user onboarding workflows. The developer community could be better, especially compared to peers, and in terms of AI capabilities, I have not heard about AI plugins from Tyk, which most API vendors provide. However, apart from that, the basic API gateway capabilities are good.
For how long have I used the solution?
I have been using Tyk for around three years.
What do I think about the stability of the solution?
Tyk is stable.
What do I think about the scalability of the solution?
Tyk's scalability is impressive; it processes millions of transactions for our internal APIs, and we have never faced any scalability issues.
How are customer service and support?
Customer support is excellent, and their support personnel, along with professional services, know the product really well, resulting in a good experience dealing with them. I would rate the customer support a definite 10.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have not switched from Tyk.
Which other solutions did I evaluate?
We evaluated WSO2, and the customer was using Azure Cloud before choosing Tyk.
What other advice do I have?
While we could not quantify any commercial improvement, developer experience has definitely improved.
I would rate Tyk around an eight on a scale of one to ten because I have worked with other API management platforms such as Apigee, Kong, and Azure API Gateway. Compared to Apigee or Kong, I find they excel beyond Tyk, which is the reason for my score.
Tyk is deployed in my organization on-premises. For another customer, we spoke with Tyk salespeople, and my experience is that they are supportive and share details effectively.
I think Tyk is very flexible and customizable for the internal API gateway, so I definitely recommend it. For external APIs, I would suggest using more mature tools. Tyk is a good product in terms of cost and deployment options.
My company has a business relationship with this vendor as partners. My overall rating for Tyk is eight out of ten.
A powerful and flexible API gateway for scalable architectures
What do you like best about the product?
Tyk distinguishes itself through its flexibility and the extensive control it offers over API gateways and traffic policies. I appreciate how straightforward it is to set up rate limits, quotas, and authentication methods, all without the need to develop custom middleware. The dashboard is sleek and responsive, making it easy to monitor API usage in real time.
Another significant benefit is its hybrid and open-source friendly design—you can deploy Tyk on-premise, in the cloud, or in hybrid environments, all without being tied to a specific vendor ecosystem. The documentation is comprehensive, and the platform handles scaling exceptionally well, even when managing a large volume of requests.
Another significant benefit is its hybrid and open-source friendly design—you can deploy Tyk on-premise, in the cloud, or in hybrid environments, all without being tied to a specific vendor ecosystem. The documentation is comprehensive, and the platform handles scaling exceptionally well, even when managing a large volume of requests.
What do you dislike about the product?
Certain configuration sections may initially seem quite complex, particularly when dealing with advanced policies or managing multiple environments. The learning curve can be steep for those transitioning from more straightforward gateways, and some features are not immediately intuitive, often requiring a closer look at the documentation rather than being easily accessible through the UI.
Furthermore, the analytics module would benefit from having more built-in visualizations, as it currently depends somewhat on external tools. While these issues are not critical, there is definitely potential to enhance usability, especially for newcomers.
Furthermore, the analytics module would benefit from having more built-in visualizations, as it currently depends somewhat on external tools. While these issues are not critical, there is definitely potential to enhance usability, especially for newcomers.
What problems is the product solving and how is that benefiting you?
Tyk has enabled us to centralize API traffic management and standardize communication between our services across different applications. It addresses challenges such as authentication, rate limiting, and security, all without requiring us to implement custom backend solutions.
Additionally, Tyk has boosted our developers' productivity by making it easier for our team to expose microservices rapidly, all while ensuring consistent policies and governance are maintained. Its stability and scalability have minimized downtime and contributed to more predictable and secure deployments.
Additionally, Tyk has boosted our developers' productivity by making it easier for our team to expose microservices rapidly, all while ensuring consistent policies and governance are maintained. Its stability and scalability have minimized downtime and contributed to more predictable and secure deployments.
Effective API Management, But Complex Setup
What do you like best about the product?
I like that Tyk offers robust features for securing, managing, monitoring, scaling, and governing my APIs. One of the most valuable aspects is my ability to track who is using my APIs, which is crucial for maintaining control and insights into API usage patterns. This feature enhances my capability to effectively monitor and secure my API interactions, providing a significant advantage over other solutions.
What do you dislike about the product?
I find the setup and configuration of Tyk to be quite complex. This complexity during initial setup can be a challenge and may require additional time and resources to get everything properly configured. Initially transitioning from other products, the ease of setup could be significantly improved to facilitate a smoother onboarding process.
What problems is the product solving and how is that benefiting you?
I use Tyk to secure, manage, monitor, scale, and govern my APIs, effectively protecting them while tracking usage. It offers robust API protection but can be complex in setup and configuration.
The best APIM solution we were able to find
What do you like best about the product?
We evaluated a handful of APIM solutions and Tyk ended up as our clear favourite. Here are a couple of points which to us made Tyk stand out over other solutions:
- Truely On-Premise and open source option without any "phone home mechanisms" (other vendors tend to push their Cloud/Hybrid solutions)
- Very easy to set up on Kubernetes
- Excellent choices of technologies which fit our existing tech stack (e.g. Postgres, Keycloak, Redis)
- Config as code ("Tyk Operator")
- Portal highly customizable via custom themes
- Well designed and intuitive UI (we found other solutions to often have overloaded UIs and/or a worse UX)
- Fair pricing
- Amazing communication and interactions with Tyk people, highly professional processes and materials
- In general a very well thought out solution
- Truely On-Premise and open source option without any "phone home mechanisms" (other vendors tend to push their Cloud/Hybrid solutions)
- Very easy to set up on Kubernetes
- Excellent choices of technologies which fit our existing tech stack (e.g. Postgres, Keycloak, Redis)
- Config as code ("Tyk Operator")
- Portal highly customizable via custom themes
- Well designed and intuitive UI (we found other solutions to often have overloaded UIs and/or a worse UX)
- Fair pricing
- Amazing communication and interactions with Tyk people, highly professional processes and materials
- In general a very well thought out solution
What do you dislike about the product?
During our setup process we found parts of the Helm/Kubernetes documentation to not be entirely exhaustive, however the Tyk team was very quick to help us with any questions we had
What problems is the product solving and how is that benefiting you?
We wanted to provide an API portal to our API consumers, where we can offer documentation and API credentials in a self-service manner.
A very good api management platform
What do you like best about the product?
Tyk is very customised and user friendly .
What do you dislike about the product?
One feature jwt token is missing. We have to generate jwt token outside and use it. Go lang plugin documentation needs to be little more precise.
What problems is the product solving and how is that benefiting you?
We are using tyk as integration tool between system and we are implementing custom logics inside tyk.
Ease of use and quick turn around
What do you like best about the product?
Its a simple gateway solution and it does its best at it . The support is good.. we asked for a feature request for an ldap authentication feature for dev portal and they implemented that in couple of days . We checked with Kong GW and they denied to implement it .We were able to seamlessly migrate from another GW too. Pretty stable and never had an issue in the last 4 years.
What do you dislike about the product?
setting up the GW using default settings is easy but a little tricky when setting up a production version of kubernetes . The support helped me to setup a kubernetes version but the documentation could have been better ..
Sometimes I observed that the latest version has features that dont work .. they need to do better in making sure all the previous features work in the new versions.
Sometimes I observed that the latest version has features that dont work .. they need to do better in making sure all the previous features work in the new versions.
What problems is the product solving and how is that benefiting you?
Its a gateway solution for us for authenticating the request and proxy it .
The Tyk product in general is good.
What do you like best about the product?
For the most parts, Tyk support is helpful and resolve my concerns.
What do you dislike about the product?
We are using the Gold support package, although Tyk managed to support us within the guranteed response time, but I usually got responses late in the envening which is off hour, so I needed to wait until the following day. Probably because Tyk support team has different working hours?
What problems is the product solving and how is that benefiting you?
We use Tyk to expose our internal APIs to external clients and currently using API CRD codebase config.
Fastest to get up and running and fewer idiosyncrasies than competitors
What is our primary use case?
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.
What is most valuable?
Of the non-Microsoft solutions, Tyk is probably the fastest to get up and running. It has fewer idiosyncrasies than many of its competitors.
The cost curve is far smoother, both in terms of volume and the number of calls it's running on, compared to most competitors. So it's a tad more expensive at the very low end, but the curve is nothing like Apigee or some of the others.
What needs improvement?
In terms of our usage, the main area of concern is that they tend to build enhancements slightly ahead of the considerations for what those enhancements and extensions are. So it could be slightly better communication with the customer base that would be my main issue with them. But as a product, it's very difficult to find any major faults.
For how long have I used the solution?
I have been using Tyk for two and a half years. I've worked for organizations where we've basically consumed them, acquired the product, or used it as part of our overall delivery solution.
What do I think about the stability of the solution?
The stability is very good.
What do I think about the scalability of the solution?
The scalability is very good. That was a key factor in the selection, like how it could be pushed to high volume and scalability, which seemed to be very good. We haven't as yet had a need to push it to that extent.
Our clients are mostly medium and enterprise businesses for this solution.
How are customer service and support?
There's always things where we need to go back to. Their support provision is very good, and they do provide routes to make inquiries, self-learn, etcetera.
But, I've never come across anything I would regard as ten, which is almost like I don't need to go to support.
There are things to go to support. That's usually about how to exploit it better rather than anything else.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have worked with Axway and Microsoft.
How was the initial setup?
I would rate my experience with the initial setup an eight out of ten, where one is difficult and ten is easy.
The deployment incorporates all elements, not just Tyk. So, the deployment time also depends on the configuration.
The actual setup can be done within a day. Like Docker and containerized... So the prep's quick, but it's a lot more than Tyk. So, deployment is not a material issue.
What about the implementation team?
We were the third party. We helped the clients with the deployment process.
What was our ROI?
It's hard to put a mark because the overall solution involves more than just Tyk. Tyk is just one component, so the ROI the customers see is on the entire system, not individual parts.
What's my experience with pricing, setup cost, and licensing?
The pricing is actually quite competitive. In Azure environments, it gets beaten by Microsoft API Gateway, but on the other hand, it offers some features that Microsoft lacks. So it really comes down to cost-benefit in the end.
I would rate the pricing a three out of ten, where one is cheap and ten is expensive.
What other advice do I have?
Understand the projected or expected growth rate, the nature of your API usage, and any industry-specific support available from Tyk or its competitors. Some tools are better suited for certain market sectors.
Most importantly, focus on the total cost, including anticipated server growth, not just call volume growth.
Overall, I would rate the solution an eight out of ten.
Tyk is an enterprise-ready open source gateway solution.
What do you like best about the product?
Tyk is an open-source platform that also supports identity providers with custom middleware solutions.
What do you dislike about the product?
More documentation needs to get added from the point of view of a developer
What problems is the product solving and how is that benefiting you?
We did a proof of concept (POC) with an open source gateway solution to test a multi-tenant solution. The API was built in Node.js, and Keykloak was used as identity provider.
Good product and lots of documentation available
What do you like best about the product?
We implemented an integration project with AWS Cognito that worked quickly and in which their support team helped us at all times. Additionally, the documentation on their website and all the videos they offer are very useful. They have many possibilities for securing APIs.
One of the standout features of Tyk API Gateway is its user-friendly interface. Setting up and configuring the integration was a breeze, thanks to an intuitive dashboard that allowed for quick and easy management of APIs, access control policies, and rate limiting. The overall user experience is excellent,
One of the standout features of Tyk API Gateway is its user-friendly interface. Setting up and configuring the integration was a breeze, thanks to an intuitive dashboard that allowed for quick and easy management of APIs, access control policies, and rate limiting. The overall user experience is excellent,
What do you dislike about the product?
The web interface is not included in the opensource version, although they offer temporary licenses for its use.
What problems is the product solving and how is that benefiting you?
Tyk API Gateway simplified the task of API management and security configurations
showing 1 - 10