Tyk Cloud, Hybrid & Self Managed API Management

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

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.

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.

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.

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 .

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.

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.

Hybrid Cloud

Microsoft Azure