We changed our name from IT Central Station: Here's why
Get our free report covering Kong, Google, Amazon, and other competitors of WSO2 API Manager. Updated: January 2022.
564,599 professionals have used our research since 2012.

Read reviews of WSO2 API Manager alternatives and competitors

Igmar Rautenbach
Head: B2B Solutions at Trustlink (Pty) Ltd
Real User
Top 5Leaderboard
Good documentation, strong security functionality and offers great flexibility
Pros and Cons
  • "There's drag and drop functionality so that you do not need to have a senior expert developer to make use of the tool. You can get more of your staff trained up to be able to use it as it's not overly technical."
  • "The installation process is a bit complex and it could be a lot simpler."

What is our primary use case?

We make use of Axway's API gateway API management tool.

Its integration with middle wear is similar to ESB. We provide integrations as we are a swift services bureau. We've got customers that are banks and in some use cases. We integrate these banks with their own back office and we tend to provide integration for that. 

We also make use of the solution to build a marketplace of financial services, which is basically our own solution. 

For other customers, we do integration of the various source systems, back-office systems, legacy systems, etc. We also do file transformation where we take messages for customers in their environments and translate it to industry formats. 

What is most valuable?

There's drag and drop functionality so that you do not need to have a senior expert developer to make use of the tool. You can get more of your staff trained up to be able to use it as it's not overly technical. 

It provides very strong security functionality to protect information in an easier way. 

It's more of a benchmark for financial services. You can better protect the information and customer information as it's got a very strong focus on security. 

The flexibility is very good. You can do on-premise and you can do cloud. That's really a strong factor in our market as many large customers in our market still want to have an on-premise solution due to the fact that they want to maintain control over their data.

Previously, the solution did not have a subscription as an option, however, now it also has a subscription model, which is great.

The documentation is fairly good and readily available.

What needs improvement?

The pricing could be more competitive. 

The installation process is a bit complex and it could be a lot simpler.

Currently, there's a strong focus on microservices, which is already there and already available. They're already able to deploy in dockerized containers. In that sense, there's nothing that I can actually see that is missing from my side.

For how long have I used the solution?

We've been dealing with the solution for the last three years.

What do I think about the stability of the solution?

The product has got strong security features, from a stability point of view. There's a large footprint in the financial services sector, where you deal with daily transactions in the millions. It has a very strong focus on stability, and our experience as well has been that, as we also use it in a payments environment, it's been proven to be quite stable. 

What do I think about the scalability of the solution?

We have probably eight people who make use of the solution in our organization.

It is a solution that is strong enough to be used by enterprise-level customers. That is the target market. However, it provides such strong features, that it is used in our environment by FinTech startups, and also by other mid-range customers that are not really at the enterprise level. It solves their issue of integration and to decouple their back-office systems so that they can develop one in a specific area, and make their system changes. It's a very versatile product; many organizations can benefit from it.

The solution is scalable. That is a benefit of the platform in itself. It provides you with scalability so that you don't have to develop all your back-office systems. The product itself is scalable in the sense that you can spin up additional environments very quickly. 

Its price scalability is also very good as you don't necessarily pay for extra usage. You pay a fixed subscription. In terms of dealing with high volumes, it is also scalable in the sense that you can just add processing capacity where you need to.

How are customer service and technical support?

We actually provide support to customers. We provide remote support as well as on-premise support. From a support point of view, we are happy, as it provides a lot of analytics. With the analytics, you can very quickly drill through transactions and see where there are issues. 

We don't foresee any difficulty with the support of the solution, and we are support providers. It's always important to have someone, to have a vendor that provides you with at least level three support so that your operational teams can be at their best productivity-wise.

The support desk is very good. I deal with them regularly. You raise a ticket as normal and they will then guide you through to a resolution.

How was the initial setup?

The initial setup is a bit complex. 

It is now Dockerized containers. That makes the whole process of installation and upgrades much more simplified. Their version 7.7, the last version, means that from here on there will not be a big change. You have to completely build an environment, however, after that, you will only patch it. 

It's software that has complexity. It's a middleware system that is set up in various environments, however, it needs to align with the corporate policies on security and DMZ. You have to design it and then you have to build it. You probably will be okay during implementation if you make use of certified technicians to assist you with building the solution.

The positive with the solution is that, once you are operational, you should be able to maintain the solution with a very small team. There are instances where there's a footprint of multiple installations - more than 20 for a global organization. Yet, they've got just one core team that actually maintains all of those installations. That illustrates the sort of scalability it has when it comes to supporting a large footprint.

If our clients need it, we can provide maintenance for them. We can do tasks such as patching, updates, etc. Customers, of course, can also handle maintenance themselves.

What about the implementation team?

It's best to get a professional technician to handle the installation as you want to make sure that it's configured correctly to get the best use out of it. Once you are operational, you can really make use of your own skills to maintain it.

What's my experience with pricing, setup cost, and licensing?

The pricing is fair. They're still investing in development and provide much-needed functionality and with the assurance that it will not leak your data or provide you with gaps in your risk. From a pricing point of view, I don't think it's on the high side. I would say it's a mid-market price and there's flexibility in their pricing options. 

Which other solutions did I evaluate?

We evaluated a number of API solutions, including WSO2, Apigee, and IBM and in the typical use cases where we deal with enterprise and financial customers. We found that some of the solutions either did not have good enough documentation, good enough support or maybe a lack of on-premise functionality. Pricing on some options was also an issue. We made the decision to use Axway after looking at it and others across these and a variety of other parameters.

For example, in the case of WSO2, our Financial Services client made use of it, however, for us, it was very difficult to understand and to problem solve that solution, and documentation played a role as it wasn't the best. 

We're also partners with IBM. The platform for us, the number one issue, is its price. On top of that, it's really more for the adoption in a mid-market space. 

We looked at Apigee and others where it's more power-orientated and that doesn't solve the problem that financial services, healthcare, and other vendors had as they wanted to have better security and have the data in on-premise.

What we found, in the European market at least, was that Axway has very strong links to financial services, transport logistics, healthcare, and banks. These are its primary industries. For us, it was important that the solution we chose had a strong knowledge base across those industries, and not only focused on a specific industry.

Some of the other vendors have got a very wide focus. For us it was easier to find agreements when looking at Axway's Roadmap. It was really important to see, that the business is focused around the solution and they execute on their Roadmap and develop out the solution continuously.

What other advice do I have?

We're largely a customer, although we are consultants and refer Axway often.

While we use the solution's cloud deployment model, we also engage with the on-premises version as well.

I'd advise other companies considering a solution like this to first go and determine their strategy around APIs in their business. That's really important. There needs to be a plan around how a company is going to manage APIs. A business needs to ask itself: What is the digital transformation strategy? They need to approach this as a strategic investment and already have some strategy behind it. 

It really is core to your digital transformation, to your ability to unlock new revenue channels for a lot of businesses or to reduce cost in your back office systems. Therefore, there must be some sort of strategic benefit that you see before you actually evaluate API platforms. 

Once you've got a strategy, you're sure that this matches your strategy. You probably need to also look at the first use cases that you want to do. You have to find a use case that shows a business benefit to deploying. It doesn't help you implement the solution just so that lots of people can use it for different things. You must find some anchor or use case that you will be able to sell. Then it will become a benefit to your internal business.

From there on it's really, really important to identify integration partners that are certified that can actually assist you from a business point of view, to deploy quickly. The quicker you get the benefit, the quicker you get the new revenue from whatever you want it to do. After that, it's crucial to internalize the knowledge around the solution. It is important to do good skills transfer so that you can have confidence in using the solution long-term.

Overall, I would rate the solution nine out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Enterprise Integration Consultant at a computer software company with 1,001-5,000 employees
Consultant
Great for any company wanting a complete digital transformation
Pros and Cons
  • "One of the more valuable features is the stability of the platform."
  • "Not many stand-out features."

What is our primary use case?

My primary use case for the solution is as an API gateway. I am an enterprise integration consultant and I implement it for customers.

What is most valuable?

I would say one of the more valuable features is the stability of the platform. The API gateways across the market end up exposing more or less the same functionality when it comes to the mediation exposure of the proxies. It was decent to work with it even though there weren't many stand out features. The user interface is consistent across all of the products. It's difficult to differentiate APG from IBM Connect or MuleSoft Anypoint platform. They have a rich user interface. 

What needs improvement?

I think while trying to evaluate the various products on the market, and what could be improved, I'm looking at the indications and analytics and the off-the-shelf dashboards that come with it. Those are things that really catch the eye. At the end of the day, it's the functionalities and the way they integrate with the multi-cloud platforms and other backends that are underpinning the hood. If I have to present an API solution to somebody and if I can show them what are the off-the-shelf dashboards that you get in the analytics profile, that becomes a major eye-catcher to take the discussion forward.

For how long have I used the solution?

I've been using the solution for a year or so. 

What do I think about the stability of the solution?

Stability is very good. 

What do I think about the scalability of the solution?

I would think scalability depends on whether you're doing it on premises or on the cloud. I don't have experience with that but I think, for example, since Kong is more into clustering and the like, so scalability in Kong should be more straightforward because it's more evenly distributed. 

How are customer service and technical support?

I haven't contacted technical support but I have been in touch with some of its engineers and they were a pleasure to deal with. They're good engineers and they are very helpful.

How was the initial setup?

In terms of initial setup, of course WSO2 with Kong is more simple than this.

What other advice do I have?

The advice I would give is that this is a platform that's meant for a complete digital transformation of an organization. If you want to realize the entire capacity or the entire power of the platform with the capability APIs and the system APIs, you know you've got to use the API-led connectivity. And here I think lies the true power of the platform; that instead of using it just as an API gateway, you can take it further and I think that is the real value that market peers are not able to offer. It's a standout feature of the API platform and MuleSoft.

I make proposals and whether the customer chooses it or not is up to them. I usually look at  different products, and then we try and see what fits the customer best. It's not black or white. If there is a need for an entire landscape of low APIs and not just proxies, I think MuleSoft is a good way to go.

I would rate this product an eight out of 10. 

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Implementer
Technical Development Lead at a government with 1,001-5,000 employees
Real User
Top 5Leaderboard
Easy to use with good scalability and performance
Pros and Cons
  • "The initial setup isn't overly difficult."
  • "We'd like it if they could reduce the cost without sacrificing on features."

What is our primary use case?

We are using the product for the APIs, which we are building in-house. We are exposing it to external or even for internal application to application integrations using this gateway.

What is most valuable?

The product has been very easy to use.

The performance is great.

The solution can scale. 

The initial setup isn't overly difficult.

What needs improvement?

I'm from the development team. We have a different infrastructure team, which is actually managing the product and is closer to the features. From my side, I do not see any areas that are lacking. 

The licensing could be better. We are looking for open source. We have evaluated a few. We'd like them to have some sort of open-source option. We'd like it if they could reduce the cost without sacrificing on features. 

For how long have I used the solution?

I've been using the solution for at least ten years. It's been a long time.

What do I think about the stability of the solution?

The performance of the product is good.it's stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

What do I think about the scalability of the solution?

The users of the API gateway are actually the applications, for example, how many APIs we have. We have hundreds of APIs.

We're always increasing usage. 

How are customer service and support?

We have many Oracle products - not just this one. We are completely an Oracle shop. We have yearly support from Oracle. We are using Oracle fusion middleware, like Oracle WebLogic and Oracle databases. I'm not sure if it's premium or not. 

How was the initial setup?

I'm not sure about the initial setup as I haven't done it myself. That said, it should not be too difficult as we are used to the process. For us, it should not be a difficult installation. That said, we haven't compared it with other installations. 

We have a technical team of around 50 to 70. They are all engineers, developers, and managers.

What's my experience with pricing, setup cost, and licensing?

The cost of the solution is very high. It's not very cheap. Some companies may not be able to afford it. 

Which other solutions did I evaluate?

We have looked at open-source options and have looked at Apigee from Google and the WSO2 API gateway. 

What other advice do I have?

I'm a customer and an end-user.

We are currently using whatever is the latest version of the product, as it's my understanding that Oracle has discontinued this. They are moving to the cloud. The latest is on the cloud only. There will be no more on-premises.

I'd rate the solution at an eight out of ten. I've been happy with its capabilities.

I'd recommend the solution to others, however, they need to keep in mind the cost is quite high.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
CEO and Co-Founder at a tech services company with 11-50 employees
Real User
Top 10
A good solution for microservices and APIs, but its price is high
Pros and Cons
  • "We loved the portal part the most, which had monetization and showed how people were using the stuff. It is a good product as a whole and has a lot of microservices and granular features."
  • "The delivery is bulky in terms of implementation. Its price could also be better. It is a very good product as compared to CA API, Google API, and WSO2 API, but its price is high. From the cloud-native perspective, some new features need to be added. It could also be made simpler to implement."

What is our primary use case?

We had a test version, which was more of an on-prem version, and we also had some on the Docker for a live API creator. 

We are a security service company, and we provide a lot of solutions in that space. We were just trying to have a frictionless authentication product, so we were working on that. We were looking for a Gateway that can serve in an API, and we've already got an open-source solution.

What is most valuable?

We loved the portal part the most, which had monetization and showed how people were using the stuff. It is a good product as a whole and has a lot of microservices and granular features.

What needs improvement?

The delivery is bulky in terms of implementation. Its price could also be better. It is a very good product as compared to CA API, Google API, and WSO2 API, but its price is high.

From the cloud-native perspective, some new features need to be added. It could also be made simpler to implement.

For how long have I used the solution?

We have been using this solution for four to five years.

How are customer service and technical support?

Technical support was okay. We were getting good support. We had access to the portal, and the support was good enough.

How was the initial setup?

It was a little complex initially. We struggled a bit initially to understand this solution, but later on, it was okay. I do not exactly remember the issues, but initially, our team was facing a lot of problems in terms of virtualization.

What's my experience with pricing, setup cost, and licensing?

It was very high at that time. We are a Broadcom CA partner, and we got it only for testing purposes. We didn't pay anything for it.

What other advice do I have?

I would recommend this solution to others. This is one of the good solutions for microservices and APIs and for people who need to go the digital way. There are a lot of other solutions that are coming into the market, and the infrastructure landscape is changing.

I would rate Layer7 API Management a six out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
CEO at a tech vendor with 11-50 employees
Real User
Top 5
Incredibly scalable with good technical support that is responsive
Pros and Cons
  • "The most valuable features are scalability and technical support."
  • "Better functionality for validating inputs and outputs would be helpful."

What is our primary use case?

We are using Apigee as our API gateway.

What is most valuable?

The most valuable features are scalability and technical support.

What needs improvement?

The definition of the APIs should improve because you can't easily validate the inputs and outputs. Better functionality for validating inputs and outputs would be helpful.

For how long have I used the solution?

I have been using Apigee for four years.

We are working with a SaaS model and we install the on-premises model version also.

What do I think about the stability of the solution?

Apigee is a very stable product.

What do I think about the scalability of the solution?

The scalability is incredible. We make an average of 22 million API calls.

We have less than ten people who are developers.

We have plans to increase usage in the future.

How are customer service and technical support?

The technical support is very good and we are satisfied with it. They respond very quickly and I like it.

Which solution did I use previously and why did I switch?

I have used several solutions previously, such as IBM API Connect, WSO2 API Manager, and many other API solutions.

What's my experience with pricing, setup cost, and licensing?

It is not suited for small companies. It's expensive.

For a bank, it would not be expensive, but to implement this solution for a smaller company such as an insurance company, it would be too expensive.

The pricing is complicated and not flexible.

The older versions are more suited for small to medium-sized companies. You can no longer pay €20,000 per year.

What other advice do I have?

This is a very good API tool.

I think that this solution is very good in some use cases but not very good for some small companies. It can be complicated for licensing and pricing. This is a product that I can recommend otherwise.

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Get our free report covering Kong, Google, Amazon, and other competitors of WSO2 API Manager. Updated: January 2022.
564,599 professionals have used our research since 2012.