Axway AMPLIFY API Management vs SwaggerHub comparison

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

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

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

"The administration tool for this solution is good."

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

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

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

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

"The scalability is endless."

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

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

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

"It is a stable solution."

"Code generation is one of the important features of SwaggerHub. We design our API, and we can generate a very rich codebase and add to it. The code generation feature is very valuable."

"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 installation process is a bit complex and it could be a lot simpler."

"The API Mocking tools need to be improved."

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

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

"SwaggerHub's UI needs to be improved as it looks very old school."

"SwaggerHub lacks in terms of integrations. They have APIs integrated, and they also have some connectors, but they don't have integration with many of the things that we use. For example, for connecting with SVN, we had to implement external scripts. So, they should work on the integration because currently, we have to work on the integration with our DevOps, continuous delivery, or continuous deployment. It would be great if these integrations are built-in. Mainly, we would like it to integrate with SVN and Jira."

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

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

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

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

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

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

"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 management considers it a bit expensive. At first, we wanted to purchase a license for 100 users, but we went for a license for only 15 users. Its cost is $10,220 per year."

"The tool is cheap."

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