Cleo Integration Cloud vs. IBM API Connect

CLEO Integration Cloud is well suited in any environment where you need to move and translate business data from one format to another or multiple other formats. It is very well suited to replace existing EDI systems that are cumbersome, are a lot of work to add new mappings (add customers for example), or where the support is lousy and you are constantly creating support tickets to try to resolve issues. It just works very well and is constantly improving including keeping up to changes made by various services such as Shopify.

Incentivized

Based on our experience, IBM API Connect clearly excels in large enterprises navigating complex B2B ecosystems, especially within the Fintech and Banking sectors. Its capabilities are particularly valuable for achieving Open Banking compliance, facilitating the monetization of data and services, and seamlessly operating in hybrid cloud environments. However, it's crucial to understand that IBM API Connect primarily functions as an API management and orchestration tool. This means that backend integrations with providers like databases are best handled by dedicated integration middleware, such as IBM App Connect, allowing API Connect to then securely and efficiently expose those functionalities to external entities.

• A great platform perfectly integrated with the rest of the company's software.
• Detailed design with simple and easy access from anywhere to our information.
• Multi-location and multi-device access.
• We save on hardware, software and maintenance, by minimizing the user's need for powerful equipment and the programs in charge of managing and configuring them, reducing the investment in their acquisition.
• Cleo integration is in charge of technical maintenance and updates.

Incentivized

• API discovery feature is very helpful to allow us to scope the work required before diving into things.
• The ability to set permissions and rulesets at a user level is essential to restrict access to specific datasets.
• Ability for external users (those from outside our organisation) to leverage the API in more restrictive manner.

Incentivized

• A fully functional help manual would be good. Some topics have no help at all, "envelopeassemblybycontext" for instance.
• A needed feature is to be able to sort files by either file type (FM, RS, BPS) or by filename. Some of our projects have almost a hundred files.
• Better, more descriptive error messages. Sometimes a ruleset or process fails and the error message is not helpful.

Incentivized

• Improvement can come in the interface of the tool, which is sometimes complex and requires a deep understanding of the tool.
• Improving the different levels of access to the playroom could be helpful because product owners and developers need to see other information.
• Publishing API and integration of API can be more straightforward.

Incentivized

Ease in understanding and setup.

Incentivized

I can honestly say that the availability of the platform has been incredible, with almost no disruptions during the two years of the implementation. Availability is provided through the distributed architecture that may be deployed in multiple zones. We have had almost no cases of unplanned outages, and most maintenance operations were done during planned downtimes.

Incentivized

Great data manager in the cloud, at a competitive price, backed by a great company and great professionals.

Incentivized

Before choosing a solution, we did a detailed analysis of cost, performance, scaling and support. Cleo checked all the right boxes and we have been very satisfied with our choice.

Incentivized

IBM API Connect and Apigee are both robust API management platforms. IBM API Connect was selected for its strong integration capabilities, hybrid cloud deployment options, and comprehensive analytics. It aligns well with organizations seeking flexibility and control over their API ecosystems, especially when dealing with complex integration scenarios across diverse environments.

Incentivized

• We have easily improved our EDI tenfold (or more) as far as ease of adding new customers for example
• We have saved a ton of money by reducing chargebacks for missing ASNs for example
• We have improved customer scorecards where they measure our EDI performance such as one large brand name customer we sell wholesale to who originally scored us around 28% and after implementing CLEO we quickly went to a 96%+ score.

Incentivized

• Our company benefited from IBM API Connect's assistance in establishing cooperation with our outside providers and efficiently managing the API. As a result, we were able to expand our vendor ecosystem.
• Additionally, creating APIs and implementing them on the goods was not too difficult. Additionally, we were able to ensure that only appropriate people could publish the APIs following evaluation by using role-based access control.
• Our teams were able to reuse and share departmental APIs and services with each other thanks to the simple, self-service developer site.

Incentivized