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

IBM API Connect vs Layer7 API Management comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

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
5th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
75
Ranking in other categories
Integration Platform as a Service (iPaaS) (7th)
Layer7 API Management
Ranking in API Management
10th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
111
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the API Management category, the mindshare of IBM API Connect is 6.5%, up from 6.4% compared to the previous year. The mindshare of Layer7 API Management is 3.1%, down from 3.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
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.
Ronald D'Souza - PeerSpot reviewer
Has great drag-and-drop features and it requires minimal coding
I have mainly implemented using Layer 7 API Management. Some of the major challenges we were able to meet with a quick release to market methodology. Some of the tasks which we achieved for our customers were: 1. Translation service from SOAP to REST and vice versa. 2. API service to DB (Oracle, MySQL, MSSQL, Snowflake, SAP HANA) -- Created Swagger APIs that were able to perform CRUD operation to the backend API mentioned above and provided routes to query and get data. 3. Integration with Payment gateway service providers to perform (transaction on behalf of the customer with third-party payment gateway service providers white labeled with our APIs ) -- Followed TMF standards for payment gateway integration with the Telcom world. 4. Orchestration of the API. Build multiple microservers and provided orchestration based on route, path, and data in the request and perform actions that would be communicated with multiple APIs and provide a single consolidated response. 5. Provided API-driven security (Oauth 2.0, JWT, SAML, Basic, and a variety of means) to access the API giving the developer the freedom to concentrate only on application/service/microservice and let the gateway handle the threat. 6. Seamless Mutual Authentication allowed good segregation between APIs in the DMZ and internal network.

Quotes from Members

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

Pros

"The solution offers a pretty good SLA."
"It offers enhanced security features to protect APIs, enforce access control, and secure sensitive data."
"The services that I consume through IBM API Connect are beneficial. It can handle multiple API management."
"Easy to configure security and generate API keys."
"It's quite flexible and easy to deploy, especially for beginners. It has almost all the features that an API gateway should have."
"I have found IBM API Connect to be highly secure, efficient, easy to deploy, and has a great GUI. It can operate and integrate well with other vendors, such as Amazon, Google, and Microsoft."
"The solution provides a common place for all APIs, allowing for easy sharing and exchange of information between internal and external stakeholders."
"We are able to share those APIs instantly within the organization; even if we want to share it outside publicly, then we can have those capabilities."
"Compared to other vendors, this product is much faster in coming up with new features, which is good."
"Easy to use, nice UI, and good search functionality."
"I work for an information security company. CA API Management is capable of using tokens for authorization to manage access control for the APIs."
"You can create little, custom Java assertions that you can insert to do your business logic, which might not be covered by the commercial product out-of-the-box."
"The Gateway can front our APIs very easily."
"It is flexible in how it creates custom policies and uses builds with impressive methods."
"It's a comprehensive tool that allows us to perform all the necessary tasks in one place."
"It impresses me as a product because it never goes down. It always does what it is supposed to do."
 

Cons

"The solution is overly complex."
"The new version is very unstable."
"The monetization of the API could be improved. The pricing for the consumer is also very important to improve this solution."
"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."
"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."
"The installation was difficult with the IBM toolkit."
"Our main pain points are in these two areas: creating a better developer portal and improving stability in terms of synchronization and monetization."
"Understanding the architecture, deployment criteria, and communication methods of the installation can be time-consuming."
"One specific feature that we need is the ability to authenticate directly to the server with API data. It's not complex nowadays. This is a feature that we need and CA doesn't have it."
"As well as the SOA Gateway - that is, the API Gateway; we call it the SOA Gateway - we also are now deploying the developer portal component of the SOA Gateway. That has limitations."
"The entire lifecycle management approach needs improvement: from the API management, development, deployment, some of the settings around the quotas, and some security policy applications, etc. for the APIs. We found the Apigee platform a lot more robust in that area."
"The developer portal needs to fully supported SOAP services (including WSDL publication with security), it would certainly push adoption for us."
"The implementation of CA API Management was complex. It is a complicated solution. You have to know so much IT knowledge to do the implementation."
"​The initial setup was very complex."
"I understand that clients are often concerned about costs. They might be exploring other options due to the high cost associated with our current package."
"The CA API Management solution has good security features, but when it comes to being used in areas like enterprise integration, where it is being used as middleware for all the IT environments, that particular feature is quite limited. It doesn't support as many protocols as an industry standard, competing product should."
 

Pricing and Cost Advice

"It is a pretty expensive tool."
"Pricing for IBM API Connect varies, e.g. it could be subscription-based. Deploying it on private cloud also means you have to own most of the software licensing."
"There was a need to purchase an upfront license or a one-time license or upfront license, but I cannot remember the details about it clearly."
"The price of the solution is very expensive, it can turn many customers away."
"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."
"API Connect is expensive - I'd rate their pricing five out of ten."
"IBM API Connect could be cheaper."
"It would be a good idea to bring down the pricing by at least 20 to 30 percent."
"CA has great pricing for gateways, so negotiate with your sales team."
"If you do a TCO of more than five years, then you will see a big jump in costs for some vendors."
"Pricing for Layer7 API Management is excellent, so it's an eight out of ten. The product is less expensive than other solutions. Layer7 API Management charges you based on the number of transactions, so the enterprise-level pricing my company got was excellent."
"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."
"The price of Layer7 API Management is too high and should be reduced. However, it is a good solution in the market."
"It is a pricey product, although not extremely overpriced compared to competitors in the market."
"Layer7 API Management is cheaper than Apigee."
"Do not buy piecemeal."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
21%
Financial Services Firm
18%
Insurance Company
10%
Computer Software Company
9%
Financial Services Firm
20%
Computer Software Company
13%
Manufacturing Company
9%
Government
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
Price depends on many factors like size of the deal, competitive factors, timing, customer profile or where the pricing for API Calls is very competitive comparing to any of the leader players.
What needs improvement with IBM API Connect?
The only downside where improvements are needed is probably on the licensing side. Scalability is an issue with IBM API Connect, making it an area where improvements are required.
What needs improvement with Layer7 API Management?
Layer7 API Management could be improved in its logging and alert mechanisms. Furthermore, although cloud deployment has been introduced, I am not familiar with all recent updates. In previous versi...
 

Also Known As

No data available
CA API Management, CA Live API Creator, Espresso Logic, CA API Gateway
 

Learn More

 

Overview

 

Sample Customers

Heineken, Tine, Finologee, Axis Bank
1. IBM  2. Microsoft  3. Oracle  4. Salesforce  5. SAP  6. Cisco  7. Dell  8. HP  9. Adobe  10. VMware  11. Accenture  12. Capgemini  13. Deloitte  14. PwC  15. Ernst & Young  16. Infosys  17. TCS (Tata Consultancy Services)  18. Wipro  19. Cognizant  20. HCL Technologies  21. Tech Mahindra  22. Fujitsu  23. Hitachi  24. NEC  25. NTT Data  26. Ericsson  27. Nokia  28. Siemens  29. AT&T  30. Verizon  31. Vodafone  32. Orange
Find out what your peers are saying about IBM API Connect vs. Layer7 API Management and other solutions. Updated: January 2025.
831,265 professionals have used our research since 2012.