3scale API Management vs SwaggerHub comparison

"3scale API Management's best feature is API management."

"The solution is quite lightweight, and the installation is very easy. It's like a two-click installation."

"The product is stable."

"The most valuable features are the gateway and security features."

"I like the API automation."

"It's good that they aren't adding a lot of features like ESP, etc. It's okay with just being a gateway."

"The standard deployment is very simple."

"To me, the most valuable feature of 3scale API Management is that it lets you add a backend to the product. I also like that you can integrate it well with OpenShift clusters, making 3scale API Management a useful solution."

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

"It is a stable solution."

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

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

"The scalability is endless."

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

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

"It would be helpful to improve the customization features so that the customer can do it based on their own needs."

"The user experience could be better. The developer portal is too complex and hard to configure."

"What I'd like to improve in 3scale API Management is its route-limiting feature. Currently, I don't know how to do that effectively on the solution, but in Kong, I know how to do it, so I would love to see route-limiting being easily done on 3scale API Management. It would also be good if there was some authentication that you could do from 3scale API Management because Kong offers that functionality out of the box. What I'd love to see in the next release of 3scale API Management is the ability to integrate more plug-ins easily onto the platform, so you'll be able to extend it, and even do customs management. If Red Hat could offer that extension where it allows the internal organization where 3scale API Management is deployed on-premise to integrate its tools on top of 3scale API Management and provide an API for that, that will make the solution very powerful."

"The product is not that flexible for developers. It's less flexible and rigid. It's not easy to make changes or customize it."

"What was suggested by Red Hat was a crucial part of the configuration, but when we started to ask about the supportability of this configuration, Red Hat said only some parts of the configuration would be supported."

"We tried to use the portal, but we decided that it wasn't enough. The content management system (CMS) is not easy to use if you want to customize things, and it's hard to get someone who has the knowledge to work with the CMS."

"I believe the CMS part of it has room for improvement though. That is where you write a couple of things if you want to publish your API. It's based on liquid scripting, which doesn't seem like the obvious ones to script with."

"3scale API Management only supports restful APIs and doesn't support SOAP."

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

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

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

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

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

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

"I don't think that 3scale is very expensive."

"The pricing is affordable, it's cheap."

"3scale API Management has reasonable pricing, judging from its competitor, Kong. My organization pays yearly for the 3scale API Management license, though I'm unable to give the exact figure because every single day there are new clusters deployed. I'm in charge of three to four clusters in my team, but give or take, it costs a few thousand lakhs."

"The cost was around $45,000 per year."

"The tool is cheap."

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