

IBM API Connect and Axway AMPLIFY API Management compete in the API management category. IBM API Connect appears to have the upper hand due to its comprehensive lifecycle management and integration with IBM services.
Features: IBM API Connect offers robust security gateways, GUI-based API development, OAuth support, holistic API management, and integration with IBM products like DataPower Gateway. Axway AMPLIFY API Management is strong in security, handling large data volumes, and providing governance. It efficiently manages APIs across different systems and offers a competitive pricing model.
Room for Improvement: IBM API Connect could improve integration with Exchange Server, ease of setup, monetization, stability, and documentation. Axway AMPLIFY API Management should aim to enhance scalability, microservices support, usability, installation simplicity, and customer support. IBM's proprietary tools can limit flexibility, whereas Axway focuses on deployment and service improvements.
Ease of Deployment and Customer Service: Both products provide versatile deployment options: on-premises, hybrid, and public cloud. IBM API Connect receives mixed reviews for customer service, with reports of slow response times. Axway, though having less available data on customer service, offers a streamlined deployment process. IBM's global deployment caters to diverse operational needs, while Axway prioritizes centralized solutions.
Pricing and ROI: IBM API Connect is considered expensive with its complex pricing structure, but its integration capabilities justify the cost for large operations. Axway offers a competitive yearly subscription model with full feature access, attracting budget-conscious users. Both solutions promise ROI, though IBM might deliver a higher return due to its extensive governance and security capabilities.
I have seen a return on investment through faster API delivery and greater governance, with my development team now spending less time managing API security and access control manually.
After standardizing authentication and gateway policy checks, the time needed to execute our core API regression suite decreased by roughly twenty to twenty-five percent.
Reducing development hours from eighty to four for an API was possible due to reusing existing scripts from DataPower.
I have seen a return on investment from using IBM API Connect, as we created multiple plans based on customer usage.
We have an engagement partner from Axway, and their technical and product teams are very supportive whenever we need clarifications or urgent confirmations.
If they understand that an issue is a bug or something that needs to be improved in their tool, they take it as improvement feedback and deploy patches in the next update.
A better turnaround time for non-critical tickets would be beneficial, as I sometimes have to wait three to five days for an issue to be resolved.
Support is excellent when it comes to APIC.
Support is extremely good, especially with Sev 1 issues.
It was frustrating that we almost could not install it by ourselves because some information I will never find because IBM keeps it.
The scalability of Axway AMPLIFY API Management is also great, and I would rate it around eight, given that we have scaled it up to twenty-eight hundred to thirty-five hundred APIs hosted on the gateway without performance degradation.
I can expand the platform without making significant changes to the overall architecture.
Regarding scalability for Axway AMPLIFY API Management, it can scale up to N servers.
When you have Kubernetes on cloud or on-premise, scalability is easy.
With container versions, scaling up or down the gateways deployed into pods is a two to three-minute task for the operations team.
It is distributed among IBM MQ, IBM Ace, IBM DataPower, and IBM API Connect.
I would rate the stability of Axway AMPLIFY API Management at around nine or nine point five, as we have not experienced any outages, and performance testing shows CPU utilization barely reaching seven to ten percent even under heavy loads.
Since banking and financial organizations prefer to use it, their preference validates its stability.
During high traffic periods, the dashboard struggles to load, and the system can go down, which complicates reporting and analysis.
The runtime engine for the APIC Gateway is still a DataPower component, which has been stable in the industry for about fifteen years.
If it is functioning well, you won't have a bad experience and your application becomes more reliable.
IBM API Connect was very stable.
When there is a very large volume or very large number of transactions going on live in production, sometimes it purges the previous data very quickly, leaving only one or two hours of data.
From the functionality perspective, I am completely satisfied with Axway AMPLIFY API Management from the gateway aspect, although the portal does have scope for improvement.
When we modify the API and resend it back to the server, we need to do several checks again to ensure that the API received from the target server works normally and that what we modified from the API is acceptable.
Examples include the lack of connectivity to MQ.
You need to know when traffic peaks, so use auto-scaling when traffic comes.
Connectivity to MQ is not available in IBM API Connect.
This model provides a cap of around one hundred fifty thousand calls per month that gives us the flexibility to host many gateways but at a cost based on production traffic.
It is an expensive tool at the time of purchase and licensing.
The pricing for Axway AMPLIFY API Management is quite high for small companies, organizations, or teams.
Pricing depends on how many instances run across environments.
Axway AMPLIFY API Management sits in the DMZ zone, outside the security firewalls of the organization, allowing us to intercept all calls originating from external sources, validate and check for threats, including SQL injection attacks, malware, and potential spamming from excessive API calls that could deny legitimate users access.
Its policy management feature capabilities are excellent, making it very easy to enforce security and governance standards across all APIs, and the developer portal is a very useful feature that helps my team discover and efficiently consume APIs.
The feature I rely on most in Axway AMPLIFY API Management is policy-based security and access control because from a QA perspective, it gives me a consistent way to test authentication and authorization scenarios at the gateway level before requests reach the backend.
It offers significant development efficiency, reducing man-hours from eighty to four when creating APIs.
We can add some policies to provide extra security, protect your backend, validate the consumers, and analyze based on the traffic limit to throw things out.
IBM API Connect has a designer and CLI features which can be used to completely automate the API.
| Product | Mindshare (%) |
|---|---|
| IBM API Connect | 4.7% |
| Axway AMPLIFY API Management | 1.8% |
| Other | 93.5% |


| Company Size | Count |
|---|---|
| Small Business | 4 |
| Midsize Enterprise | 2 |
| Large Enterprise | 12 |
| Company Size | Count |
|---|---|
| Small Business | 19 |
| Midsize Enterprise | 10 |
| Large Enterprise | 62 |
Axway AMPLIFY API Management offers secure and user-friendly API management solutions supporting flexible deployment options while ensuring robust security for data exchange and centralized management for developers.
Axway AMPLIFY API Management emphasizes strong security measures against threats, facilitating authenticated data exchange. Its centralized management tools enable efficient API analytics and portal usage. The platform's flexible deployment options, including on-premise and cloud solutions, are coupled with a user-friendly interface featuring drag-and-drop functionalities to streamline operations. However, improvements are needed in Amplify Central portal, customization features, and scalability options. While used primarily as an API gateway for internet, web, and REST APIs, companies leverage its features to create secure connections and integrate APIs internally and externally, fostering a comprehensive API ecosystem.
What are the key features of Axway AMPLIFY API Management?In the financial services industry, Axway AMPLIFY API Management is integral in creating secure marketplaces and ensuring reliable communication among partners. Its robust security and hybrid-cloud capabilities make it ideal for creating sophisticated API ecosystems, facilitating both internal and external integrations essential for modern operations.
IBM API Connect is an API management tool providing robust security, seamless REST and SOAP conversion, and flexible deployment options for diverse cloud environments. It aids organizations in securing and monetizing their APIs while streamlining the development process.
IBM API Connect offers features like a security gateway, API lifecycle management, and integration with DataPower. Its intuitive interface enhances ease of use, supporting extensive analytics and traffic management. However, there are areas for improvement in automation, system integration, and user configuration. Organizations can deploy API Connect on-premises or in the cloud, delivering secure access control and analytics for banking, financial services, and government sectors. Compliance with standards like PSD2 ensures secure external API exposure and integration with multiple systems.
What are the most important features of IBM API Connect?In specific industries like banking, financial services, and government sectors, IBM API Connect plays a crucial role in API management, orchestration, and regulation tasks. It provides secure access, control, and compliance with industry standards, serving as an essential gateway for data exchange and integration across multiple systems.
We monitor all API Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.