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.

WSO2 API Manager serves as a central hub for integrating sensors across SmartCity projects. We provide support for developers, enabling them to build applications using our platform. Our use cases include features like spotlighting, forecasting, and environmental monitoring. We also offer security management through WFO protocols for responsible and secure environment for our users.

WSO2 API Manager is open-source, which offers a range of features not found in other open-source API tools. The user interface is another standout feature that we appreciate. In terms of effective features for API life-cycle management, we use the tool for licensing, allowing us to differentiate rates based on customer numbers and end-user data publishing.

Regarding security features, WSO2 API Manager is a robust compliance solution, especially for AWS usage. It offers deployment management, performance-based security, and overall compliance support.

I would like to see improvements in the speed of the solution as it can be a bit slow compared to other platforms along with addressing memory issues would be beneficial.

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

We experienced some stability issues, particularly related to memory, which affected the database performance.

WSO2 API Manager is scalable and suitable for our project needs. We have around twenty to twenty-five actual users who access the platform for deployment and management purposes.

I have interacted with technical support in the past, and they have assisted us with our queries. They were helpful overall, although some complex issues took longer to resolve.

I have experience using another API management solution from a larger company. Comparing WSO2 API Manager, it has its strengths in flexibility and customization based on our requests. It also has robust features and components. But in terms of cons, it can be complex and may take some time to set up compared to simpler solutions.

The setup was a bit complex because we initially started with enterprise professional services, but later transitioned to the open-source version which required more effort to set up.

We didn't encounter many challenges while integrating WSO2 API Manager with other systems as we primarily focused on setting up our own solution. We mainly relied on the solution itself for updates and upgrades.

Our deployment involved setting up two rings in the cluster and transitioning from testing to production. It took some time to learn the deployment process, especially with the enterprise version.

We completed the set-up in-house. One person is required for handling the deployment for the enterprise aspect.

We haven't implemented any AI-driven solutions or encountered AI-driven issues within our company.

I would recommend WSO2 API Manager to other users, especially if they value a robust support system and are ready to invest in the deployment process. However it is important to consider factors like support costs and licensing models before making a decision.

In terms of overall rating, I would give it a seven out of ten, taking into account both its advantages and limitations.

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.

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.

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.

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.

It's an API gateway. So, it just sits between the API layer and the orchestration layer. Basically, we use it to orchestrate service calls.

It has a lot of flexibility. The flexibility is definitely a highlight.

We have flexible mapping capabilities, allowing us to provide common mappings or create custom ones as needed.

It also has an excellent dashboard for real-time monitoring of tests and a pluggable development studio where we can code custom logic directly into the execution flow. This goes beyond standard mapping, enabling us to write our own custom logic directly.

Based on our recent large scaling project, the latency needs to be improved.

I have been using it for one year.

It seems good based on the client's claims and what we've seen in our benchmarking.

I would rate the stability a nine out of ten.

I would rate the scalability an eight out of ten. But the latency can be improved with better scalability, so that would be ideal.

From the client's perspective, around 20 to 30 interfaces are involved in their batch processing. From the administrative side, around 40 to 50 users use it.

We've had certain issues where we posted queries and got responses. Thankfully, none were blockers so far. So we haven't needed to formally contact support.

So we don't have to conduct support. We had good interactions.

We used some lightweight solutions that we replaced with WSO2 API Manager.

We were looking for a solution that could handle a complex gateway with multiple components, balancing, routing, and business process automation.

Our previous solution offered basic load balancing and monitoring, but for our business needs, we needed more. WSO2 API Manager offered the features we checked and felt it was a step up to an enterprise-level product with better technical support.

The complexity of the setup is kind of medium; it's not super easy, but not super difficult either. You can manage it if you learn the roadmap properly.

We've been using it on-premises. Right now, we're planning to move it to the cloud.

Deployment depends on various factors, but typically, it can be done relatively quickly.

It's costly.

It's a stable product with good features that are well-bundled. The documentation is helpful, and there are many community resources available if you need custom integrations.

Most importantly, it has many plugins for integrating with various databases, which are standard integrations in the market today. You don't need to code them yourself; you can just use the plugins for integration and easy access.

Overall, I would rate the solution a nine 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.

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.