Axway AMPLIFY API Management vs SwaggerHub comparison

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

"Centralized API Platform allow us better reusability and monitoring"

"This platform can be highly scalable."

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

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

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

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

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

"Since I started using SwaggerHub, it has had a positive impact on our organization due to better collaboration between developers and the quality assurance team, and it has reduced errors because of its automated validation."

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

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

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

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

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

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

"It is a stable solution."

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

"The API Mocking tools need to be improved."

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

"Not a ten because of the pricing and technical support."

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

"The portal still has room for improvement."

"They should also improve the way that we upgrade from one version to another. In our case, it's been very troublesome."

"Team management capabilities could be improved."

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

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

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

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

"The customization and doc formatting options for documentation pages are restricted in SwaggerHub."

"In SwaggerHub, I appreciate that it is a powerful platform for API design and collaboration, but currently, the access control is somewhat limited."

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

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