Tyk API Management

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.

What do you like best about the product?

I've been using Tyk for a few years now, and one of the things I appreciate most is how flexible it is. We use it to manage a fairly large set of APIs, and it's been reliable even as our traffic has grown.

The UI is clean enough to get most day-to-day work done without digging through documentation, and for anything more advanced, the API and configuration options give you a lot of control. Integrating with OAuth, JWT, rate limiting, analytics, and different backend services has been straightforward.

Performance has also been solid. The gateway introduces very little overhead, and we've been able to scale without running into bottlenecks. Overall, it strikes a good balance between ease of use and the level of customization backend teams usually need.

The documentation is generally good, but when you're implementing less common integrations or debugging edge cases, it sometimes requires a bit of trial and error. I also think the AI capabilities could be expanded further; for example, suggesting policy optimizations, detecting unusual traffic patterns, or helping troubleshoot gateway configurations would save engineers a lot of time.

Pricing may also feel a bit steep for smaller teams, although for larger deployments the value becomes much easier to justify.

What do you dislike about the product?

There are a few areas that could be improved. While the UI works well for common tasks, some advanced configurations can feel spread across different sections, so it takes time to find exactly what you're looking for.

The documentation is generally good, but when you're implementing less common integrations or debugging edge cases, it sometimes requires a bit of trial and error. I also think the AI capabilities could be expanded further for example, suggesting policy optimizations, detecting unusual traffic patterns, or helping troubleshoot gateway configurations would save engineers a lot of time.

Pricing may also feel a bit steep for smaller teams, although for larger deployments the value becomes much easier to justify.

What problems is the product solving and how is that benefiting you?

Before using Tyk, we had API authentication, rate limiting, and access policies implemented differently across services, which made maintenance difficult and onboarding new APIs time-consuming. Every new integration required additional custom work, and troubleshooting production issues wasn't always straightforward.

With Tyk, we now have a centralized API gateway where security, traffic management, analytics, and integrations are managed consistently. Onboarding new APIs is much faster—we've reduced the setup time by around **40-50%**, and developers can focus on business logic instead of reinventing gateway functionality.

The platform has also been reliable under production traffic, with minimal latency overhead and good visibility into API usage and performance. The built-in integrations with authentication providers and monitoring tools have simplified operations, while the intuitive UI makes routine management easy even for engineers new to the platform.

From an ROI perspective, Tyk has helped reduce operational effort and maintenance costs by eliminating duplicated gateway logic across services. The support team has also been responsive whenever we've needed assistance. Looking ahead, I'd like to see stronger AI-driven capabilities, such as intelligent policy recommendations and proactive anomaly detection, but overall it's been a solid investment for managing APIs at scale.

What do you like best about the product?

Honestly, the thing I like most is that Tyk just gets out of the way and lets us do our job. The open source version already has pretty much everything you'd want in an API gateway. Rate limiting, quotas, JWT and OIDC auth, transformations. So we didn't have to fight for budget just to cover the basics.

We've also gotten a lot of mileage out of the custom plugins. Being able to drop in our own Go middleware for business logic is something I didn't realise I needed until I had it. Self hosting was painless, and it's nice knowing there's no phone home stuff running in the background. Once it was up, it kind of just worked. Uptime's been solid, the dashboard is easy enough that even newer folks on the team can find their way around, and we haven't had to babysit it.

What do you dislike about the product?

The documentation is probably my biggest gripe. It covers the basics well but once you get into anything advanced, like custom plugins or edge cases with auth, you end up digging through GitHub issues or community threads to piece things together. A few more real world examples and video walkthroughs would go a long way.

The learning curve is also steeper than it looks at first. Tyk is powerful, but figuring out how APIs, policies, keys, and security profiles all fit together takes time, especially if you're coming in fresh. And while the dashboard analytics are useful for quick checks, they're pretty basic. If you want proper insight into API usage and performance, you end up pushing data out to another tool anyway.

What problems is the product solving and how is that benefiting you?

Before Tyk, we had auth, rate limiting, and routing logic scattered across different services, and every team was kind of doing their own thing. Tyk gave us one place to handle all of that, so our backend services can just focus on business logic instead of reinventing the same middleware over and over.

It's also made onboarding new APIs a lot faster. Spinning up a new endpoint with proper auth, quotas, and monitoring used to be a whole project. Now it's mostly configuration. The self hosted setup means we keep full control over our data and traffic, which was a hard requirement for us, and the plugin system lets us handle the weird custom stuff without waiting on a vendor roadmap.

Overall it's saved us a lot of engineering time and given us way more confidence in how we expose and secure our APIs.

What do you like best about the product?

I use Tyk as an API gateway to expose our backend APIs securely. I appreciate how Tyk centralizes API management, which is really beneficial. I like the API management features, specifically authentication, rate limiting, and routing versioning, which help secure our APIs and manage traffic efficiently. The initial setup of Tyk was easy, and this tool has really streamlined our processes.

What do you dislike about the product?

n

What problems is the product solving and how is that benefiting you?

I use Tyk to securely expose our backend APIs, centralizing API management. It helps secure APIs, manage traffic efficiently with features like authentication, rate limiting, and routing versioning.

What do you like best about the product?

What i like most about tyk is its simplicity and flexibility if comparing with other tool i have worked on nginx, kong gatewayand traefik as well but the easiness tyk comes up with its excellent also about the pricing part which makes it more valueable. About the interation with our product application is really good. so the overall performance is very good as comparing with other market tools. and the onboarding experience which is self hosting is also seamless as a user point of view.

What do you dislike about the product?

see its best api gateway but that does not make it to fit in every usecase as per my understanding. also if we talk about the community support is less comparing with others. plugin supports seams less and not everyone knows about it.

What problems is the product solving and how is that benefiting you?

every service or microservice has to handle security, rate-limitings and authentication in there code own which make the code duplication and increase the complexicity into business while if we implement tyk api gateway thn we need to focus more on business logics and the purpose our services serves rather making it more security and complex codes.

What do you like best about the product?

I like Tyk for its ease of integration, which makes my work more manageable. The simple UI is another plus, ensuring continued usage and making it easy to fix issues when they arise. The initial setup was also easy, which helped in getting started without any hassle.

What do you dislike about the product?

I think Tyk could improve with more API support and quicker response times. I also noticed there can be drops in responses, which is something I hope gets fixed.

What problems is the product solving and how is that benefiting you?

I use Tyk for API platform management. It unifies multi-vendor APIs, which is a big help. The ease of integration and simple UI ensure continued usage and make it easy to fix issues.

What do you like best about the product?

Firstly the ease of implementation and the docs are readily available plus you can easily switch to previous versions but again the costing is a bit expensive

What do you dislike about the product?

i think its too expensive for enterprise expecially for startups that are just getting started and have less then 50 employees in their organizations.

What problems is the product solving and how is that benefiting you?

i centralized entry point for our backend APIs. Instead of building security, authentication, rate limiting, and traffic controls into every microservice individually, It also speeds up our development cycle significantly because developers don't have to rewrite authentication or rate limiting code for every new service.

What do you like best about the product?

What I like most about Tyk is its flexibility and ease of deployment. It supports both cloud and self-hosted environments, making it suitable for different infrastructure needs. The API gateway is lightweight, performs well under high traffic, and provides useful features like authentication, rate limiting, request transformation, and analytics out of the box. I also appreciate its Kubernetes support and the ability to manage APIs through automation, which fits well into DevOps and CI/CD workflows. Overall, it simplifies API management while giving enough control for complex production environments

What do you dislike about the product?

One area where Tyk could improve is its learning curve, especially for teams that are new to API gateways. Some advanced configurations and policies require time to understand, and the documentation can occasionally lack detailed examples for complex use cases. The management dashboard is functional but could be more intuitive, particularly when managing a large number of APIs. Troubleshooting advanced issues sometimes requires digging through logs and configuration files, so better debugging and observability features would make the overall experience even smoother.

What problems is the product solving and how is that benefiting you?

Tyk helps us centrally manage and secure our APIs instead of handling authentication, rate limiting, and access control separately in each service. It provides a single place to enforce policies, monitor API usage, and manage API versions, which simplifies operations and improves consistency. The gateway also integrates well with our existing DevOps workflows, allowing us to automate API deployments and configuration changes. This has reduced operational overhead, improved API security, and made it easier to scale and maintain our services as our infrastructure grows

What do you like best about the product?

It’s very easy to use and configure. It also offers deployment flexibility, and it’s open source. On top of that, it supports various protocols like REST and GraphQL.

What do you dislike about the product?

The initial configuration requires deep knowledge, and the setup is a bit complex. There also isn’t proper documentation for custom deployments, and this really needs to be addressed.

What problems is the product solving and how is that benefiting you?

We’ve been using Tyk for API configuration, deployments, traffic routing, and security enforcement. We also use it for analytics, and it provides deep visibility into how our APIs are being used.

What do you like best about the product?

I use Tyk as a security professional to control and protect APIs, and I appreciate that it gives me a clean way to manage access, enforce policies, and monitor traffic without overcomplicating things. Tyk centralizes API security and control, making it easier to apply consistent rules and track activity without extra noise. I really like how it reduces the gap between security and delivery, allowing me to have protection in place without slowing down API updates. The most important reason for me to like Tyk is the control it provides without being cumbersome. Tyk handles the security and policy aspects practically, allowing me to focus on protecting APIs without unnecessary complexity. I also find it fairly easy to set up overall, as it becomes straightforward once the initial main steps are complete.

What do you dislike about the product?

I think the learning curve can be improved. Tyk is powerful but some parts take more time to get comfortable with, particularly while setting things up for the first time. The hardest part is the initial setup, especially understanding how the different security and policy settings fit together. It can be better if the early steps are a bit more guided.

What problems is the product solving and how is that benefiting you?

I use Tyk to control and protect APIs. It centralizes security and access management, simplifies policy enforcement, and helps keep an eye on traffic without complicating things. It reduces the gap between security and delivery, ensuring protection without slowing updates.