No more typing reviews! Try our Samantha, our new voice AI agent.

IBM App Connect vs TIBCO Cloud Integration comparison

 

Comparison Buyer's Guide

Executive Summary

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 App Connect
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
26
Ranking in other categories
Cloud Data Integration (14th)
TIBCO Cloud Integration
Average Rating
8.4
Reviews Sentiment
8.5
Number of Reviews
3
Ranking in other categories
Integration Platform as a Service (iPaaS) (22nd)
 

Mindshare comparison

IBM App Connect and TIBCO Cloud Integration aren’t in the same category and serve different purposes. IBM App Connect is designed for Cloud Data Integration and holds a mindshare of 2.0%, down 4.4% compared to last year.
TIBCO Cloud Integration, on the other hand, focuses on Integration Platform as a Service (iPaaS), holds 2.0% mindshare, up 1.0% since last year.
Cloud Data Integration Mindshare Distribution
ProductMindshare (%)
IBM App Connect2.0%
AWS Glue7.6%
Informatica Intelligent Data Management Cloud (IDMC)6.7%
Other83.7%
Cloud Data Integration
Integration Platform as a Service (iPaaS) Mindshare Distribution
ProductMindshare (%)
TIBCO Cloud Integration2.0%
Boomi iPaaS6.9%
MuleSoft Anypoint Platform6.7%
Other84.4%
Integration Platform as a Service (iPaaS)
 

Featured Reviews

Nirav Patel - PeerSpot reviewer
Senior QA Engineer at a tech vendor with 1,001-5,000 employees
Cloud workflows have accelerated integrations and now demand better debugging and DevOps support
IBM App Connect provides many features, but there are several areas for improvement. Better debugging and observability would help us track any single transaction end-to-end across steps and connectors. Features such as a step-by-step line view and one-click download for flow execution would be beneficial. Improved CI/CD pipeline and GitOps experience would be valuable. The team wants flows as code and predictable promotion across development, test, and production environments. Stronger native Git integration, export-import functionalities, and first-class pipeline templates like Jenkins, GitHub, and Azure DevOps would be beneficial. More cloud-native, lightweight runtime options would be very helpful. Connector reliability and consistency need improvement because some connectors feel more mature than others, and version changes can break mapping. Pricing and licensing clarity is important because the licensing is complex and can slow down adoption and planning. Some improvement areas include handling very complex structures that the platform currently does not support. Improvements on the DevOps side, particularly providing templates, would be beneficial. The platform is somewhat expensive and hard to predict in terms of cost. Debugging features need to be provided. For CI/CD, the flows are not truly accurate and need improvement.
NarendraThota - PeerSpot reviewer
Vice President of Technology Services at a computer software company with 501-1,000 employees
A product that is easy to install and offers good stability to users
The API part of the solution is an area in the solution where improvements are made since I see that TIBCO is currently trying to revamp its tool by focusing more on redesigning it. There was a tool called Mashery, which is an API management tool that was acquired by TIBCO. TIBCO Cloud Integration is not a user-friendly tool when it comes to the installation phase or for maintaining the systems since its architecture is really complex. I think in the UK, one of the major telecom providers for whom I had done the infrastructure setup uses TIBCO Cloud Integration. Basically, TIBCO Cloud Integration is a bit difficult to install and manage the platform, but I feel there are improvements in the tool's latest version, especially on the API management side. Instead of moving to the higher version and converting the older version of TIBCO Cloud Integration or the legacy platform covered under TIBCO, they still use it because the architecture is completely different, and the components that the product has are completely different from what the new version of the product offers, making it one of the major reasons why TIBCO is coming up with a new version of the product that will be released in the upcoming year. The legacy platform of TIBCO will run on the cloud directly. TIBCO plans to develop a unified tool that is supported on the cloud and in an on-premises environment.

Quotes from Members

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

Pros

"The solution is a good product in the integration space and a leader in the market."
"This solution is used as the integration hub between the internal application of any enterprise."
"We use IBM App Connect for the integration between the applications."
"The most valuable feature for me is the availability of the adapters, which are already made out of the box."
"The solution is very fast-paced when it comes to making things right. We can quickly download what we need if we need any app migrations for our software business. We can download it plenty of times when we need to use it. It gives us very high speed for delivering any development."
"I would say that the most valuable feature is the array of connectors and integration tools."
"It's a powerful application for collaboration. It has many features for customization and integration."
"IBM App Connect definitely saves a lot of time, approximately 50 to 60%, and based on the time savings, we can reduce the number of employees needed and save money on reduced resources."
"The product's initial setup phase was easy."
"The initial setup was straightforward and because we often work with one of the most interesting companies in integration in Italy, what the program offers is absolutely outstanding."
"I like that it is a very good integration tool with many other things; TIBCO is very good for cloud integration."
"I am really impressed by TIBCO's integration of any level of complexity."
 

Cons

"IBM needs to enhance and have a stronger offering for the event streaming part because this is the future needed for the containerization and the new integration requirement."
"The interface could be better."
"Finding developers for the product is difficult since it is a niche solution. I know the OpenShift environment is running well for the microservice environment. We had some issues with the other environment we tried to implement. It can be easily implemented internally, but we have some problems in practice."
"Updates are constantly delayed and that is something IBM could improve."
"I've been using IBM App Connect for about twenty-five years, and while I like it, there are some areas for improvement. The trace policy is ridiculous, and the biggest issue is the cost—it's expensive. People would use it much more if the price point weren't so high."
"Plugins for the repositories are a little difficult to find."
"IBM App Connect occasionally crashes for various reasons, requiring problem-solving intervention."
"When we do a version upgrade of the system, the platform is kind of complicated."
"Integrations could be better. Although integration is good, we have faced some block issues."
"The deployment was rather complicated."
"TIBCO Cloud Integration is not a user-friendly tool when it comes to the installation phase or for maintaining the systems since its architecture is really complex."
"It is an extremely powerful solution, but it is very expensive, even though it only offers adequate functionality."
 

Pricing and Cost Advice

"The price could be better."
"The solution's pricing isn't cheap, but you can get good discounts based on your competitive deal."
"Initially, App Connect was quite expensive because the cost was based on the number of processors we used. However, it's now based on containers, which means we can be more specific about our consumption and get a better price."
"It is very expensive if we want to scale."
"IBM App Connect's pricing is high compared to other products."
"The cost depends upon the consumer."
"App Connect is not cheap."
"The licensing cost for IBM App Connect is very high."
"We don't pay for a license."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
902,417 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Manufacturing Company
14%
Computer Software Company
8%
Construction Company
7%
Construction Company
26%
Comms Service Provider
11%
Outsourcing Company
7%
Consumer Goods Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise4
Large Enterprise21
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for IBM App Connect?
Configuration time varies by implementation. For insurance companies with simple JDBC connections, the process is straightforward. However, companies requiring multiple configurations for ODBC, JDB...
What is your primary use case for IBM App Connect?
IBM App Connect serves as our integration platform, allowing us to connect application systems and data without heavy load or heavy coding. In my current organization, we use the AWS cloud, and IBM...
What advice do you have for others considering IBM App Connect?
We are using the private cloud deployment on AWS. My company purchased IBM App Connect through the AWS Marketplace. IBM App Connect is a very user-friendly tool, and we can very easily integrate wi...
Ask a question
Earn 20 points
 

Also Known As

IBM Cast Iron
No data available
 

Overview

 

Sample Customers

United Way of Allegheny County, Saint-Gobain CPS, Ricoh, SunTrust Banks Inc.
NASA, T-Mobile, EagleView, Air France KLM, Caesars Entertainment
Find out what your peers are saying about Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: June 2026.
902,417 professionals have used our research since 2012.