WSO2 API Manager Reviews

My major use cases for WSO2 API Manager are mainly for system integration between multiple layers because we are working on the middleware layer between the systems.

WSO2 API Manager has everything that any API Manager product could have. This is the best thing to say about WSO2 API Manager, as it has everything I needed.

The Lifecycle Management feature helps me manage my APIs when I'm using it. Additionally, it has a scoping feature that not every API Manager product has. This is a feature that can be considered an add-on or something extra that WSO2 API Manager has, and other products might not have because it is not a mandatory feature.

Regarding WSO2 API Manager, I have no drawbacks or areas for improvement. However, regarding the Micro Integrator, I had some issues while developing complex services because it was mainly designed to be used for simple services, not complex ones. While using complex services, I encountered some issues. I communicated this with WSO2, and they released other products that solved everything related to my concern. These products were released before my concern was raised. When I explored them, they were pretty good, and I did not see the same issues I had experienced. WSO2 is enhancing themselves, and their products are fine. The previous concern was about the previous product, so it is resolved now since there are new products available.

I would like WSO2 to improve quality or response time in support, or both.

I have been using WSO2 API Manager and the Micro Integrator for three years.

I do not face any issues regarding API security from OAuth 2 based authentication. It is secured and well-secured, and I have not faced any security-related issues.

The issues I have faced with WSO2 were more related to the environment, not the product itself. If you do not have a stable environment with enough resources and everything else in place, whatever product you are using will go down. What I faced was more related to the environment, not the product.

For the cases I have experienced, WSO2 API Manager is easy to scale. I did not face any issues, though I have not worked on everything. In the cases I worked with, it was easy and I did not face any issues.

I believe the technical support from WSO2 is better than other support. They are good in their support.

The support is an important thing because not every company or every middleware product company or integration product company has advantages in this point. If a company has an advantage in support, it would be exceptional. I believe the support is a significant strength for WSO2.

I have dealt with TIBCO Mashery before, but it is now sold out to Boomi, and its name is now Cam. I explored it but did not work deeply using it. It is good, and I do not have any concerns. I also worked with Software AG API Manager product. I believe it is sold out now to IBM, though I am not certain if this information is correct. They were good, and I did not have critical comments when I explored them, but I did not work deeply with them.

Regarding TIBCO Mashery, there were a lot of concerns, but since it is sold out now, there is no need to mention the pros and cons because the support will end in October 2026. It was missing a lot of features. Regarding Software AG's API Manager product and Boomi, I believe the only difference is about the design and how to deal with it, but they are not missing main features.

WSO2 API Manager is really easy to install and deploy. This is the main thing that anyone can install and use WSO2 API Manager. In other products, it is much more complex and needs experts. WSO2 API Manager was open source from the beginning, so the documentation was everywhere, and it was easy to install, deploy, and do everything else. For other products, they require expertise.

We worked in all environments for WSO2 API Manager installations. On-premises, hybrid, and cloud. The installations in WSO2 were on-premises. For TIBCO Mashery, it was on-premises and cloud.

I believe WSO2 API Manager is able to save time or money for the client in terms of ROI. I believe this point is applicable for all the middleware or integration products as they are all saving a lot of time. I cannot give a specific rate, but there is definitely saving in time and efforts since you have a middleware layer using integration products. Since you can scale it and maintain your work, it is effective.

The thing that I hoped WSO2 had in their integration products, not WSO2 API Manager, was AI agents, and now they have this. I believe at this stage, they have the things that the market is going through. I did not use the analytics capabilities on WSO2 API Manager. I only used it to publish APIs and to develop and publish APIs, but I did not use any analytics features.

I did not use the fine-grained access control feature. From their marketplace, I did not explore it before, so I did not explore it. My overall rating for this review is 8.

WSO2 API Manager is a cumulative security-based software, and I had a good experience with it.

We could easily deploy APIs on WSO2 API Manager, and CORS configuration was easy to manage. The solution's analytics capabilities were good. It had a robust mechanism and was easy to use. It was also easier to change anything from the back end.

In WSO2 API Manager, we had little flexibility and were restricted to a specific software or tool. The entire API publication or API creation was done using a particular pipeline we had developed. It was automated in our organization, but it would be really great to have a pipeline rather than doing manual entries.

I'm aware that WSO2 has some Groovy scripts that can be run to create the APIs. However, we can improve it and make it more user-friendly or easy to use.

I have been using WSO2 API Manager for three years.

There were certain glitches in the solution. Although the solution did not provide 100% stability, it was around 85% to 90% stable.

I haven't worked much on the solution's scalability, but it was good to manage. We hired 10,000 to 12,000 APIs and managed them in real time. We were not dissatisfied with that aspect.

We had great technical support from WSO2, and it was really satisfactory.

I have used WSO2 Store and WSO2 API Manager at the architecture level. I worked on two versions, namely WSO2 API Manager 2.6.0 and 5.7.0. I have also worked with WSO2 Identity Server versions 5.7 and 5.11.

There are certain things that Apigee handles better than WSO2 API Manager. The user interface of WSO2 API Manager is much easier than that of Apigee. The scope of flexibility was much greater in Apigee. In WSO2 API Manager, we had little flexibility and were restricted to a specific software or tool. On the other hand, we had the scope of customization in Apigee.

The solution's initial setup is easy when you go through the user manual. Although we faced some challenges and made numerous rollbacks, the installation process was normal overall. It took around four and a half hours to deploy the solution. One to two people with good insights are enough to deploy the tool.

We had a good technical support team that helped us whenever we were stuck. We had real-time support for migration and real-time fraud issues. We used to get the support even late at night. The best return on investment we got was the human support rather than the technical support.

I don't have much information on the pricing because it was handled by our finance team. As far as I'm aware, the costs are not minimal but satisfactory.

The WSO2 team from Sri Lanka helped us with everything. We used to reach out to them via the WSO2 dashboard for maintenance. We used to raise tickets and have maintenance expertise and guidance on this dashboard.

Overall, I rate the solution an eight out of ten.

Positive

We use WSO2 API Manager for our microservices and our APIs, both internally and externally.

Using WSO2 API Manager, we were able to create one API and use it for multiple channels. Previously, without using microservices or an API manager, codes and functions were duplicated across different systems. This resulted in significant cost savings in development and deployment of applications.

The most beneficial feature of WSO2 API Manager is its capability to use Swagger to define and then populate the API. The security features are also valuable, allowing customization of encryption, decryption, and identity authentication. Additionally, being able to create one API for multiple channels and eliminating duplicate codes provides significant development and deployment cost savings.

One area for improvement is monitoring. Dashboards for application monitoring of the APIs would be beneficial, allowing us to check for faulty APIs.

We have been using WSO2 API Manager for at least five years.

WSO2 API Manager is relatively stable, although there are instances where it consumes a lot of resources when unable to connect to the API, leading to potential shutdowns.

WSO2 API Manager is highly scalable, rated at nine out of ten. It can scale horizontally and be deployed on a Docker environment, which is favorable for expanding business demands.

We haven't contacted customer service. We are using the open-source version and do not have the enterprise version.

We reviewed Apigee alongside other API management solutions, however, we chose WSO2 API Manager as it is open-source, mainly due to cost considerations.

The initial setup was done in-house. It was straightforward and took approximately three hours for configuration and deployment.

We have one senior developer who researched and ultimately deployed WSO2 API Manager. The maintenance is also handled by our team, comprising about twenty people.

The use of WSO2 API Manager has significantly improved operational efficiency and reduced costs. By creating one API for multiple channels and eliminating duplicated code across systems, we have achieved substantial cost savings.

WSO2 API Manager is chosen for its open-source nature, which is a cost-effective option compared to other solutions.

We evaluated solutions like Apigee and 3Scale. We chose WSO2 API Manager for its open-source benefits.

I rate WSO2 API Manager at nine out of ten.

I first implemented WSO2 API Manager with Wipro, which then implemented it for some banks, Telcos, and now two major government customers in India, along with one fintech. They primarily use it for the API gateway to create an API marketplace for exposing APIs. Before this, none of our customers had a full-fledged API gateway, so creating APIs was time-consuming. With WSO2 API Manager, they now have an API marketplace where new users can easily access and use APIs. As for API monetization, although one customer has considered it, no one has implemented it yet. The APIs are mainly used internally within the organization across different channels like web, mobile, and third-party connections.

WSO2 API Manager provides strong internal API security, including token-based authentication and HTTPS support for various formats like REST. However, the newer API security features that are emerging are not available yet. They might be in development, but for now, internal API security is well-covered.

WSO2 API Manager could improve by adding external API security features, which is one area where there is room for enhancement. Internally, API security is strong, and all other necessary features are already available. It has a solid marketplace, supports both Docker and standalone setups, and offers great enterprise integration. The developer portal has greatly improved the user experience, making it simple and user-friendly wherever we’ve implemented it. Overall, it’s not as complicated as other API gateways.

I have been using WSO2 API Manager for the past six years.

WSO2 API Manager has good integration capabilities and is easy to integrate within existing infrastructure. It also integrates well with third-party solutions, as there are many connectors available.

Deploying WSO2 API Manager is easy and not complicated. With someone experienced, the full implementation, including a database setup, can be completed within a week. 

The challenge is the increasing pricing, which has led some customers to consider alternatives, like using Spring Boot solutions instead. The rising costs, especially as cores and usage increase, have been a concern, prompting some to migrate to other products.

Overall, I’d give the product a ten out of ten. For future improvements, I’d like to see external API security features added, as security is becoming a big issue. It would be great if WSO2 API Manager could provide an API security dashboard, showing details like API discovery and highlighting any unsecured APIs, public tokens, or other vulnerabilities. This would help in identifying and securing any exposed APIs.

I use the solution in my company from our customers to expose APIs built for being exposed. The tool is also helpful for managing security in the area of APIs and making sure that only those people can access the process of developing and managing APIs. Managing the versions of the APIs and their functionality and all the documentation around the APIs is also possible with the tool. In a nutshell, WSO2 API Manager deals with API orchestration and to try using APIs together. For example, suppose you make claims in management and insurance. In such cases, you touch a few when you do the claiming process, and it is where the APIs are a basic part of the process and are involved in the orchestration process to call for different APIs. It all basically gets managed by WSO2 API Manager.

With regards to WSO2 API Manager, I think it may be a bit difficult to speak about the features because security has its own standards, and those standards have to be met by the product. The security standards include encryption and supporting things like acceleration of tokens, single sign-on, the generic tech tokens used to authenticate the API Manager, and integration with other tools. The important thing is that it should support users from a security point of view.

I haven't seen any issue on my side. I like the tool. I can't think of something on top of my head that needs to be improved right now.

The product is built on open standard APIs and offers different levels of support to users. Sometimes, the tool has to be forcefully integrated with other products. The pricing models offered by WSO2 API Manager could be more flexible and should offer different options so that more people can access them.

I have experience with WSO2 API Manager.

It is a very stable solution. We have experienced no issues. The tool is quite stable and robust, making it a well-built product. The tool's architecture is a natural fit for others because it is built to fit in anywhere, and that is helpful.

It is a scalable solution because it can be scaled horizontally and vertically. You can run many instances and there is a flexibility offered. With volumes coming in that are quite large, you just basically add more nodes, and then you do have the load balancing between them after which it will basically take care of everything.

In our company, we only have two customers who are using the solution.

The solution's technical support is fast. You need to buy a subscription to get support. There is obviously free support, but it is limited. If you need very quick and effective support, you obviously need to buy a subscription for that because the product is an open-source tool. If you need support and extensions and things like that, you obviously need to work with WSO2.

The product's initial setup phase is straightforward. When I used it, there were two options for installing it, and both were quite straightforward. The tool itself is quite simple. There are two options that we have to install the tool, one of which is a managed service. Basically, you just go to the cloud and configure it because you have to configure it to your requirements. You can either go on AWS or an on-premises version, but even then, it is a simple process to handle since it is an open-source company. You are able to download the product and follow the instructions, which are well-documented and quite easy to follow.

The tool's ROI is quite high because if you compare it with other products in the market, you would pay quite a high licensing fee. If you get a WSO2 two product, you don't pay a high licensing fee. As the product is robust, it is quite an effective tool from an ROI point of view. To get a product that gives me good value, my ROI would be quite high because I am not investing a lot.

I suggest others to just use the tool. It is a good product. I think you just need to have some skills to use it. If you want to use the product, try to understand programming languages.

I have not used AI in the tool.

I rate the tool an eight out of ten.

I use the solution in the telecom sector.

The most valuable feature of the solution stems from the fact that it is a free tool. Functionality-wise, I like WSO2 API Manager - Publisher API and WSO2 Enterprise Service Bus.

In the future releases of the product, I hope WSO2 API Manager remains available as an open-source product. In the Gulf region, there is a great need for open-source technologies.

WSO2 API Manager should be always available to users as an open-source product that is license-free. In that case, it will be very much appreciated and used in the Gulf region and Saudi Arabia.

I have been using WSO2 API Manager for two years.

Stability-wise, I rate the solution a seven to eight out of ten.

Scalability-wise, I rate the solution a six out of ten.

Around 15 developers and the end users or consumer users are about 1,000 for the tool.

There are no plans to increase the use of the solution.

I rate the product's initial setup phase a five on a scale of one to ten, where one is a difficult setup phase, and ten is an easy setup phase. Initially, any developers, integration experts, or guides have complete knowledge of how to install the tool. For fresh graduates and engineers, the setup process can be very difficult.

The solution is deployed on an on-premises model.

The solution can be deployed in an hour.

There are no subscriptions or licenses required to operate the product, like in the case of Apigee and IBM API Connect. It is an open-source product.

I recommend the product to small companies, and whichever other companies need to deploy WSO2 API Manage should go ahead and use it since it offers the full set of functionalities offered by similar tools like Apigee vs IBM API Connect.

I rate the overall tool an eight out of ten.

It is for Reselling and Integration in our solutions to be sold  to customers

This has improved us a software company, where we have integrated the solution to many of our customers,

We use the vanilla version of the WSO2 API Manager and integrate additional features ourselves. The basic features of the API Manager, such as blacklisting and whitelisting, are very helpful. We also created dashboards.

We paid extra for some new features of the WSO2 API Manager and integrated them into our system. We created our dashboards and did not opt for additional features like Identity Manager and other components.

The commercial aspect could be improved. Pricing varies with partners, so selecting the appropriate pricing can be challenging at times

I have been working with the product for four to five years. 

The Solution is very much stable, and has a very good support mechanism in place too

The product is very scalable. Our customers have up to 20,000 TPS users, and the solution handles it. It also provides regular updates to ensure scalability.

I haven't contacted the technical support directly. My technical team contacts them and finds them responsive. We have not got any concerns or negative feedbacks thus far.

Positive

We chose the tool due to the company's decision. 

The solution helps us to save time. 

My previous company paid about 1.2 million dollars, and my current company pays about 300k. Both companies are at the enterprise level.

There are some built-in security features, but we also have our security measures integrated with the product.

The tool conducts regular research and comes up with constant improvements. I recommend it to others. 

I rate the overall product an eight out of ten. 

My company uses WSO2 API Manager as a gateway to support our services and monitor their use.

Based on the information I have, the solution's most valuable feature is its capability of implementing custom solutions.

The price and the complexities attached to the solution are two areas of concern where improvements are required.

One of the problems with the solution that we face in our company stems from the fact that we have not been able to do any direct upgrades because of the custom feature that is included in the solution, and we specifically face such problems during migration projects. I would say not that we are not updated in our company when it comes to the solution. In general, my company is not able to do an automatic update because of some custom features in the product. The aforementioned area can be considered for improvement.

I have been using WSO2 API Manager for three or four years. My company is a customer of the solution. I don't know exactly the version that we have of the solution in our company.

Stability-wise, I rate the solution an eight out of ten.

It is a scalable solution. Scalability-wise, I rate the solution an eight out of ten.

I would say that with the solution, my company deals with around 100 use cases.

The solution is used daily in my company. I work in a retail bank and know that the bank's customers constantly access the solution. My organization's IT or administration people use the solution weekly or monthly. I don't think I have seen any updates often.

It is not easy to reach the solution's technical support team. My company has an external partner who helps us with the support part of the tool. Though my company's external partner is entitled to get support from the solution's support team, it is not easy for them to reach out to WSO2 API Manager's technical team. I rate the technical support a four out of ten.

Neutral

The initial setup of the product is a little bit difficult.

I rate the initial setup a three on a scale of one to ten, where one is really difficult, and ten is easy.

The solution is deployed on an on-premises model.

The product's deployment phase may extend to weeks or months, but in general, it can be completed in a couple of months from the beginning until the final deployment to production.

One or two people from my company were required to take care of the product's deployment phase.

The deployment phase of the solution was done in-house, that is, in our company, but with the support from some collaborators we have with an external partner.

WSO2 API Manager is quite an expensive tool. I rate the product's pricing a nine on a scale of one to ten, where one is low and ten is high.

No more than one person is required to manage the product's maintenance phase.

Owing to the fact that I don't have enough expertise when it comes to the solution, I don't know if I would be able to recommend it to others. In my company, there is a team involved in the process of evaluating the solution from whom I try to get some information related to the product.

I rate the overall product a six or seven out of ten.

I use the solution in my company as an enterprise application that will be placed in more than 175 places across the world, which would be in different countries. As an API management tool, it will be placed across different regions on Azure Cloud and WSO2's cloud.

I work for the front-end applications in my company, for which we consume APIs with the help of WSO2 since it is also used in our multiple different back-end systems, causing the tool to get integrated and work as a middle layer in our organization.

WSO2 team recommends mTLS as security. Recently, my company faced some issues when implementing mTLS between the DB and front-end applications. My company needs Technical help from WSO2's team to deal with the aforementioned area. WSO2 team should provide better guidance in documentations to implement this.

I have been using WSO2 API Manager for a year.

It is possible to scale up and scale down with the solution. As my company is involved in the setup of the product in different regions, I can say that I have not seen any issues related to scalability.

I have contacted the product's support team, and my company gets support on time since we have enterprise-level support from WSO2 since we are involved in a big project. My company raises our concerns about the product with the support team through an available ticketing system. My company can also call the product support team directly.

I rate the technical support an eight out of ten.

Positive

I have previous experience with Azure API Management and Apigee API Management.

It is wrong for me to compare WSO2 API Manager with the tools like Apigee API Management or Azure API Management that I have used in the past since they may have matured a lot during the time frame when I have not used them over a period of a year. I cannot compare the product I used in the present with the product that I used two years ago. On a quarterly or six-month basis, many tools get upgraded.

There is a separate team in our company to take care of the tool's setup phase. I work as an architect and have experience with the setup phase of Apigee. I mostly focus on the front-end applications in our company.

My company has to operate in different regions, which are spread out in 175 places across the globe. My company soon plans to set up the product on the cloud platform for different regions, primarily with the services from Azure Cloud for regions like the USA, India, the Gulf, and China. For every region, my company needs to deploy the product separately. The DevOps team has set up the product in various regions for my company.

The solution is deployed on the cloud.

My company chose WSO2 API Manager based on the decision made by the client who wanted it in their environment.

My company is okay with the analytics and usage of the product. The analytics part is mostly managed by the client who uses the product or the API team in my company, so I am unsure about the analytics part.

My company has used the product's customized integration capabilities for MongoDB and some other commercial tools.

Speaking about the most beneficial features for API lifecycle management, I would say that my company has a DevOps tool in place for deploying all the APIs. My company also received feedback from WSO2's team during the development phase. On the API lifecycle management side, I do not see much, but I know that it consists of areas like API versioning and API deployment. I don't see anything special when it comes to the API lifecycle management area of the product since it is similar to what AWS offers. All the processes related to the product are taken care of by my company.

I have worked with many API management tools in the past, and I don't see any case scenarios that were different from what I have seen while using other products.

My company has faced so many technical challenges in many areas. Our company's team members face issues with the product since we have not yet properly implemented it. I have worked with the API management tool from Google in the past and have seen that Google provides better documentation, which is much better and cleaner than what WSO2 API Manager provides.

I rate the overall product a seven out of ten.