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

Flowgear vs IBM API Connect comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 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

Flowgear
Ranking in Integration Platform as a Service (iPaaS)
24th
Average Rating
9.6
Reviews Sentiment
7.9
Number of Reviews
7
Ranking in other categories
No ranking in other categories
IBM API Connect
Ranking in Integration Platform as a Service (iPaaS)
8th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
76
Ranking in other categories
API Management (8th)
 

Mindshare comparison

As of August 2025, in the Integration Platform as a Service (iPaaS) category, the mindshare of Flowgear is 0.3%, up from 0.2% compared to the previous year. The mindshare of IBM API Connect is 2.9%, up from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Integration Platform as a Service (iPaaS)
 

Featured Reviews

Fulufhelo Sibei - PeerSpot reviewer
Fast support, good data ingestion, and a nice UI
I am happy with the product. It has solved our business challenges. It is easy to integrate into multiple sources. We did have to use a data transformation tool which would take months to map and transform data that was being dumped into our secure file transfer. Previously, by the time we finished ingesting the data, it was no longer relevant. This has since changed. Therefore, there are no areas needed for improvement.
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.

Quotes from Members

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

Pros

"The no-code visual front end, along with pre-built samples, allows someone with very little technical ability to get an integration up and running."
"The Flowgear tool is helping us reduce the manual work that is done."
"It has improved our integration with our data supplier."
"Being able to seamlessly make changes to how one can do mapping visually without having to be a seasoned developer is great."
"Great for data flow."
"Well-managed version control of workflows and the simplicity in promoting workflows through each environment has aided my team in developing workflows for various environments without the risk of losing development work."
"The solution has increased efficiency and productivity and saved us time and money."
"Using API Connect allows us to quickly create proxy APIs and saves time on end-to-end testing, which lets us deliver quickly to clients."
"The product gathers data to measure API performance."
"API Connect's most valuable feature is its ability to act as a gateway. It's very easy to configure security and everything else in it. You don't have to kill yourself implementing custom configurations."
"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."
"This is a very easy to use solution."
"This solution is ready to scale and already supports our agile CICD."
"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."
"I have found the API Management to be most valuable."
 

Cons

"The initial setup was a bit complex as we were new."
"The product needs to improve the self-help tools and samples."
"The software itself needs to keep up with the daily demand to service all clients as the need arises."
"Currently, when designing and testing larger workflows, the sessions timeout and re-authentications are frequently required."
"The product would be nice if it could provide the deployment features in the lower packages."
"We would like to see more learning videos for beginners."
"The UI could be improved."
"The installation process could use improvement. I hope that in the next release, the installation process is easier."
"The new version is very unstable."
"I would like to see support for non-Java based services. We struggle a bit to be able to deploy and connect our .NET services because of things like data types. We had to map a couple of things. For one solution provider, we had to move them to .NET Core before we could use it properly. I would like to see more agnostic tool service platforms rather than moving it more towards Java or open source."
"Improving the documentation would be beneficial as it currently presents navigation challenges. Incorporating a step-by-step guide could facilitate the integration or migration of various systems, including databases. The existing documentation only comprises plain text, hence incorporating more interactive instructions could enhance its usefulness."
"They seem to have left out a feature for microservices and also a certification module for OIDC."
"The solution is not scalable."
"Firstly, the pricing model, when compared to other open sources, is high. Secondly, the availability of resources in the market, specifically the developers available in the market, is not so much."
"There are issues with upgrading in the cloud version. The cloud version is extremely buggy. We prefer to use the on-premise version."
 

Pricing and Cost Advice

Information not available
"It is an expensive solution. The licensing model is based on a per-subscription and per-subscriber end-user basis, meaning the price is determined by the end-users of the platform."
"It would be a good idea to bring down the pricing by at least 20 to 30 percent."
"IBM API Connect could be cheaper."
"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."
"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."
"It can be quite expensive. It's okay for large-scale usage but quite expensive for smaller-scale implementations."
"API Connect was highly expensive for us, but the decision to switch was made before I joined the company. It seems like the company bought it, but they didn't know how to use it. After two years, they decided to reevaluate and conduct some cost estimates."
"The price of the solution is expensive. However, there are a lot of customization capabilities."
report
Use our free recommendation engine to learn which Integration Platform as a Service (iPaaS) solutions are best for your needs.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
20%
Insurance Company
13%
Computer Software Company
11%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Ask a question
Earn 20 points
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...
 

Overview

 

Sample Customers

Information Not Available
Heineken, Tine, Finologee, Axis Bank
Find out what your peers are saying about Flowgear vs. IBM API Connect and other solutions. Updated: July 2025.
865,384 professionals have used our research since 2012.