Oracle API Management vs SwaggerHub comparison

"It is very secure, easy to manage, and easy to configure. It is a web-based API. Moreover, we get direct support from Oracle guys."

"The initial setup isn't overly difficult."

"The security, the authentication, and the publishing qualities are great."

"The most valuable features for us are security and centralization."

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

"It is a stable solution."

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

"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 tool's most valuable feature is licensing."

"One of the best features of SwaggerHub is how it allows me to create APIs and control the evolution of APIs within an organization."

"Oracle should actively seek feedback and tailor the approach to client needs. It shouldn't always be about pushing additional products."

"Before gaining experience with the product, I found that it was not simple to use and things took longer to do than I had anticipated."

"We'd like it if they could reduce the cost without sacrificing on features."

"From an administration and developer point of view, the user interface and user experience are not great."

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

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

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

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

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

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

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

"Oracle is not a cheap solution and it is not affordable for all of our clients in Portugal."

"The tool is cheap."

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