Axway AMPLIFY API Management vs SwaggerHub comparison

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

"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 API portal capability is a valuable feature."

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

"This platform can be highly scalable."

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

"The administration tool for this solution is good."

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

"The scalability is endless."

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

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

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

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

"Team management capabilities could be improved."

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

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

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

"Sometimes we find bugs where certain calls are not returning all the data we need."

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

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

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

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

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

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

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

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

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