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)
27th
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)
9th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
76
Ranking in other categories
API Management (8th)
 

Mindshare comparison

As of October 2025, in the Integration Platform as a Service (iPaaS) category, the mindshare of Flowgear is 0.3%, up from 0.3% compared to the previous year. The mindshare of IBM API Connect is 2.7%, up from 1.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Integration Platform as a Service (iPaaS) Market Share Distribution
ProductMarket Share (%)
IBM API Connect2.7%
Flowgear0.3%
Other97.0%
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 Flowgear tool is helping us reduce the manual work that is done."
"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."
"Being able to seamlessly make changes to how one can do mapping visually without having to be a seasoned developer is great."
"The solution has increased efficiency and productivity and saved us time and money."
"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."
"It has improved our integration with our data supplier."
"The management of the API and API portal is good."
"In-built policies and security functions."
"Policy configurations are pretty easy."
"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 solution offers a pretty good SLA."
"WSRR is a powerful component for getting the endpoints."
"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."
"The solution's technical support team is good."
 

Cons

"The software itself needs to keep up with the daily demand to service all clients as the need arises."
"The product needs to improve the self-help tools and samples."
"Currently, when designing and testing larger workflows, the sessions timeout and re-authentications are frequently required."
"The initial setup was a bit complex as we were new."
"The product would be nice if it could provide the deployment features in the lower packages."
"The UI could be improved."
"We would like to see more learning videos for beginners."
"The implementation of IBM API Connect is complex, as it's an enterprise solution with many components that require more than one person. It's not a single product that you work on, and this is an area for improvement, but normally, it's good. Having a more structured model for IBM API Connect support is also room for improvement that would help customers better."
"There are some performance issues and issues related to asynchronous APIs."
"IBM API Connect could improve the security of the application and the integration."
"There is room for improvement regarding the connectivity of the DevOps."
"Different versions of the same thing can mean unnecessary duplication."
"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."
"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."
"Automation for our Domino applications could be improved."
 

Pricing and Cost Advice

Information not available
"It's an expensive product."
"The price of the solution is very expensive, it can turn many customers away."
"It would be a good idea to bring down the pricing by at least 20 to 30 percent."
"The pricing is significantly high."
"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."
"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."
"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."
report
Use our free recommendation engine to learn which Integration Platform as a Service (iPaaS) solutions are best for your needs.
869,566 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business7
Large Enterprise1
By reviewers
Company SizeCount
Small Business19
Midsize Enterprise10
Large Enterprise58
 

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: September 2025.
869,566 professionals have used our research since 2012.