Akana API Management vs SwaggerHub comparison

"It allowed us to publish and replace pre-essential transactions in one place, with a uniformity in terms of control and policies."

"The tool's authentication mechanism is easy to implement. We had to define a few parameters."

"Good interface, intuitive solution."

"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 scalability is endless."

"It is a stable solution."

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

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

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

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

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

"Lacks an integrated billing feature."

"Akana API Management needs to improve its documentation."

"The product has new features that we are going to implement in the next few months, such as API management and analytic reporting."

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

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

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

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

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

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

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

"For us, the pricing and licensing policies were for an on-premise installation with a fixed cost structure, that matched our budgeting policies."

"The tool is cheap."

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