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

Layer7 API Management vs TIBCO Cloud 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

Layer7 API Management
Ranking in API Management
11th
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
111
Ranking in other categories
No ranking in other categories
TIBCO Cloud API Management
Ranking in API Management
29th
Average Rating
7.0
Reviews Sentiment
6.5
Number of Reviews
11
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2025, in the API Management category, the mindshare of Layer7 API Management is 3.0%, down from 3.2% compared to the previous year. The mindshare of TIBCO Cloud API Management is 0.8%, down from 1.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
API Management
 

Featured Reviews

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.
Amitava Roy - PeerSpot reviewer
Offers pre-built packages for quick and easy onboarding of APIs but configuration is not that easy
The configuration is not that easy. It's not that user-friendly, and security-wise when you try to implement the security layer on top of it, it's not that easy either. There are certain things where the performance is not that great. When the traffic is huge, we see some lag in performance.

Quotes from Members

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

Pros

"The administration interface (Policy Manager) is very easy to understand and use."
"Containerization and the monetization module are quite unique for an API tool... In addition, the development time and rollout time are pretty quick."
"The initial setup process is easy and flexible."
"The solution fills our two most important concerns in seeking an API solution by providing a reliable gateway and security options."
"The latest version that just came out at the first of October really was a powerful move in the right direction. I was very, very pleased with that because it allows now beginning to use information of things. We've got this IOT infrastructure that we can plug into, and for my use cases there are a lot of outdoor sensors that provide valuable information to my customers."
"Easy to use, nice UI, and good search functionality."
"We have more than 50 applications in the backend. We monitor the infrastructure through a database monitoring tool. Our daily tasks involve working on P1 incidents, managing change requests, conducting patching updates, working on P2 tickets, backend server certificate renewals, etc."
"We are able to go to market very quickly and deploy our functionalities very quickly."
"The most valuable feature is the ability to have different packages based on the API keys. The same core system can have different packages based on different environments."
"We can completely manage the APIs at the org level and BU (business unit) level."
"The control that we have and the security features are very valuable. With regard to API implementation or API orchestration, it works very well in the cloud because as soon as you create an API with one click, you can actually expose your APIs."
"Conversion to RESTful and SOAP protocols and management console (can manage individually throttled settings to manage our service levels for customers)."
"It has something called packages. In that way, it's good because we have some pre-built packages. So, if you want to onboard different APIs, we can just add them to the package, and it's there."
"It is easy to work with ."
"The most valuable aspect of Mashery is its stability."
"The solution is a good general API manager. They have a few propriety features but are offering items that are standard in the industry as well."
 

Cons

"The solution should prioritize ease of use and align with the growing trend of cloud-native environments."
"It would be nice if we could create APIs directly from Swagger files. We're doing that ourselves with a middle layer. But if you could integrate with open API Swagger specs, and then just create a Swagger and upload it to the gateway and it would create all my API template policy, and would apply the OAuth restrictions, the types of security restrictions I have on there, that would be pretty cool."
"we cannot add gateways on the fly because there are a lot of moving parts; endpoint connectivity is one of them. If we add more nodes then the rate-limiting feature is affected. This kind of gateway always has the scalability issue. But, I think CA is coming up with its Microgateway, which is in Beta. If they stabilize their Microgateway platform, we could do very well in terms of scalability."
"The UI design could be improved in the next release."
"The Portal lacks maturity. Since the move from Portal 3.x to 4.x, a lot of features were removed. It is slowly coming back. I can see a lot of changes are done in the "background" to decouple components and make it more flexible. Those changes are just not getting to the UI side quick enough."
"The product's initial setup phase is not very straightforward, making it an area where improvements are required."
"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."
"The only issue we have is that we have to buy an APM license separately for end-to-end monitoring."
"The way agile life cycle is working needs improvement. I also want to see more support for open API standards. I want to see some improvement on the protocol transformation. That is quite missing now. These are the three main issues."
"Policy management has been a bit of a concern."
"We observed delays under heavy load conditions, and without proper tuning, changes could take an extended period to filter and become effective."
"They can fix some stability issues and probably make it more user-friendly so that not only an IT savvy person but an end-user can also easily navigate through this solution."
"The security needs improvement, specifically, propagation of security to an API. Calling other APIs is something that is missing in the product and that makes us think about going to a competitor."
"Monetization is not that great in API management. You need customization. Improvements are needed with sandbox local as well as with monetization. Those features are missing."
"It's not that user-friendly, and security-wise when you try to implement the security layer on top of it, it's not that easy either."
"The management console of API and customers' applications are not the most intuitive."
 

Pricing and Cost Advice

"Layer7 API Management is cheaper than Apigee."
"We weren't comfortable with the pricing of licensing. It was slightly more expensive than its competitors."
"Be aware of additional licenses for your warm standby. Ensure you get plenty of non-production licenses."
"If the CA pricing for API management would be a little lower, they would be able to cover a broader market."
"APIs can be developed to provide security. We can show them in one single pane of glass, such as the CA API Management API Developer Portal. It is there that we can provide the monetization for their APIs and what is happening on third-party applications, like Paytm or BookMyShow."
"The price of Layer7 API Management is reasonable compared to Apigee."
"The product is moderately priced."
"There is an annual license for the use of this solution. I think we are paying for some support maintenance fees, included in that license. I don't know how it works. They should provide more information."
"Licensing is quite flexible."
"We have secured terms on which we have been happy to renew for a number of years."
"TIBCO Cloud API Management is not an expensive solution."
"Its price is pretty reasonable. There are some lightweight API options available in the market, but given the feature set that TIBCO provides, its price is really reasonable."
report
Use our free recommendation engine to learn which API Management solutions are best for your needs.
838,640 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Computer Software Company
13%
Manufacturing Company
9%
Healthcare Company
6%
Computer Software Company
25%
Financial Services Firm
14%
Manufacturing Company
10%
Real Estate/Law Firm
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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...
What do you like most about TIBCO Cloud API Management?
The platform's most valuable features are its capabilities to support security measures such as tokenization, token refresh, throttling, and enforcement of payloads.
What is your experience regarding pricing and costs for TIBCO Cloud API Management?
My primary role was to assess the solution from a capability perspective. So, there are some issues with the licensing cost.
What needs improvement with TIBCO Cloud API Management?
The configuration is not that easy. It's not that user-friendly, and security-wise when you try to implement the security layer on top of it, it's not that easy either. There are certain things whe...
 

Also Known As

CA API Management, CA Live API Creator, Espresso Logic, CA API Gateway
Mashery API Management
 

Overview

 

Sample Customers

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
uShip, Sabre, TouchTunes, Best Buy, Cisco, Comcast, athenahealth, Coca-Cola Enterprises, CentralIndex.com, Constant Contact, Edmunds.com, FoodEssentials, Getty Images, Klout, Rovi, Rotten Tomatoes, Sportradar, TomTom, ACTIVE.com
Find out what your peers are saying about Layer7 API Management vs. TIBCO Cloud API Management and other solutions. Updated: January 2025.
838,640 professionals have used our research since 2012.