Axway AMPLIFY API Management vs SwaggerHub comparison

"We like the portal for documentation a lot."

"The UI and UX are quite good and easy to understand."

"I don't believe the Salesforce has been fully utilized yet. It gives us quick engagement."

"This product is reliable and stable."

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

"Its flexibility allows us to adapt to different scenarios."

"The API portal capability is a valuable feature."

"For what we do, the API portal capability is the most valuable feature."

"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 has significantly improved how my organization designs, documents, and manages APIs, centralizing API management so that all API definitions are stored in one location, which makes it easy for stakeholders, developers, QA, DevOps, and products to access the latest version."

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

"SwaggerHub plays a crucial role in order to bring teams and automate things faster and also reduce the man-hours and increase the work efficiency."

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

"It is a stable solution."

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

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

"Areas of improvement include marketing and enhancing the data products area by using ETIs."

"A significant area of improvement for Axway AMPLIFY API Management is the Amplify Central portal, which should help expose APIs on a webpage for potential customers."

"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 areas for enhancement should be improving certain filters within the solution. Although they are generally functional, there are occasional problems that could be more precisely adjusted. Additionally, the solution performs well within its workload limitations, but it may not be suitable for scaling up or managing a larger volume of transactions through the gateway. To address this, it may be necessary to adopt a unique architecture rather than relying on traditional pre-packaged options."

"We sometimes have issues with some of the functions because they do not work very well."

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

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

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

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

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

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

"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 could be improved with better integration for tools."

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

"The tool is cheap."

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