Try our new research platform with insights from 80,000+ expert users

IBM API Connect vs Perforce Acana comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jun 8, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM API Connect
Ranking in API Management
8th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
76
Ranking in other categories
Integration Platform as a Service (iPaaS) (9th)
Perforce Acana
Ranking in API Management
30th
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the API Management category, the mindshare of IBM API Connect is 6.0%, down from 6.3% compared to the previous year. The mindshare of Perforce Acana is 0.5%, down from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management Market Share Distribution
ProductMarket Share (%)
IBM API Connect6.0%
Perforce Acana0.5%
Other93.5%
API Management
 

Featured Reviews

Shanmugasundaram Shanmuganathan - PeerSpot reviewer
Offers basic API orchestration and provides robust security and governance features
While Azure API Management offers configurable scalability, IBM API Connect relies on Kubernetes clusters. This might seem manual and require defining cluster instances upfront, but it's completely customizable and not on-the-fly scaling. It's completely custom-driven, not on-the-fly scaling, which some may consider cumbersome. Overall, I would rate the scalability an eight out of ten. Almost all applications we've been exposing lately go through this middleware, so it's used extensively. There are around sixty applications directly using it, but six Kubernetes clusters serve those applications. It's heavily used for integration, including system-to-system integration and product integrations. Our usage has been increasing year-on-year based on our needs.
Saurav Krishna - PeerSpot reviewer
Authentication mechanism is easy to implement but improvement is needed in documentation
For API security purposes, we use the tool to host all our APIs. This allows us to take advantage of the security features provided by the platform. With the solution, we can implement rules such as rate limiting and restricting the number of API calls for each user. It acts as a secure gateway…

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The centralized management: this provides a management module that can deploy and apply security policies to all APIs, including all the gateways that are deployed on-premises and on any cloud because the gateway component can run at a VMware or in a Kubernetes cluster."
"Security is well organized and managed within the solution."
"The most valuable feature for me is the ability to distribute work among our API developers, so we don't have to do all the work as IBM API Connect administrators and IBM DataPower administrators."
"Our version supports containerized integration. I can write APIs, which can be moved into a testing environment without needing a forklift. It can check if APIs are compliant before moving them into production."
"Overall, I rate it nine out of ten."
"It offers enhanced security features to protect APIs, enforce access control, and secure sensitive data."
"The most valuable features are stability and security."
"The solution's technical support team is good."
"The tool's authentication mechanism is easy to implement. We had to define a few parameters."
"Good interface, intuitive solution."
"It allowed us to publish and replace pre-essential transactions in one place, with a uniformity in terms of control and policies."
 

Cons

"It would be helpful to have access monitoring."
"It's based on a little bit dated architecture. A lot of evolution has happened after that. It's an evolving field. Kong is a Kubernetes-based platform. Kong runs on Kubernetes, but all the other ones are in microservices. So, there's a lot of improvement that can be done."
"When comparing API Gateway with DataPower Gateway, several features in DataPower Gateway are absent in the APIC layer. Examples include the lack of connectivity to MQ."
"The solution would be better if it had cloud functionalities."
"The solution is overly complex."
"The initial setup and installation could be easier."
"There are some performance issues and issues related to asynchronous APIs."
"IBM info-center help documentation also needs improvement. Competitive product like Apigee provide out of the box policies to run Javascript, JAVA and better/flexible logging policies."
"Akana API Management needs to improve its documentation."
"The product has new features that we are going to implement in the next few months, such as API management and analytic reporting."
"Lacks an integrated billing feature."
 

Pricing and Cost Advice

"It is quite an expensive product."
"API Connect is expensive - I'd rate their pricing five out of ten."
"I haven't seen anyone go from on-premise to the cloud. In fact, I am seeing people go from the cloud to on-premise because the costs can quickly grow on the cloud."
"API Connect's license cost could be a little lower. But, unfortunately, there aren't many open-source API gateways. Ideally, some new developers could come up with a minimum-functionality open-source solution."
"I rate the product price a seven on a scale of one to ten, where one is a low price, and ten is a high price."
"It would be a good idea to bring down the pricing by at least 20 to 30 percent."
"This is a licensed product. If your company is looking to obtain a license, you have to work with IBM partners."
"It is expensive when compared to other products in this class. There were no extra fees for add-ons or technical support."
"For us, the pricing and licensing policies were for an on-premise installation with a fixed cost structure, that matched our budgeting policies."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
868,759 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Insurance Company
12%
Computer Software Company
11%
Manufacturing Company
7%
Financial Services Firm
19%
Manufacturing Company
14%
Computer Software Company
13%
Performing Arts
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise10
Large Enterprise58
No data available
 

Questions from the Community

What do you like most about IBM API Connect?
Publishers can easily identify, create, and publish APIs on the developer portal, defining plans, packages, and potentially billing rules.
What is your experience regarding pricing and costs for IBM API Connect?
Pricing depends on how many instances run across environments. I don't deal with licensing, but compared to other IBM products, the licensing is not significantly higher.
What needs improvement with IBM API Connect?
When comparing API Gateway with DataPower Gateway, several features in DataPower Gateway are absent in the APIC layer. Examples include the lack of connectivity to MQ ( /categories/message-queue-mq...
What do you like most about Akana API Management?
The tool's authentication mechanism is easy to implement. We had to define a few parameters.
What needs improvement with Akana API Management?
Akana API Management needs to improve its documentation.
 

Overview

 

Sample Customers

Heineken, Tine, Finologee, Axis Bank
British American Tobacco, Credit Suisse, Daimler, eBay, FOX, Liberty Mutual, Marriott, Mayo Clinic, Skandia, Tata communications
Find out what your peers are saying about IBM API Connect vs. Perforce Acana and other solutions. Updated: September 2025.
868,759 professionals have used our research since 2012.