Axway AMPLIFY API Management vs SwaggerHub comparison

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

"We like the portal for documentation a lot."

"The most valuable feature of the solution is security."

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

"The API portal capability is a valuable feature."

"There's drag and drop functionality so that you do not need to have a senior expert developer to make use of the tool. You can get more of your staff trained up to be able to use it as it's not overly technical."

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

"In general, API governance provides a better experience for providers."

"It is a stable solution."

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

"The scalability is endless."

"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 product's initial setup phase was easy and not at all difficult."

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

"The API Mocking tools need to be improved."

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

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

"Team management capabilities could be improved."

"The portal still has room for improvement."

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

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

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

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

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

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

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

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

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

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

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