Tyk Cloud, Hybrid & Self Managed API Management logo

    Tyk Cloud, Hybrid & Self Managed API Management

    Tyk is a high-performance API gateway and full lifecycle API management platform built for enterprises and engineered for scale. The Tyk platform provides governance and tooling for API design, security, governance, and automation, enabling teams to build, scale, govern and automate APIs efficiently while minimizing operational overhead. Built for open standards, enterprises can accelerate development, drive innovation, and create differentiated digital experiences through open standards and a scalable architecture.

    Ratings and reviews

    4.4
    64 ratings
    2 star
    1 star
    66%
    33%
    1%
    0%
    0%
    4 AWS reviews
    |
    60 external reviews
    External reviews are from G2  and PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (64)
    Consulting

    Our new Enterprise AI Gateway

    Reviewed on Oct 30, 2026
    Review provided by G2
    What do you like best about the product?
    We major on Kubernetes, and Tyk makes it straightforward to manage that infrastructure as code while covering both AI and APIs. Our team lives in CI/CD pipelines, not GUIs, and Tyk really fits that way of working. As we roll out more LLM capabilities internally, we expect to make even more use of the Tyk AI Gateway.
    What do you dislike about the product?
    They really need better documentation. The information is there, but it’s confusing and not laid out in a clear way. I also wish the operator were more fully featured, especially when it comes to the Developer Portal.
    What problems is the product solving and how is that benefiting you?
    We needed a fast way to get a single cohesive view of API and AI consumption and we needed a single data plane to enforce access. Now all of that is visible in Open Telemetry dashboards, so we're getting on top of governance and reducing risks. We can also see more about who is spending what on AI
    Banking

    Easy API Configuration, Granular Controls, and Fast Support

    Reviewed on Oct 29, 2026
    Review provided by G2
    What do you like best about the product?
    The user interface makes it easy to configure the API and manage analytics. It also offers multiple middleware options for request and response transformations. The configuration is very granular, yet straightforward to integrate, and it delivers efficient performance. The user support team is also quick to respond.
    What do you dislike about the product?
    Enterprise features such as request encryption and signing have not yet been integrated. It would also be better if observability-related features were added directly in the dashboard itself, so users can manage all API configuration and see their running data analytics and logs within the same dashboard.
    What problems is the product solving and how is that benefiting you?
    Tyk performs quickly and offers a variety of options for managing APIs, including the UI, API, and operator. The dashboard also provides a good user experience for consumers.
    Viral S.

    Flexible, Lightweight API Management Built for Hybrid Cloud and Kubernetes

    Reviewed on Oct 29, 2026
    Review provided by G2
    What do you like best about the product?
    What I like best about Tyk is its flexibility, lightweight architecture, and ability to support scalable API management across hybrid and cloud environments. Its API-first approach, strong security capabilities, flexible policy management, and support for automation make it well suited for enterprise platforms. I also value its Kubernetes compatibility, deployment flexibility, and integration with CI/CD pipelines, which help teams standardise API onboarding, improve operational efficiency, and enable self-service adoption across multiple teams.
    What do you dislike about the product?
    While Tyk offers strong flexibility and API management capabilities, some areas could be improved, particularly the usability of the management interface, troubleshooting experience, and visibility into operational issues across distributed deployments. More comprehensive documentation and practical examples for complex enterprise use cases, along with simpler configuration and debugging workflows, would help reduce the learning curve and improve the overall developer and operator experience.
    What problems is the product solving and how is that benefiting you?
    Tyk solves the challenge of managing, securing, and governing APIs consistently across distributed teams and hybrid cloud environments. It provides a centralised approach to API authentication, authorisation, traffic management, rate limiting, and access control, while enabling teams to expose APIs in a standardised and controlled manner. This benefits me by improving platform security, simplifying API onboarding, promoting self-service adoption, reducing manual operational effort through automation, and enabling consistent governance across teams. It also supports scalability and operational efficiency while allowing flexibility in deployment and integration with existing enterprise infrastructure and CI/CD pipelines.
    Ananda B.

    Tyk Delivers Ultra-Fast Performance, Deep Observability, and Promising MCP for AI

    Reviewed on Oct 29, 2026
    Review provided by G2
    What do you like best about the product?
    Tyk has been an integral part of our API management and transformation journey for a couple of years now. Tyk’s biggest strengths are its performance, observability, and evolving capabilities for AI integration.

    We use Tyk as a self-managed platform, replacing MuleSoft as our internal API gateway. So far 16-20 teams have adopted the gateway, with more in the queue.

    Performance: Tyk is an ultra-fast, low-latency API gateway. In our testing, the platform has been validated at 10,000 requests per second, making performance a key strength for enterprise API traffic.

    Logging and Monitoring: The Tyk Dashboard provides valuable visibility into API traffic, including success and error rates at both API and API-key levels. This helps teams monitor API health, identify issues, and understand usage patterns more effectively.

    AI and MCP Capabilities: Tyk’s introduction of MCP support is particularly promising. The ability to extend API gateway security and governance capabilities to AI tools and agent-based interactions, while maintaining authentication, authorization, logging, and monitoring, is a valuable step towards secure enterprise AI adoption and Intelligence at scale.

    Overall, Tyk combines high performance and operational visibility with capabilities that can support the next generation of API and AI-driven platforms.

    We are also looking to use Tyk’s MCP capability in our AI and Intelligence initiatives, to provide secure communication from agentic chatbots to the different tool sets available across the organization.
    What do you dislike about the product?
    Tyk works well as a federated model, but the data plane components need to be tested carefully to suit your specific performance needs. With that effort up front, the results have been very strong for us.
    What problems is the product solving and how is that benefiting you?
    We run a strong microservices ecosystem across the organization, and operating at that scale requires a gateway with best-in-class authentication and performance.

    Our previous integration toolset had two main issues. First, it created heavy vendor lock-in. Second, it relied on a lot of custom tooling built around specific needs, which deepened that dependency and made the platform harder to evolve. We wanted to move away from this model. We also wanted a Kubernetes-native gateway that runs in our Kubernetes environments out of the box.

    Tyk met these needs: it is Kubernetes-ready, its performance benchmarks are well tested, and it gave us a clear path away from vendor lock-in.

    We built reusable pipelines for API onboarding and for infrastructure setup, working consistently across both cloud and on-premises environments. This cut API onboarding time by around 70%. We also reduced our dependency on any single tool, which brought down the cost of running the platform by around 40%.

    Quantified benefits

    API onboarding time reduced by around 70%
    Platform cost reduced by around 40%
    Consistent deployment across cloud and on-premises
    Reduced vendor lock-in and less custom tooling to maintain
    Financial Services

    Reliable gateway that brought order to 1,000’s of APIs

    Reviewed on Oct 15, 2026
    Review provided by G2
    What do you like best about the product?
    We were looking for a platform that handles AI and API workloads. We moved about 140 internal and partner APIs onto the Tyk Gateway over six months. What I like most is how much we can do declaratively — rate limits, quotas and JWT auth are set per API in config we keep in Git, so changes go through the same review as our code. Latency overhead has been negligible for our traffic (we measured low single-digit milliseconds at p95). The Developer Portal also cut partner onboarding from a ticket-and-wait process to self-service.
    What do you dislike about the product?
    The learning curve on advanced policy and plugin configuration was steeper than we expected — the docs cover the common cases well, but we needed support's help for a couple of edge cases around custom Go plugins. Planning major-version upgrades also takes care across multiple environments. Support was responsive when we raised both, but better worked examples for complex set-ups would help.
    What problems is the product solving and how is that benefiting you?
    We’re building cutting edge AI infrastructure for a global financial institution. Before Tyk, each team secured and exposed its own APIs, so auth, logging and rate limiting were inconsistent and audits were painful. Now every API goes through one gateway with standard policies, which gives our security team a single place to check. Partner integrations that took three to four weeks to set up now take a few days, and we've retired home-grown proxies we were maintaining.
    reviewer2900325

    Improved API monitoring has standardized authentication and reduced manual administrative work

    Reviewed on Sep 18, 2026
    Review provided by PeerSpot

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have been using Tyk for about four years.

    What do I think about the stability of the solution?

    This tool seems stable in my current environment.

    Which solution did I use previously and why did I switch?

    Before adopting Tyk, I did not use another solution.

    What was our ROI?

    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.

    What's my experience with pricing, setup cost, and licensing?

    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.

    Which other solutions did I evaluate?

    I did not evaluate other options before choosing this tool.

    What other advice do I have?

    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.

    Svetoslav Georgiev

    Modern API workflows have accelerated delivery and now need clearer security and AI governance

    Reviewed on Aug 26, 2026
    Review from a verified AWS customer

    What is our primary use case?

    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

    How has it helped my organization?

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

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

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

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

    My impression is that Tyk is pretty capable and scalable.

    How are customer service and support?

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

    Which solution did I use previously and why did I switch?

    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.

    How was the initial setup?

    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.

    What about the implementation team?

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

    Which other solutions did I evaluate?

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

    What other advice do I have?

    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.

    SaurabhKumar10

    Secure banking APIs have protected sensitive transactions and support daily compliance monitoring

    Reviewed on Aug 25, 2026
    Review from a verified AWS customer

    What is our primary use case?

    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.

    What is most valuable?

    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.

    What needs improvement?

    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.

    For how long have I used the solution?

    I have been using Tyk for the past four years.

    What other advice do I have?

    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.

    Which deployment model are you using for this solution?

    Public Cloud

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Gilson Watanabe

    Gateway has improved API security and has simplified authentication and rate limiting concepts

    Reviewed on Aug 07, 2026
    Review provided by PeerSpot

    What is our primary use case?

    At the time, my main use case for Tyk was more for security and exposure matters related to business. Part of what I was trying to solve with Tyk was authentication, access control, request volume, protection, and a bit of protection against code injection such as SQL Injection, and from there on it was already extras.

    What is most valuable?

    In my opinion, the best features that Tyk offers were the rate limiting and authentication themselves.

    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.

    What needs improvement?

    I cannot really say much about Tyk because it has probably already improved significantly since the last time I used it. I chose the number eight because I think at the time I ended up using the version and I had not found, or there was not, a way for me to install it locally to study and learn a way of using the tool.

    For how long have I used the solution?

    In IT itself, it has been more than twenty years, but in software architecture specifically I would say it has been at least about fifteen years.

    What do I think about the stability of the solution?

    Tyk was stable even during the tests I performed.

    What do I think about the scalability of the solution?

    I did not run any tests regarding scalability or performance, and I did not run any test in that sense.

    How are customer service and support?

    I was well served regarding customer support during my evaluation period, but I only used email contact at the time. Regarding questions themselves, not necessarily support, I used only the official documentation available on the website itself.

    Which solution did I use previously and why did I switch?

    I evaluated other options before choosing Tyk. I had evaluated Axway's, IBM's, Kong's, Google's, and I think a couple more that I do not remember off the top of my head.

    How was the initial setup?

    Tyk was implemented in my environment during this evaluation period in the provider's own cloud.

    What was our ROI?

    In terms of return on investment, it was more in terms of learning, as it was the tool that I suggested to other people to start learning and using the concepts of. It was more in the sense of knowledge sharing itself.

    Which other solutions did I evaluate?

    I did not use a different solution for this type of need yet; it was a proposal exactly to choose a solution for that.

    What other advice do I have?

    As it was more experimental, I also did not end up using it in production or in real cases. As it was in isolation, I do not have anything to add, but probably if it had gone ahead there might have been some integration with the company's security control. It is difficult to say regarding advice I would give to other people who are thinking about using Tyk. As it has been a long time since I did this evaluation, probably a lot has changed since then, and I do not think I have anything else to add beyond what has already been asked. I would rate this review an eight.
    Lew M.

    Full-Featured API Gateway with Powerful Open-Source and Pro Capabilities

    Reviewed on Aug 06, 2026
    Review provided by G2
    What do you like best about the product?
    First, it has full-fledge of capabilities, such as api routings, rate limiting, middleware etc. Second, it has both open-source and professional. Even open-source version is full of useful functionalities.
    What do you dislike about the product?
    Last time I use Tyk (not open-source), and it requires a token. Maybe can increase the duration of the token to enhance user experience. It will be helpful for new user to explore the functionality of Tyk.
    What problems is the product solving and how is that benefiting you?
    1. API routing -> route API
    2. Rate Limiting -> rate limit api request
    3. Custom middleware -> custom function adds before/after api request
    4.

    These functionalities help me to solve the development requirements in my job.