SwaggerHub vs TIBCO Cloud API Management comparison

"I rate the solution's stability a ten out of ten."

"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."

"The scalability is endless."

"The tool's most valuable feature is licensing."

"The most valuable features are the collaboration between multiple teams and the control and distribution of specifications."

"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."

"It is a stable solution."

"The product's initial setup phase was easy and not at all difficult."

"We can completely manage the APIs at the org level and BU (business unit) level."

"Very few outages or SLA issues."

"The reason why we selected the solution originally was because of its ability to have a gateway both on-premise and in the cloud. This is the most valuable aspect of the solution for us."

"The most valuable aspect of Mashery is its stability."

"It is easy to work with ."

"When we did the product evaluation, we saw that TIBCO Mashery offers end-to-end API life cycle management. It provides all API features that are required for managing the complete life cycle. It includes the developer portal and tools for API monitorization. The out-of-box security features that TIBCO Mashery provides are enterprise-grade, which gives it an edge over other API products."

"The control that we have and the security features are very valuable. With regard to API implementation or API orchestration, it works very well in the cloud because as soon as you create an API with one click, you can actually expose your APIs."

"The platform's most valuable features are its capabilities to support security measures such as tokenization, token refresh, throttling, and enforcement of payloads."

"SwaggerHub's UI needs to be improved as it looks very old school."

"It could be more intuitive compared to one of its competitors."

"The review process should be improved. There seem to be some gaps, at least for us, for the editing part because we would like to have a full request review mechanism. They support some comments, but it is really hard to manage those comments. We would like to use the full request. Therefore, we are now looking to integrate with repositories. It has integration with Bitbucket and GitHub, but we have some internal constraints, and we need to move some of the repositories to GitHub. Our source code is on-premise in Bitbucket, and it was a bit of a problem for us to integrate. Now we are transitioning our repositories to GitHub, and hopefully, we can enable the integration. This will probably solve the problem with the review and approval. Its customization should also be improved. There are limitations around the support for the developer portal. There should be more customization options for the website that you can use as a developer portal. Currently, it has only Swagger UI with minimal customization. You cannot actually add additional pages and documentation for explaining concepts and general things. That's why we have started to look around to see what other tools are doing. They should also allow tagging on the API. We would like to add some tagging on the API to reflect certain things. Currently, any metadata that you would like to have has to be a part of the spec. You cannot do anything else. It should also have support for Open API 3.1, which was released at the beginning of the year. It would be great to be able to switch to that."

"The scalability aspect of SwaggerHub can be improved. It becomes a bit unreliable when the load is increased and isn't up to par with expectations for scalability."

"SwaggerHub could be improved with better integration for tools."

"We have to use additional tools to test APIs."

"It has limited functionality...Unfortunately, some of its features are not what we need."

"More integration and usability with the cloud microservices would be nice"

"They can fix some stability issues and probably make it more user-friendly so that not only an IT savvy person but an end-user can also easily navigate through this solution."

"TIBCO Cloud API Management should improve its installation and make it easy."

"It lacks many features at the API gateway compared to other solutions."

"It's not that user-friendly, and security-wise when you try to implement the security layer on top of it, it's not that easy either."

"The security needs improvement, specifically, propagation of security to an API. Calling other APIs is something that is missing in the product and that makes us think about going to a competitor."

"The management console of API and customers' applications are not the most intuitive."

"There are some areas for improvement in TIBCO Cloud API Management, especially regarding network protocols such as SMPP, SMTP, GVI, SVI, and Diameter which could show performance issues in terms of handling and connection management pooling efficiency."

"Monetization is not that great in API management. You need customization. Improvements are needed with sandbox local as well as with monetization. Those features are missing."

"The tool is cheap."

"It has a yearly subscription, but I am not sure."

"Its price is pretty reasonable. There are some lightweight API options available in the market, but given the feature set that TIBCO provides, its price is really reasonable."

"TIBCO Cloud API Management is not an expensive solution."

"We have secured terms on which we have been happy to renew for a number of years."

"Licensing is quite flexible."