Tyk Reviews

My main use case for Tyk is that it functions as an API gateway and API management platform in our organization. It is used to secure, expose, manage, monitor, and control API access in an enterprise environment. In our day-to-day operations, Tyk supports our cloud-native and microservice-based architecture application, which consists of multi-backend services that need to communicate securely and effectively. Tyk acts as a centralized gateway between clients and vendors in our application. It works for our mobile app, web application, partner, third-party, and backend services. Instead of allowing users to directly access the backend APIs, all requests are routed through Tyk, which ensures security and scalability.

In one of our projects in banking, we use Tyk to secure our application. Our application belongs to the banking domain and is specifically for the credit card department. I work with the support team for an API hosted behind Tyk API gateway in the production banking environment. My responsibility for that particular application includes monitoring API health, troubleshooting, and analyzing 4xx to 5xx errors and Tyk API logs, and validating backend connectivity. In one incident, we received a report of a customer facing an HTTP 500 error while onboarding through our API. We investigated Tyk gateway logs and traced the request path, which identified a failed backend microservice deployment. After that, we coordinated with the deployment team, rolled back the deployment, restored service, and monitored the API traffic through Tyk to ensure stability, scalability, and security. Additionally, we have a service mesh team that also wanted to use Tyk. They used Tyk support to deploy their application, with us functioning as a control plane and them as a data plane. If they want to use and onboard any kind of API through Tyk, they usually connect with us, and we help them onboard the API through Tyk API for their application.

Regarding my main use case for Tyk, it is very secure, more reliable, and encrypted for the application. If we have a banking application, every request goes through Tyk API, which is much more secure. This is a brilliant aspect of the solution.

Tyk offers many valuable features. For the API, the best features include API security such as API key authentication, JWT tokens, barriers, and OIDC. There is rate limiting and throttling to control how many requests a user can make at one time, such as 100 requests per minute or 1000 requests per minute. API gateway routing and load balancing are handled very smoothly, and API analytics and monitoring are comprehensive. Request-response transformations allow us to track customer ID and monitor how many requests can go to the API versioning. Tyk gives Kubernetes and cloud-native support, including Kubernetes, Docker, and AWS, depending on the cloud-native and cloud-based platform. Logging and troubleshooting capabilities are among the best features.

In terms of product benefits, Tyk secures the credit card API, protects the payment API, monitors transactions, handles traffic spikes, reduces downtime, troubleshoots with failover, and improves application reliability.

Tyk has positively impacted my organization as it is not just an API gateway but has become a critical business platform that helps organizations securely expose, manage, monitor, and scale their APIs in the modern banking domain, fintech, and commercial insurance environments in cloud-native settings. Almost every application communicates through APIs, and Tyk ensures that the API remains secure, scalable, and has high availability.

There are many features in Tyk, but a few things need to be improved from the developer side. Some of the features are a bit slow, but that can be worked on. I believe that the upgrade will come soon.

I have been using Tyk for the past four years.

For the API security and monitoring features in my daily work, if I am working on production deployment and support, the API security task involves investigating 401 unauthorized errors and conducting daily checks, verifying JWT token validity, token expiry validation, and API gateway operations. An example would be an issue where a customer is unable to access the credit card API due to an expired JWT token. API key management is part of my daily activity as well, including creating API keys, managing new consumers, revoking compromised keys, and updating access permissions. We work on access control validation, SSL and TLS certificate monitoring, renewals, and production issues, and conduct security incident investigations as part of API monitoring tasks such as API status and response time monitoring. We use these kinds of services from Tyk on a daily basis.

I have noticed outcomes such as secure and faster onboarding since using Tyk. There are no issues, and it is done in a secure way, using the encrypted method that Tyk uses to onboard the API application for the other teams.

Regarding Tyk's governance and security, it truly follows compliance and security standards, and it is provided through encrypted APIs, API tokens, and security keys, with reliability and encrypted password tokens. Everything is excellent and well-designed.

Concerning Tyk's accuracy and reliability of output, accuracy is really fast, and reliability is also very secure. The accuracy is 99 percent out of 100. The latency for the request response time is excellent and very good.

I would say Tyk is better than other applications as it is much more reliable, secure, scalable, and it delivers faster results for the application. Tyk is not just an application; it is a critical business platform that helps organizations secure, expose, manage, monitor, and scale their applications.

I would rate Tyk an 8 out of 10 because I see they need some improvement on the slowness. Tyk is truly brilliant and the best, but some of the product services are quite slow, not excessively, but that is adjustable. I hope that another fix will come from the developer, and it will work faster.

As a platform architect for contact center solutions, TyK serves as the primary Middleware & API Gateway/Proxy between Genesys Cloud, Salesforce, and other back-end systems at the company.

All customer lookups from the customer front-end portal are converted into REST calls to the back-end system and CRM when customers reach and identify with a particular number. Tyk is being used as an API Gateway via REST interfaces. Similar integrations include converting voice input into a string using Tyk back-end speech APIs, such as Google Cloud Speech-to-Text or Azure Speech Services. The concept remains the same: the front-end passes input, authenticates via OAuth2, and sends it to the back-end; the back-end does the reverse. In some use cases, the input could be decoded and encoded.

The interface has been managed primarily by developers and system analysts from the middleware team, who have configured specific message inputs. It appeared convenient and user-friendly for their agile delivery processes

Flexibility, cost efficiency, and scalability are some of the strategic key benefits worth mentioning

From a security perspective, the authentication methods we have been using and the ability to easily switch between OAuth and OAuth2 are valuable. Tokenization and all pipeline chain controls are important, as is the ability to use standard protocols in the business, such as REST, SOAP,  JSON, AsyncAPI, and MCP for AI agents.

Monitoring, logging, and troubleshooting capabilities are quite satisfying

Again, cost is definitely a key factor. A migration from TIBCO middleware to Tyk was driven by cost in many organizations. What I noticed is that the time-to-market was decent, and colleagues were quicker to deliver certain services and new requests from client platforms. It was a positive and smooth experience overall.

Regarding time-to-market, on average, a new service request would arrive within average two sprints when using Agile delivery. It was much quicker and provided an easy way to test in the environment.

Documentation and consultancy could've been better. In the end, we managed to gather all the information and knowledge needed for my integration from various sources. Structured product information that is accessible to the end technical users can add value. Also, tooling for automated generation of the interface descriptions/agreements would be quite valuable

Occasionally, slower performance and glitches may occur, but several factors could be influencing this.

More information on security concepts and development would have been helpful to me. In the new landscape of AI agents and tools, I am not quite sure about governance. I would like to learn more about the governance model and existing out-of-the-box APIs & features to understand how I can enhance them when needed.

Scalability appears to be good based on what I have seen. The API definitions were a little difficult for me to understand, but I am not a developer. There were some problems with rate limits, and in certain cases, the capacity was in question. I believe this has to do with proper scalability and upgrades across the entire cluster, since Tyk itself was not hosted within the company but in the cloud.

I migrated my systems and started using TyK in 2022, marking four years of use.

Tyk is stable and exceeded expectations. Still, certain glitches can occur mentioned earlier

My impression is that Tyk is pretty capable and scalable.

The support is good, but we go through an integrator, so the support is not directly to Tyk as an organization.

The company has been using TIBCO middleware and Data Power for quite some time. It was primarily based on SOAP, not on REST or other services. It was an on-premises solution that worked very well and met the enterprise integration needs, but was occasionally difficult to implement and significantly more expensive than Tyk.

The transition was smooth overall. It was flexible and an open-source product that exceeded my expectations when the migration was initiated and the product was chosen. The migration, which was a phased approach, was positive and flexible. I rate the product between a seven and eight out of ten for overall quality. There are several improvements that I would expect to meet enterprise organization needs, but overall it was a positive experience.

The implementation was handled through a service integrator that my company was working with.

Tyk was cheaper than some alternatives. The cost indications were pretty positive, and the pricing was provided by a third-party supplier.

I would rate Tyk a  solid seven (+) out of ten overall.

I have the feeling that I do not have enough information or insight into certain features, but I know that Tyk provides multiple authentication mechanisms, including API keys, OAuth2 (which I used primarily), and basic authentication for some things. With AI and the new world of AI, I believe we will see an increasing need for fine-grained access, down to the endpoint or even the message control protocol level. I know that Tyk has a gRPC gateway that I am not familiar with, and perhaps this is in the right direction. Access lists, customer-specific IP restrictions, and policies are all in the right direction. However, as with any organization, we are still in the early implementation stages and will likely face some challenges. Security has become a major problem. There has been a recent major security breach in which Tyk has also been part of the pipeline.

Regarding AI capabilities, I have limited experience, but I believe Tyk covers the main needs and is a generic product in that sense. I would be curious to learn more about it, and I would be happy to receive more input from the company, or at least a reference where I could find information about its capabilities. For example, how AI could be used in building up services within AI. I cannot provide further input on that yet, but I am open to learning more.

I would expect Tyk and Salesforce to have more specific, service-oriented collaboration. I have noticed some challenges for my middleware colleagues when implementing services and invoking Salesforce and customer custom back-end APIs, though nothing in particular.

What I felt with the implementation of Tyk is that it required fewer senior and more deep experts in middleware development and architecture. A less complicated product implementation meant fewer deep-custom-knowledge experts were needed. This is positive feedback because it looks like a more comprehensive and modern product. In the previous situation, much more deep custom knowledge was required.

My advice would be to have clear use cases and do the homework well in advance. I mean to prepare for the selection process and to look not only at the current set of features but to discuss what is on the roadmap, expected growth, and especially the API needs, how things are going, the cost model, and the licenses. These are generally important inputs for the selection process.

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 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.

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.

I have been using Tyk for around three years.

Tyk is stable.

Tyk's scalability is impressive; it processes millions of transactions for our internal APIs, and we have never faced any scalability issues.

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.

Positive

We have not switched from Tyk.

We evaluated WSO2, and the customer was using Azure Cloud before choosing Tyk.

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.

Connecting APIs securely with load balancing is my main use case for Tyk. Our applications connect to the AWS cloud microservice from the UI layer to the backend layer, so instead of exposing the actual backend API layer, we are having the proxy layer handled by Tyk. The UI accesses through Tyk to get the backend data necessary for the user to display.

Tyk is high performance and open source enterprise API gateway. Its high performance and open source aspects have benefited my work as it is extremely light and incredibly fast to deliver the response.

Tyk has granular traffic control, fine-tuned for rate limiting, request throttling and fixed quotas for API key or user. Our organization has been using Tyk for a very long time as a major API management platform.

Tyk allows teams to define specific traffic routing, authentication methods, and security policies for individual versions of an API.

There are some architectural bottlenecks, including operational complexity and multi-component overhead. Unlike single binary modern alternatives like Traefik or Zuul, running a production-ready Tyk instance requires orchestrating an expensive web of infrastructure dependencies. Tyk could improve by consolidating state management, reducing reliance on dual data layers for embedding lightweight default storage to simplify local development and horizontal scaling.

Under heavy production workloads involving complex request transformation, Tyk could performance tune by tightening Go's garbage collection allocation under high connection concurrency or optimizing the internal cryptographic engine for mTLS token validation.

I have been working with Infosys for the past eleven and a half years.

Tyk is stable.

Tyk is performing well, and if we need more Tyk servers, it is automatically scalable.

Tyk's customer support has been quite good. I would rate the customer support an eight on a scale of one to ten.

Previously we have used Google Gateway, and then we migrated to Apache API Gateway.

We usually upgrade Tyk when there is a patch activity or maintenance that has been available and recommended for production. We usually maintain the system up to date with the latest versions, approximately two times per year.

I do not have a complete picture because I am a vendor company working for an external organization. We are a partner, a vendor company that is helping an insurance provider.

My experience with pricing, setup cost, and licensing is overall good.

We evaluated and chose only Tyk before selecting.

I have not used the AI capability yet of Tyk, so I do not have a recommendation in that area.

When enterprise applications communicate with public or private LLMs, Tyk intercepts the data payload to enforce strict compliance.

It is very easy for our team to gain Tyk principles because we have external documentation. We have our internal Grafana to monitor all the APIs and right now we are migrating to Dynatrace to monitor all the APIs running through Tyk.

Tyk's documentation and community support is helpful compared to other solutions I have used. Tyk is a wonderful API management gateway for maintaining enterprise-grade applications.

I would rate this review an eight overall.

The positive impact was more in terms of understanding because the other tools I evaluated were harder to understand how to use and how to configure. In that respect, I found it much more intuitive and it helped me better understand the concepts and the functioning itself, which I thought was easier to use. I noticed the ease of configuration and the knowledge itself.

My main use case for Tyk is API monitoring and API Gateway. A concrete example of how I use this tool for API monitoring or as an API gateway in my daily environment is the integration of API specification files inside the gateways in order to see all the flows from point A to point B and to be able to monitor all API calls and requests.

I think the best features that Tyk offers are its visualization dashboard, the robustness of the gateways, and the addition of an extra authentication layer on the requests.

The visualization dashboard and the extra authentication layer make my daily work easier by standardizing API authentication and the different policies that make it possible to grant access to several APIs through a single key.

Tyk has had a positive impact on my organization by saving time through the reduction of manual tasks and monitoring of API flows.

In my opinion, Tyk could be improved by providing the ability to see the different organizations on the dashboard at a single glance. I would also like to see the name of the organization I am connected to in the banner at the top of the dashboard page.

I have been using Tyk for about four years.

This tool seems stable in my current environment.

Before adopting Tyk, I did not use another solution.

I have seen a return on investment since using this tool, with savings in time and resources, needing about two people compared to four before to administer the API solution.

My experience regarding pricing, installation costs, and license management for this tool is that it is slightly expensive for support that is not present enough and difficult to contact.

I did not evaluate other options before choosing this tool.

I rate Tyk overall as eight on a scale from one to ten because of the positive impact it has had on my organization through time savings and resource efficiency.

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.

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.

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.

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.

The stability is very good. 

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. 

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.

Positive

I have worked with Axway and Microsoft.

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. 

We were the third party. We helped the clients with the deployment process. 

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.

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. 

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.

Other than the limitations with the cloud version everything else is fantastic. You can set up workflows and write limited pieces of logic. 

We tried hosting it on our own machines, which we thought would solve the problem, but Tyk, despite being pretty good for the features it claims to support, is still in its early stages, and is still maturing. It's still pretty new.

We ran it for a while, but then we decided to move away from Tyk, because Tyk's cloud version, the SaaS version, has a significant limitation of limited flexibility, so you can't program very much.

If you need anything customized, Tyk's cloud solution isn't for you. On the cloud version allowing customization is something, I'd like to see.

I would like the ability to add custom headers to the request.

I would like to see customizability included. Most API gateways, in my opinion, lack orchestration capabilities. If they can solve that really well, they will be able to quickly rise to the top of the market.

We evaluated Tyk for over a month.

We used the latest version.

We started with the cloud-based version and then moved on to the hosted version.

In terms of stability, we had no issues. In fact, one of our competitors, who also happens to be good friends, has been using Tyk in production for quite some time. It hasn't caused any issues.

We did not test it for scalability yet because we were only running in-house test workloads at the time, and we would have once we knew that all other conditions were met, but because other conditions were not met, we did not move forward with the scalability. I felt, and through my, research Tyk is found to be reasonably scalable. I have also heard this from people who use it.

We only asked one question, and it was resolved within a reasonable amount of time.

I believe they can improve their support for multiple programming languages.

We had found a solution, and we still have that solution, which required the use of an API gateway. We wanted some programming logic to be programmed at the API gateway level. At the time the college chose API Gateway.

That was something we wanted to do, but unfortunately, we desired greater flexibility in terms of our ability to program and wanted to make the best decision, and we chose Apigee, not Tyk or AWS. Apigee provided the best support for that flexibility.

Apigee requires a massive installation, a very bulky installation, which requires a significant amount of maintenance, overhead, and cost. 

The reason we didn't go ahead with the Apigee was that it was becoming very expensive, in terms of license and maintenance costs, as well as setup time. 

We tried Tyk, and a  couple of our client's competitors are already using Tyk, and they are using it pretty extensively. 

When it did not meet with our needs in terms of being able to customize, we looked into AWS API Gateway, which supports that through AWS Lambda, a serverless function, but it has limitations in terms of certain hardbound limitations, such as an API timeout of a maximum of 30 seconds or 10 seconds. I'm not sure what it is. It was also unsuitable for APIs, particularly external APIs that take far too long to respond. As a result, we did not proceed with any API Gateway. Instead, we made use of AWS AppSync. AppSync resolved two of our issues. One is solved by an API gateway, which allows you to connect to any number of data sources over the internet.

It also allows you to have Lambda functions, which you can customize and use to write any custom logic you want in most modern programming languages. Third, because it provides graph scale endpoints, it helped us save a lot of time on our backend development.

We tried it and found it to be quick and easy to set up. The setup time was really, really quick.

The initial setup is very straightforward.

I run a company with its own team of developers. We were also involved in a joint venture with a client.

It does not require a lot of maintenance.

We were the integrators as well as the owners in this joint venture, no third parties were used.

It had a free version, which suited many of our needs, but not all, but we were happy to go ahead with the licensed version as well, which is the paid version.

We are required to pay a licensing fee. There are no additional costs, it was pretty transparent.

To be honest, I don't remember much about the license, but as far as I know, there was nothing alarming.

We compared a few options. We compared Apigee, Tyk, and finally AWS API Gateway. We don't use any of these. We had decided to go ahead with the Tyk, but for some reason, we changed our minds. In addition, we are now utilizing AWS AppSync. It matched our use case better. There are, however, pros and cons of each.

If they are considering an API gateway for a straightforward API gateway case, use case, but if they are considering something more, something that an ESB should support, such as orchestration, transformations, flow management, routing, if those are the capabilities that they are requiring, then it is better to avoid using an API gateway and instead go for a more complex solution, like MuleSoft.

From my experience, I would rate Tyk a six out of ten.

We use this solution to measure, and eventually scale our application programming interfaces.

The portal for developers that this solution provides has great functionality.

We also like the products design of the UX and the UI, which is easy to understand and manipulate as needed.

We would like a better tool for generating documentation for the APIs to be developed.

We have been using this product for nearly four years.

We have found this to be a vary stable solution for use in development.

We believe this to be a scalable product, but we have not yet tested this aspect of the solution. 

The technical support for this product have been very good to date They provide a lot of useful communication, which allows us to fix issues without having to raise tickets.

The initial setup of the solution is straightforward, but it does require configuration work before being deployed.

We are using the open-source version of this product, so there are no licensing costs for its use.

I would advise organizations to start small with the solution, and ensure that the configuration is complete before beginning implementation.

I would rate this solution an eight out of ten.

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.

The most valuable feature is the load balancing with the circuit-breaker function.

The virtual endpoint and distributing requests work well.

It integrated well with other solutions, such as Datadog.

Sometimes when new features are released, they are not immediately stable. It can take a few months for them to catch up completely.

I have been working with Tyk for about three years.

Tyk is really stable and we haven't had any crashes in three years. It is the type of solution that is running all of the time.

The scalability is awesome. Most of our customers are large businesses with a lot of internet traffic. One of our clients installed this product on AWS and the auto-scaling is great.

Depending on the requirements, the solution is sized accordingly. If there are more than five nodes then it is unlimited, so it is very flexible.

The technical support is good. They use a ticket-based system and they respond within two business days, without any SLA.

I used Kong at one point but it was quite some time ago, so I do not have recent experience with it.

The initial setup is straightforward and really easy. They distribute a Docker version, which can be installed within several minutes after a couple of clicks.

Depending on the requirements, this solution can be deployed on-premises, not the cloud, or in a hybrid configuration.

We deployed this solution for our customers, and one person is all that is required.

There are different versions and plans available depending on the requirements, so there is flexibility in terms of the pricing. Compared to other products, this is a cheaper solution.

Our customers are happy with the features and performance, and I have not heard any complaints with respect to technical support.

Tyk only has a single product, so the length of time between updates is really short. For example, if there is a change in a security specification then they catch up quickly.

Overall, this is a good product but they could improve in terms of stability and performance with new updates that are released.

I would rate this solution an eight out of ten.