SwaggerHub vs TIBCO Cloud API Management comparison

"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 most valuable features are the collaboration between multiple teams and the control and distribution of specifications."

"It is quite a useful tool. It is quite good with the validation of the spec. It works quite well in terms of errors and conformity to the OpenAPI standard. It is better than Visual Studio Code in terms of editing."

"You can click & play and add the notation in a human-readable form. Spotlight is also very good in the graphical design of APIs."

"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 tool's most valuable feature is licensing."

"It is a stable solution."

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

"Conversion to RESTful and SOAP protocols and management console (can manage individually throttled settings to manage our service levels for customers)."

"The solution is a good general API manager. They have a few propriety features but are offering items that are standard in the industry as well."

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

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

"Very few outages or SLA issues."

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

"It has something called packages. In that way, it's good because we have some pre-built packages. So, if you want to onboard different APIs, we can just add them to the package, and it's there."

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

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

"Some areas of SwaggerHub that could be improved include the interface between the code editor and the visual editor, the integration with private APIs, which currently requires an upgraded account."

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

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

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

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

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

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

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

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

"The way agile life cycle is working needs improvement. I also want to see more support for open API standards. I want to see some improvement on the protocol transformation. That is quite missing now. These are the three main issues."

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

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

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

"We observed delays under heavy load conditions, and without proper tuning, changes could take an extended period to filter and become effective."

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

"The tool is cheap."

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

"Licensing is quite flexible."

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

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