Axway AMPLIFY API Management vs SwaggerHub comparison

"We like the portal for documentation a lot."

"It provides very strong security functionality to protect information in an easier way."

"This platform can be highly scalable."

"The most valuable features are security enforcement and throttling."

"The API portal capability is a valuable feature."

"The best feature of Axway Amplify API Management is its exceptional level of security, which is highly reassuring, coupled with its remarkable capacity to handle substantial volumes of data in impressively efficient turnaround times."

"This product is a ten when it comes to API management."

"Axway is a good product according to Gartner which is why we started to adopt it."

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

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

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

"Normally, they publish their APIs on SwaggerHub for seamless integration with SmartBear and ReadyAPI, which allows us to perform detailed end-to-end automation testing."

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

"The best feature that SwaggerHub offers is the collaboration capability that helps us the most across all of our teams, as we have a single API infrastructure but several teams working in different areas of these 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."

"SwaggerHub is helping with team collaboration, as all the people now know the link, they just go there and get the information they need, and it is really a documentation tool for sharing documentation information about the API we support."

"The product shows a lack of maturity. The setup is difficult, the tech support and community are lacking, and it is not very stable."

"The installation process is a bit complex and it could be a lot simpler."

"It would be great if they have an asset report. It's hard to get support for that."

"The product shows a lack of maturity. The setup is difficult, the tech support and community are lacking, and it is not very stable."

"Ultimately, from a very high-level overview, cloud platforms or Kong could have a slight advantage when compared to Axway AMPLIFY API Management."

"In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better."

"Axway's queuing messages could be enhanced."

"This solution does have some limitations regarding the deployment model."

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

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

"At some point, we were missing some tagging of the APIs, and we could not do that."

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

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

"One of the most difficult things about SwaggerHub is the user interface and its usability, as it can feel quite complex and require too many clicks for simple actions."

"SwaggerHub can be improved since the API testing features are limited compared to Postman, and it is somewhat expensive for small teams as paid plans cost a lot."

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

"The solution is expensive. When you acquire a license you have full access to the solution, unlike other competitors such as Apigee X, where there are fragmented licenses. Some licenses only allow access to certain features while others allow access to more features. Upon procuring this solution's license, you will have full access to the solution, allowing you to experiment with all of its features."

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

"The tool is cheap."