WSO2 API Manager Reviews

I have used features like routing and authentication, as well as the most well-known features of WSO2.

WSO2 API Manager has some support problems and can be a little complex.  So our developer teams decided to use 3scale or Kong instead. We found WSO2 API Manager to be a bit complex.

So, in terms of complexity, WSO2 API Manager has some challenges. Also, there is a bit of an issue with the pricing and license of WSO2. It's a little high.

I used WSO2 API Manager for two projects. However, I can't say I have used it all the time. I have about 50% experience and knowledge about it.

We are not satisfied with the customer service and support. In a few instances, their response time has been a bit slow.

Neutral

It is difficult to implement WSO2. The implementation can vary depending on various factors, such as the features required and the availability of human resources, including developers. It could take anywhere from two to three months or even just one week, depending on the specific requirements.

Our team worked together with our developers to carry out the implementation.

For our projects, we found it to be a little high. However, it may not be the case for another company or project. Because the costs depend on the specific features you would require and other factors.

It's a good product. I prefer it. However, I would only recommend using WSO2 API Manager if the user has a specific requirement for one of its features. If they don't have a specific reason for using it, I can't provide a recommendation because it depends on factors such as the project, the local team, and the desired features. The API management system is complex by default. Therefore, the selection primarily depends on the project and the programming platform used by the developers.

Overall, I would rate WSO2 API Manager a seven out of ten because there is still room for improvement. 

WSO2 API Manager is used for digitalization and innovation.

WSO2 API Manager could increase their security compliance.

Here in India, the government is coming with a lot of regulations and required security features which the solutions have to upgrade to meet this requirement. Most of the solutions sell API management as a security solution, but they have to improve the security features.

There are a lot of modules and it can be complex.

I have been using WSO2 API Manager for approximately four years.

WSO2 API Manager is a stable solution.

My customers are not large companies, their volume is less. That is the reason why I recommend WSO2 API Manager because they have a full life cycle of products. For example, they have ESB, API management, and other tools. Additionally, they have webMethods and is quite expensive. 

There is a solution called Gravity which is new that is very good, but they have pure API management which vendors are looking for a full-fledged solution. That is their legacy model, they would need an ESB.

The technical support is good but it depends on the partner relationship.

I would rate the support from the WSO2 API Manager a four out of five.

Most of the solutions similar to WSO2 API Manager have small differences, because of how it fits in their environment. The features that WSO2 API Manager has most of the vendors have too.

I rate WSO2 API Manager a seven out of ten.

We use it along with IdentityServer, as our main API management tool for API exposure to the internet. It's not for internal usage, it's for external use.

We have two main roles regarding WSO2 API Manager. There are the admins, who publish guides and user updates, etc — we employ around four people who perform this role. In terms of users, we have around five to six million users going through it on a monthly basis.

The main feature — the publication of the API, the management section — is great in general.

I think it would be very unfair for me to answer this question because we are running a very outdated system (they might have improved it a lot with their newer versions), but I'm going to try it anyway. I think they could greatly improve the general UX with their solutions because when you manage different components that are meant to work together, it's very difficult. You have to deal with two completely unrelated interfaces.

Perhaps they should include a tool to assist with migrating to Azure.

I have been using WSO2 API Manager for the past four to five years.

Stability-wise, it's actually pretty nice — it's good. I wouldn't say it's very good or excellent, but it's good. It fits the bill.

Scalability-wise, I'd give it a three-star rating out of five — good, but not very good or perfect.

The provisioning has to be done manually. In terms of system-wise configurations, these settings involve a lot of big Java components, so it's not natural. It's not very easy to handle. Again, this is an older version. Perhaps they have already worked on this.

We don't have a contract for dedicated support. We have to deal with internet forums, etc. Officially speaking, there's no support outside of community forums.

The documentation and community support are pretty helpful. There are a lot of questions answered about WSO2 on several forums and message boards, etc. Although it's not dedicated, it's quite relevant.

We're actually in the process of switching to Microsoft Azure API management.

For us, the main benefit of Azure is that it's a managed solution. We have a very restricted theme and not having to deal with the actual configuration of the platform or the underlying operating system and other intrinsic administration tasks is a big win for us. The feature that we use the most and that is most licensed is perhaps the online portal. The certified online portal is the biggest win for us because we can deal with the associated integrations within this new portal, which we can't in the current stack, the on-premises stack.

I wasn't a part of the original project, but I know that the initial setup wasn't easy.

We use the open-source version — the free version.

I wouldn't actually recommend this to anyone. I think that there are paid solutions, such as Azure API Management, which will relieve you from the administrative burden. Personally, I wouldn't recommend this solution at all.

On a scale from one to ten, I would give WSO2 a rating of seven. It's a good tool, but dealing with the on-premises infrastructure is a big headache.

We provide this solution to our customers. Most of our clients are enterprise size organizations. We have a partnership with the company and I'm a solutions architect. 

This is a complete integration suite and it's good for open banking and the like. From a product perspective, it's a good platform. 

We've had some challenges with the professional support and licensing aspects of WSO. 

We've been using this solution for six years. 

Stability is definitely something that needs to be improved. 

Customer support could be improved. 

Neutral

I think our deployment process is good but our interactions with WSO could be improved. 

The licensing process could be improved, it's been a challenge for us.

The traction we've seen with API Manager over the last couple of years has dropped off and solutions like Kong have become more popular. Our focus has now shifted to that product. 

I'd rate everything about this solution an eight out of 10. 

The solution is used mainly for API management. 

The main feature is the enterprise integrator. It's very important to API management. You can implement SOA strategy in the company using the API Manager. Some companies were just using enterprise integrators at the beginning. For implementers, they had to install it to use the API management and identity the server to have more security in the system.

The solution is stable. 

It's scalable. 

It is easy to set up. 

They've already improved a lot of features between versions six and seven.

The user interface could be a bit better. Sometimes you have different visual aspects when you change from one screen to another.

I'm implementing a WSO2 project right now. I've used the solution for the last six months. 

It is a reliable, stable solution. There are no bugs or glitches. It doesn't crash or freeze. 

You can scale the product. 

We can install it in a cluster manner. We can use Docker to scale all of the systems. 

We have 1,000 users on the solution. 

We had support every time we needed it; we could reach support without a problem.

Positive

The initial setup is not complex. You can install everything together in what they call an all-in-one setup, or you can install each model separately. It's not difficult to install.

If I had to rate the initial setup of WSO from one to five, I'd rate it a four out of five.

I don't deal with the licensing aspect of the product.

I'm starting with Microsoft as our API manager on a daily basis.

I'm working as a project manager and architect, so I don't install the products. However, I understand their texture and how the parts interact with each other.

I'd advise new users to have a company that knows it very, very well. If you don't don't know the product at the beginning, you can make a mess of your project. Choose a good partner first to make everything easier.

I would rate the solution eight out of ten. It's a good product.

We use the integrator.

The solution helps me get my job done. It's a good product.

The product hasn’t been updated for some time. I wonder if it has reached the end of its life and is no longer being maintained.

I have been using the solution for more than four years.

I rate the tool’s stability a five out of ten. There hasn’t been an update for a long time.

We did not face difficulties while deploying the product. The tool can be deployed within a few minutes. The documentation is good. We haven't had any issues in maintaining the tool.

I am using the free version.

We are a B2B company. I am the CTO. I work on the solution alone. We use it for a small project. All the technologies we use are open source. I recommend the solution to others. Overall, I rate the tool a seven out of ten.

We use the solution mainly to protect the frontend and backend proxy APIs. We also use the solution for federating with the identity server. We publish our backend API into WSO2 API Manager and use the proxy API outside. We use the solution for authorization, authentication, and accounting purposes.

WSO2 API Manager is quite easy. With WSO2 API Manager, we can use different DBs. It is easy to accommodate the solution along with any kind of identity server. WSO2 API Manager has a user-friendly model.

WSO2 API Manager should improve its marketplace subscription model and documentation in order to reach a higher level in the market.

I have been using WSO2 API Manager for the last two to four years.

I rate WSO2 API Manager an eight out of ten for stability.

I rate WSO2 API Manager an eight out of ten for scalability.

The solution's support model is not very clear enough right now.

Neutral

I previously used the Akamai tool.

The solution's initial setup is very easy. I rate WSO2 API Manager an eight out of ten for the ease of its initial setup.

The solution's deployment takes two to three hours. One person is sufficient to deploy WSO2 API Manager.

WSO2 API Manager is a costly solution, and its pricing is not competitive enough compared to other products.

I would recommend WSO2 API Manager to other users.

Overall, I rate WSO2 API Manager an eight out of ten.

Our primary use case is integration of legacy systems and channels, exposing APIs and security. I'm co-founder and CTO of the company. 

The solution is open source and easy to configure. 

I'd like to see some new features and updated functionalities.

I've been using this solution for three years. 

The solution is stable. 

The solution is scalable. 

The technical support is very good. 

The initial setup is straightforward. 

I would recommend this solution, open source is king. I rate this product 10 out of 10.