Axway AMPLIFY API Management Reviews

I have used Axway AMPLIFY API Management to expose and manage APIs across different internal and external applications, which helps secure the API, monitor traffic, and control access through policies. I mainly use it for integrating backend systems with mobile and web applications.

The primary use case of Axway AMPLIFY API Management for my organization is monetization. I have multiple segments based on how many times an API has been called, and we charge accordingly, making it very easy to monitor all APIs at once in one place.

Since using Axway AMPLIFY API Management, I have observed reduced downtime, faster onboarding, and improved governance and consumption of APIs across the organization. Onboarding is faster because developers can easily discover and access APIs through the developer portal, which has helped reduce the effort required to manage security and improved API visibility while reducing operational overhead.

Axway AMPLIFY API Management has positively impacted my organization, particularly in terms of scalability, as the platform has handled increased traffic without major issues. The service and support are very helpful and knowledgeable, with quick response times for critical issues.

The best features of Axway AMPLIFY API Management include centralized API management capabilities, allowing me to publish, secure, and monitor the management API from a single platform, which saves a lot of time and effort. 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 developer portal feature of Axway AMPLIFY API Management is very useful whenever internal teams or partner teams want to consume an API. I can directly visit the portal to view API documentation easily and can also request access and end-to-end test the APIs.

The AI capabilities of Axway AMPLIFY API Management are useful for identifying unusual API traffic patterns and providing security policy recommendations or insights on API performance and user trends. I believe it would also be useful if AI could assist with troubleshooting configuration issues, as the recommendations and security policies given by AI are quite good and summarize everything in one place. Adding troubleshooting capabilities and automatic optimizations would reduce manual effort and help manage APIs more efficiently.

The AI features of Axway AMPLIFY API Management enhance recommendation accuracy and reliability. Their suggestions are quite helpful, but sometimes recommendations require manual verification before implementation, meaning I do not rely completely on them. Improving the quality of insights and reducing false positives would be beneficial, as I have noticed multiple instances where the AI provided inaccurate information based on the workflow. Providing more context behind recommendations would boost confidence in using AI for my day-to-day API management.

Axway AMPLIFY API Management could be improved in terms of user interface and navigation, as it could be more user-friendly. There are no helping resources such as question marks or help icons to easily identify elements, making it difficult for new users to learn the platform without some form of training. The configuration and policy setups also require multiple steps, which complicates the process, and it would be easier if some steps could be skipped. Better analytics and reporting capabilities should provide improved trackability for API performance and consumer behavior.

Documentation for advanced use cases would help reduce the learning curve. However, when trying to integrate with third parties, it can be quite difficult and requires a lot of authentication and authorization, which is better for security but poses challenges for new users trying to connect with a third party to transfer data between platforms.

Additionally, the customization options for the dashboard are very limited, which restricts my ability to customize the entire dashboard meaningfully.

I have been using Axway AMPLIFY API Management for approximately four years, and during this period, I have worked on API publishing, security configuration, policy management, and monitoring across multiple projects.

I have experienced issues with Axway AMPLIFY API Management's stability at times, particularly when there are a large number of API calls. During high traffic periods, the dashboard struggles to load, and the system can go down, which complicates reporting and analysis. As a workaround, I often extract data and create reports offline.

Axway AMPLIFY API Management's scalability is very good, as it has handled my growing API landscape well. Although I encounter some minor issues as the number of APIs and consumers increases, I can expand the platform without making significant changes to the overall architecture. It generally performs well but starts to create some lag time when traffic increases by about twenty-five to thirty percent, making it suitable for large enterprises that need to manage a high volume of APIs.

Customer support for Axway AMPLIFY API Management is generally helpful and knowledgeable. The response time for critical issues is acceptable, although complex cases can take longer to resolve. 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. Communication with support is friendly, and they actively work to resolve issues via email.

The initial setup of Axway AMPLIFY API Management was moderately complex, requiring proper planning around the infrastructure, security, and integration with existing systems. Once the architecture was finalized, the implementation became much smoother.

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. The platform has also improved visibility into API usage, enhancing my operational efficiency and productivity.

The pricing for Axway AMPLIFY API Management is quite high for small companies, organizations, or teams. The setup cost is also high, and licensing is very limited. They should restructure everything to make it more affordable for smaller organizations.

In recent projects with one client, I worked on managing multiple APIs that they were not able to handle at once. I analyzed the APIs they were calling and the frequency of those API calls by using the dashboard on the management system, which helped me determine how many logs, including error logs, had occurred and allowed me to analyze the entire data of that API easily.

My advice for others considering Axway AMPLIFY API Management is that if you want a comprehensive API management solution that includes a good dashboard with analytics, log functionality, monetization, and security, everything comes under one roof, making Axway AMPLIFY API Management a solid choice. I would rate this solution an eight out of ten.

I am currently working on Axway AMPLIFY API Management, which is the Axway API platform. The main requirement for API management is that the API platform provides security to the different APIs which fetch data from the front end and back end. If a customer needs to fetch data from the back end, which could be any database or any organization that has the data, that customer goes through the API platform. Axway AMPLIFY API Management maintains security throughout the entire process. Whatever checks, credentials, API keys, authorization, or authentication is required by the database to confirm that the customer is valid is performed by the API platform.

The integration part of Axway AMPLIFY API Management works as a middleware platform and helps with integration with different parties on both ends. Think of it as an hourglass funnel where many different APIs sit at the top and slowly move downwards through that funnel. At the center is an API Gateway platform which checks every API, verifies all the security, processes all integration features, and sends the data downwards. From an integration point of view, the parties sitting at the top could be Mulesoft, Boomi, Dynamics 365, or any other specific tool that is integrated. The call goes from these tools to Axway and then to different vendors, which could be any third party or out-of-organization teams. Alternatively, data could come from outside the organization into the Axway system and then be sent to Dell, Boomi, or Mulesoft integration tools. Axway AMPLIFY API Management is capable of handling the integration in both directions, meaning both parties must integrate the specific API URL to reach the back end or front end.

The most valuable function in Axway AMPLIFY API Management is security. It provides customers with the security assurance that data they fetch from the back end is well authenticated before retrieval. If a customer needs to fetch data from the back end, that customer should be validated and there should be no loss of data or unauthorized access from outside the organization. The prime feature of the API Gateway platform is that it provides security of the API to move data back and forth between the front end and the back end.

The second valuable feature would be for developers. Axway AMPLIFY API Management is a centralized management platform where all developers can easily create, modify, or provide access lists to different stakeholders for various APIs. Developers can easily give specific access to a specific set of people for a specific set of APIs.

API analytics is useful for obtaining insight because it is a tool that gives analysis of the entire flow of APIs and the count of APIs. If there are one hundred APIs for a specific client, API analytics shows which ones are most used, to which back end they go, the flow according to specific areas that have maximum or lowest traffic, and what the traffic was for the last thirty, sixty, or ninety days. This graphical approach allows me to fetch reports on a monthly basis, conduct audits, and see which API gets the most hits and the most transactional count. API analytics is a matrix-based tool.

Potential areas of improvement or lack of functions in Axway AMPLIFY API Management is a challenging question because even after working for almost six years, I have not been able to touch everything this tool offers. This tool is very comprehensive and useful. However, from my opinion, when there are different dashboards on which the API platform shows monitoring, I expect Axway AMPLIFY API Management to be more visible in terms of showing pre-historic data. In other words, if 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. When there is very low volume, it can sustain data up to five days. The visibility of the previous historic database is a feature that could be improved. Different tools can be used to empower this capability, such as Splunk or the ELK stack, which includes Elastic. There are different features that could be used, but Axway as an organization would likely implement their specific products. I am simply providing a very basic opinion anonymously and do not want to sound like I am against this organization.

I have been working with Axway AMPLIFY API Management for approximately more than six years.

I would rate stability for Axway AMPLIFY API Management as nine out of ten. It is quite a stable tool. I have seen it handling more than twenty million transactions per hour, which is substantial. It handles high volumes very well. Since banking and financial organizations prefer to use it, their preference validates its stability.

Regarding scalability for Axway AMPLIFY API Management, it can scale up to N servers. The infrastructure must be compatible, meaning the requirements of RAM and disk size must be compatible in order to scale this tool.

I could rate the technical support as having always provided resolutions, with the matter being the time it takes, which sometimes takes more or less depending on the complexity of the issue. Sometimes issues are very tricky and the subject matter experts need to take additional help or perform testing at their end, which takes considerable time. However, they always provide a resolution. 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. They work very well on their tool.

Positive

The initial setup for Axway AMPLIFY API Management is not that difficult. They have very good documentation in order to set up or conduct the installation, so it is not that challenging.

Regarding pricing for Axway AMPLIFY API Management, I cannot say definitively because it depends on the transactional volume expected by customers. I would not be able to give the final answer, but overall, it is an expensive tool at the time of purchase and licensing. I cannot provide the complete answer on this part.

When comparing Axway AMPLIFY API Management with competitors like AWS or Azure, I would not be able to answer very accurately because I am not familiar with Kong. However, when it comes to AWS API Gateway or Azure, they both have a slight advantage compared to Axway AMPLIFY API Management. The reason is that Axway AMPLIFY API Management is specific to their API tool, but AWS and Azure provide different integration capabilities within their own cloud platform. They have their EC2 instances, their own databases, their own connectivity within the system, plus the cost would be like a pay-as-you-go model. Ultimately, from a very high-level overview, cloud platforms or Kong could have a slight advantage when compared to Axway AMPLIFY API Management. However, this does not mean that Axway AMPLIFY API Management is bad. Axway AMPLIFY API Management is niche technology that people prefer because it has emerged beautifully. It has very nice support and enterprise-level features which are not provided by cloud Azure or AWS, which is an advantage of Axway AMPLIFY API Management.

The main benefits end users receive from Axway AMPLIFY API Management are numerous. Axway is an organization that creates different tools in the market. They have API, B2BI, and multi-file transfer known as MFT or FT. In the API area, Axway has been beautifully immersed from around 2014 to 2016 onwards and has captured the market in a beautiful way. The crux is that they are a product-based organization, which means they have their own licenses and costs for bearing those licenses, plus costs for conducting training online, which is not open source. I must pay the organization to get that training. These are the perks and cons of the organization. Competitors such as AWS API Gateway, Kong API Gateway, or Azure API-M are pretty good competitors of Axway. AWS and Azure are huge platforms that provide multiple different features to users, so API Gateway is just one of their one hundred applications. They are focused on many things. If I am at AWS, I can use Lambda along with AWS API Gateway, and there is a database and everything included. Although Axway AMPLIFY API Management has a very good niche market, the demand of users and employees using this tool is quite niche and not very easily available. When the organization needs to be performed right away at ground zero, the demand comes up. However, this does not mean that open source tools, such as AWS API Gateway, which has good training on the YouTube platform and different platforms, does not give competition to Axway. Axway AMPLIFY API Management has a specific feature in that since it is product-based, they have their own dedicated support team, their own escalation matrix, and subject matter experts. Whenever I am facing any issues at a platform level or product level, they provide a good timeline resolution. AWS and other organizations follow the same flow, but I am not sure how much time it will take. I have unlimited access as a member of Axway. It could be the same with Kong or with any other organizational tool. I am specifically talking about Axway. There are both pros and cons of using this feature of Axway. I aid my clients with Axway products. I would recommend Axway AMPLIFY API Management to other users because I have worked with this tool for quite some time and it is quite easily operational. It has a very good graphical user interface. It has an upper hand compared to AWS or Azure in that they are very blunt in specific formats of XML, but Axway AMPLIFY API Management gives graphical interfaces for visibility of how the API transactions are going from here to there. From the user visibility part, I would give this upper hand to Axway AMPLIFY API Management. My overall rating for Axway AMPLIFY API Management is eight out of ten.

Our main use case for Axway AMPLIFY API Management is to use the product as an API gateway for securely exposing and accepting calls from the internet, such as securely exposing the web APIs or REST APIs developed within the network, and having authentication layers around it. This is a primary use case, and we also leverage the portal part of the product so that developers can come in, explore our APIs, and if they find that it is of use for them, then they can register and start doing business with us.

The integration features of Axway AMPLIFY API Management are very useful for us, as I am employed as one of the leading internet providers in the UK, where I work as a platform manager. It is very important for us and our external consumers, communication partners such as Vodafone, TalkTalk, and Sky, who wish to use the functionality of the APIs that we are exposing. Integration is very helpful for us by helping expose the APIs as REST APIs.

The most useful features in Axway AMPLIFY API Management, in my opinion, primarily involve the security aspect of the product, which provides us very good methods of securing the network. 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.

The main benefits that Axway AMPLIFY API Management provides for us include securely exposing our APIs for external consumers, which helps us integrate these consumers outside of our network. We need a secure hosting platform for protocol transformation and to abstract the actual endpoint URLs of many products exposing their REST APIs, enhancing both security and meeting business requirements when consumers want to perform certain activities or access analytics data from us.

Regarding the analytics part of Axway AMPLIFY API Management, we do not extensively use analytics as a separate product, but we do use the traffic management analytics portion to see the number of successful and failed API calls. Additionally, we have Splunk integrated into our network to monitor all calls and logs, enabling us to search for success and failure scenarios, but we do not use Amplify's monitoring analytics extensively.

A significant area of improvement for Axway AMPLIFY API Management is the Amplify Central portal, which should help expose APIs on a webpage for potential customers. Although it offers some customization, more features are needed to better serve the purpose. Most Axway customers use their own wrapper sites for API discovery because the basic API portal does not meet all their needs. I would prefer to see more customization options, similar to high-end developer portals from Google or Facebook.

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. We have successfully migrated all our APIs from the Apigee API Management platform onto Axway, a consolidation we completed just last year, and it has been reviewed with Axway as well.

I have been working with Axway AMPLIFY API Management for close to six plus years.

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. In that regard, I would rate it highly, noting that there have been some minor outages related to the database, but we have not faced any major issues in the last four to five years.

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. However, the number of APIs hosted tends to be limited, which makes it difficult to provide a more comprehensive rating.

For technical support from Axway, I would give it a rating of nine out of ten, as ninety to ninety-five percent of our tickets have been answered within the SLAs, and we are very satisfied with the product. We have an engagement partner from Axway, and their technical and product teams are very supportive whenever we need clarifications or urgent confirmations.

Positive

When comparing Axway AMPLIFY API Management to Apigee based on my experience, I find Axway to be better. The rationale for migrating to Axway stems from our use of Apigee Edge, which was entirely a SaaS platform managed by Google. With that, if traffic increased, Google handled the auto-scaling, ensuring high availability. However, Google pushed us towards Apigee X, which required us to maintain load balancing and other networking aspects, leading us to decide to consolidate our API management with Axway, where we had already encountered no issues while managing our infrastructure.

The setup process for Axway AMPLIFY API Management is simple.

My team handled the setup entirely without requiring external integrators or consultants, although we did get the architecture reviewed by Axway. It was mainly to get the green light, while our developers designed the entire architecture and layout in-house.

I would rate the pricing of Axway AMPLIFY API Management at around seven, considering we moved away from a perpetual licensing model to a transaction-based model about three to four years ago, providing 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. While we appreciate this model, I would still prefer the price to be a little lower.

I initially had a perpetual license with Axway, hosting the API gateway on-premises, but due to Axway's shift away from supporting Oracle Linux, we moved to a containerized model for hosting the gateway. Though these containers are not hosted on the cloud, they are hosted on the same virtual machines or infrastructure, allowing flexibility regardless of the operating system of the host machine.

Overall, I would rate Axway AMPLIFY API Management at eight. The cloud hosting is costly for us, which led us to opt for a different model instead, and I feel that competitors such as Kong are emerging rapidly in the market, creating pressure on Axway to enhance their offerings, especially in the realm of API gateway hosting for microservices.

I can describe the use cases for what it can be used for because I was a project manager. We share APIs, modify, and check whether the API already sent it. They receive something, and when we modify the API and send it back and forth.

We deploy this solution by sharing information from my side to the customer side, and there are several parties. We are sharing information and updating the information from each other.

I'm not certain what specific features exist, but it has the capability to monitor because I was a user during that time and I'm not fully experienced yet.

I would improve performance because most of the time we have to send the API several times and then get the notification that the API is received. I'm not certain how accurate it is. The API is not really standardized with each other, so we have to modify it every time.

The application we are using is web-based, and from what I remember, we are clients for them. From our side, it's quite stable. However, 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. The main application doesn't have any obligation, so that's why I'm suggesting improvement to be more stable in terms of the connection, maybe through NGINX or the gateway server.

I would prefer to improve the performance and the stability.

I have been using it for around two years.

The stability may require a more defined meaning of what stable means.

I'm not certain about the scalability because we don't really have a lot of API calls; maybe just around a hundred to two hundred API transactions a day, and we have to modify around fifty percent of them.

I'm not certain about the scalability because it's not really utilized in our organization during that time.

I never used the technical support because I usually go back to the provider.

I never used the tech support because every time we found a problem, we usually go back to the vendors, who contact the tech support.

Currently, we use Wonder from Taiwan, so I have evaluated other API management solutions.

I have never heard of Seaburger Business Integration Suite before.

I cannot recall the setup details because it's a one-time thing, but it's quite long. If it went wrong, we need several days to install that software. There's a project to install and run and make sure that everything is working properly.

We can do it in-house, as we did not use a consultant or an integrator.

Regarding the technical staff, we need around five people on our side, and from the vendors, there are around three or four people on their side. We may have a total of around eight to nine, but I'm not certain if there is somebody else behind their team.

If you are talking on an annual basis, I would say it's not very good. I need around at least three years, but I guess that's something that we can consider in terms of investment; three years can be quite normal but also quite expensive as well.

Regarding the licensing, I don't fully understand it because there's an additional fee about it. The license was covered by the vendor, and we just paid for the API that we used.

I would recommend the solution for other people who want to start using it.

It's not the best one, but it's nice to try to have this to learn about API management rather than having direct APIs one by one, which can create problems.

On a scale from one to ten, I would rate it around seven or six. My overall review rating for Axway AMPLIFY API Management is seven.

My main use case for Axway AMPLIFY API Management was functional and integration testing of APIs deployed through the API Gateway. I test request routing, authentication and authorization, HTTP responses, policy enforcement, invalid payloads, timeout scenarios, and interactions with backend services.

In one project, we used Axway AMPLIFY API Management as a gateway between our internal applications and several external partner APIs. As a QA engineer, I used it to validate authentication, rate limits, and error handling across different environments.

Axway AMPLIFY API Management is part of our broader API testing process rather than as a standalone testing tool. I use it to verify gateway-level behavior such as authentication, routing, policies, rate limiting, and error handling, while using tools like Postman for request execution and validation. It was particularly useful for regression testing because we could verify that changes to API policies or configurations did not affect existing integrations.

The best features Axway AMPLIFY API Management offers are policy-based security and access control, authentication, authorization configuration, API lifecycle management, API Gateway routing and mediation, and monitoring and API usage information.

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.

Axway AMPLIFY API Management has positively impacted my organization by helping us make API integrations more consistent and easier to govern. From a QA perspective, having authentication, routing, access policies, and rate limiting managed at the gateway level gives us a more standardized environment for testing different integration scenarios. It also improves collaboration between QA, development, and integration teams because we can clearly separate gateway-related issues from backend application issues.

Axway AMPLIFY API Management can be improved by making the configuration and troubleshooting experience more intuitive. Some gateway policies and configuration options have a learning curve, and it can take time to understand why a particular request was rejected or routed differently than expected.

I have been using Axway AMPLIFY API Management for around three years.

After implementing Axway AMPLIFY API Management, we saw the biggest improvement in regression testing. 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 because many gateway-level checks became reusable across different APIs.

We purchased Axway AMPLIFY API Management through the AWS Marketplace.

I would recommend evaluating Axway AMPLIFY API Management against your actual API architecture rather than focusing only on individual features. If you have multiple APIs, external integrations, and requirements around security and governance, it is worth looking at.

I rate this product an eight out of ten.

We use the solution for ESB and B2B integration between the systems of our business.

The security aspect of the Axway solution is a valuable feature. Managing APIs through different systems is a strong point, as it is a gateway between several systems. It is reliable and relatively easy to work with. The pricing model is also good.

Axway's queuing messages could be enhanced.

I have been using Axway AMPLIFY API Management as a system integrator for four years. We are using the latest version of the solution.

The product’s stability is very good.

I rate the solution’s stability a ten out of ten.

The solution is very scalable.

I rate the solution’s scalability a nine out of ten.

We communicate with Axway, and they consistently respond fast. They provide alternative suggestions and address any incomplete issues. We are very satisfied with their team.

Positive

We don't have any challenges deploying the solution.

A proper deployment takes probably takes a week.

You must set up an architecture of how the enterprise requires it for availability and consider various other things. It becomes the backbone of an enterprise integration platform. If you look at deployments in real big enterprises, they can take much longer.

The solution has a yearly subscription.

The solution’s pricing is competitive. Axway makes a significant impression compared to its peers, especially with a sensitive budget. In many instances, it is priced below its competitors.

I rate the solution’s pricing a six out of ten.

We are doing the solution’s maintenance with the help of six engineers.

We use Axway in various use cases, including healthcare, financial services, and manufacturing. Its flexibility allows us to adapt to different scenarios. It is highly reliable, forming a backbone for our business. Axway has consistently delivered and has not let us down at all.

Overall, I rate the solution a nine out of ten.

There are APIs, which we call application programming interfaces, in IT. These are the calls, which generally take the data from one place and send it to the other. Their mode of operation is simply transferring the data from one place to the other. APIs are handled by their own gateways and their own management. Axway AMPLIFY API Manager is a tool used to manage API calls. Because they contain sensitive data, security is important and is applied through the use of APIs. The API Manager is an interactive tool that allows applications to communicate with each other. The solution also facilitates data transfer, which can be secured through the use of APIs.

The solution can be deployed both on-prem and the cloud, but 99 percent of the customers for which I have worked, deploy on the cloud. Both AWS and Azure but most of the time the solution is deployed on AWS.

The most valuable feature of the solution is security. I haven't seen a single case of hacking in the past five years. Axway AMPLIFY API Manager is secure.

I can interact the solution with another, for example, ELK, that's another AWS tool, or Kibana, which works quite well. We require some configuration changes, of course, but once it is done, everything is visible and we can interact with the other solutions. Axway AMPLIFY API Manager is quite user-friendly.

Sometimes we find bugs where certain calls are not returning all the data we need. This means the data can become obsolete and non-visible. This needs to be fixed.

I have been using the solution for five years.

The number of calls API Gateway Manager handles ranges from 10 to 100 for some customers. For high-end traffic customers, the number of calls can range from 70,000 to 80,000 in 10 minutes. We can understand the magnitude of the number of calls. The solution is stable and shows no variation. Axway AMPLIFY API Manager has a huge capacity to deflect changes.

The solution is scalable. 

We occasionally need help from the support team of Axway because some of the issues are very technical, and even go above our heads. The technical team is good enough to address the issues. When an issue is really difficult they also help us by raising an immediate ticket to the problem-management team and working with that team to resolve the issue. The technical team is quite helpful. 

Positive

Axway also has competition from other tools, such as AWS Gateway and Google Apigee. However, it is a young tool compared to these others, and it is emerging nicely because it has its own product and is communicative with the cloud, not just Google. It is also interactive with other tools. For example, not just API, but also B2Bi for the Axway organization. Therefore, the solution captures the market well. The sales or product teams of the higher management of this company must have a very competitive price to sell to the end users.

Axway provides good documentation that newcomers can easily follow, but I believe the initial setup would be tough for someone new. Experienced employees know where everything is and how to do their job, so it would be difficult for a new hire to get up to speed.

For an experienced person, I give the initial setup a ten out of ten.

Deployment can be considered a hundred lines of code and some a thousand lines. For a simple deployment, it takes 10-15 seconds. And if the environment connectivity is good enough to respond and there is some heavy code that is being deployed, it takes around 30-60 seconds max, if we are referring to the cloud, where the connectivity for the long duration of the calls is there. The total deployment time is one minute to finish up. From the industrial point of view, Europe has a major chunk of users followed by, the US, and then Australia or the Asia-Pacific region.

I give the solution an eight out of ten. The solution is highly emerging in the market. Plus, it is easy to understand and provides good jobs in this market. Therefore, I would say it is a niche tool that is one of a kind.

In my current organization, there is a limited set of people who can use the solution because it is a licensed product. Not every customer has the requirement to use it. However, in my previous company, every other person was using the solution. Every customer who was engaged with us used Axway AMPLIFY API Manager because it was a product-based organization.

The solution has received positive feedback from the organizations that are using it. However, not every day is perfect; sometimes there are glitches or connectivity issues. But even with these issues, some customers have been using the solution for more than five or six years. In fact, the number of users of the solution has increased by three times since I started working with it. From my experience, customers are loving Axway AMPLIFY API Manager.

This is a product-based solution, so not all the information can be found on Google. Axway AMPLIFY API Manager is not open source. Some features are hidden behind the license pack that Axway sells to customers. I believe that if the organization is compatible enough or has enough money to purchase the solution, then it's a great solution. The documentation is great. And if the organization is capable enough to hire experts for the solution, then they won't have issues working with Axway AMPLIFY API Manager. 

We use Axway Amplify API Management for primarily two use cases. The first one involves an API Gateway exposed on the DNC layer to allow external organizations to connect to internal APIs. The second use case is when applications within the organization need to connect to already hosted APIs, which is done through an internal gateway. These two use cases are supported by APIs built around them.

The best feature of Axway Amplify API Management is its exceptional level of security, which is highly reassuring, coupled with its remarkable capacity to handle substantial volumes of data in impressively efficient turnaround times.

The areas for enhancement should be improving certain filters within the solution. Although they are generally functional, there are occasional problems that could be more precisely adjusted. Additionally, the solution performs well within its workload limitations, but it may not be suitable for scaling up or managing a larger volume of transactions through the gateway. To address this, it may be necessary to adopt a unique architecture rather than relying on traditional pre-packaged options.

If there was a new release of this solution there should be a feature called "Revision History" or "Version Control" that would allow developers to easily navigate and compare different versions of their API flows within the Amplify API Management toolkit. This would save time and effort by eliminating the need to constantly switch between the toolkit and external Git repositories. Additionally, it would provide an added layer of security by allowing developers to quickly revert back to previous versions if a mistake or issue arises.

I have been using Axway AMPLIFY API Management for approximately four years.

The solution is stable. It is evident by its impressive features, such as zero downtime and various other elements that ensure the constant availability of your APIs. However, if the volume of usage was to increase, then certain specific measures would need to be taken in order to maintain the aforementioned stability.

There is an issue with the scalability of the solution. This can be attributed to the internal database, Cassandra, that it employs. In order to accommodate a large volume of requests coming into the gateway, the traditional practice was to install both Cassandra and the gateway on the same on-premise server. However, with an increase in the number of request volumes, scaling up has become problematic. As a result, it has become necessary to install multiple instances of a Cassandra server and gateway separately.

We have approximately 200 to 250 people using the solution who are deployed to different projects.

We have used the technical support team of Axway AMPLIFY API Management. Even though their responses are always very timely, we found ourselves in frequent interaction with them. This can be attributed to the high volumes and complex setup that we have, resulting in a minimum of two to three tickets being raised each month.

The majority of the time we used the support we had answers, but in some cases, we were able to figure out the solution without help after we created the tickets.

 I rate Axway AMPLIFY API Management an eight out of ten.

Positive

I have used various other API Management solutions, such as Apigee. Apigee is now on the cloud.

The initial setup of Axway AMPLIFY API Management is easy.

The amount of time it took to set up and launch everything, including spinning up instances and completing environment setup for development or quality involvement, the entire process took approximately one week to finish. Additionally, it's worth noting that the spinning up of a new API gateway instance was a relatively quick process. It's possible that the deployment could be accomplished faster if you're solely focused on this aspect of the process. Furthermore, as part of the deployment process, both penetration and load tests were conducted to ensure everything was functioning properly.

The solution is expensive. When you acquire a license you have full access to the solution, unlike other competitors such as Apigee X, where there are fragmented licenses. Some licenses only allow access to certain features while others allow access to more features. Upon procuring this solution's license, you will have full access to the solution, allowing you to experiment with all of its features.

This is a good solution. However, for on-premise networks, this solution works well. I would recommend it to others.

It is a highly stable platform with great filter and feature options. While there is still room for improvement in areas, such as toggling, traffic management, and gateway portal availability, overall it is a very impressive tool.

I rate Axway AMPLIFY API Management a nine out of ten.

We use Axway for exposed APIs and REST APIs, basically. We also use it internally and expose it for external consumption, essentially.

Axway AMPLIFY API Management has improved our organization. For example, nowadays, we expose the APIs of Fintechs. We have several partners, brokers, and financial institutes. Generally, our APIs are utilized for synchronization and internal communication integration between applications.

The usage of Axway in the future depends on the projects and their requirements.  Our growth is generally determined by the specific needs of each project. For instance, we may have two or three instances for every three logs. However, in the production environment, we currently have around three to five instances of actual running in the production environment. So, the future of Axway depends on the needs and priorities of our projects.

Axway has several important features. Governance is an excellent feature. Policies are valuable as well. Performance is also important for us. In general, API governance provides a better experience for providers.

Areas of improvement include marketing and enhancing the data products area by using ETIs. Also, we need to improve communication and data exchange using ETS and EPS. 

Additionally, nowadays they're using another product in the cloud. However, they also have their own product. 

I have been using Axway AMPLIFY API Management for about seven years. I am using the latest version.

Axway is a very stable solution.

Generally, when using Axway in on-premises infrastructure or any EAF mode, the scalability is manual. It's not automatic. 

But, when using it in the cloud, the scalability is low for us because you need to set up all the infrastructure for scalability, and it depends on the cost provider. When using virtual machines (VMs), scale-out is relatively lower for us.

In my last experience, the enterprise support assigned by my company was better. We have a dedicated team for this product.

We deployed Axway on virtual machines in the cloud, but it's generally used on-premises. In general, the setup is very common and useful for us at scale.

Nowadays, we operate on-premises, but we also have some services in the cloud, although not in the past mode.

We have a dedicated team for that.

I see it as an investment sometimes and as a return on investment other times. It depends on the situation.

Generally, my colleagues mention that it's expensive, but it depends on the case. In some cases, it's fair to pay for the product considering the benefits.

If you want to use Axway, it's recommended to expose your APIs, whether they are for internal or external consumers.

I would rate it as a nine.

We use this solution for our e-commerce clients. 

The UI and UX are quite good and easy to understand. I think if a company has a specific IT admin employee dedicated to this solution, it will be very simple and easy to use.

In terms of customer service, the company needs to be easier to contact, and the support team needs to understand the situation and the product itself better. Sometimes, in our recent experience, we noticed that our engineers were much more advanced than the tech support. Our team found some challenges, problems, and issues. We sat down together and found the solution ourselves.

I have been working with this solution for about six months. 

So far, the stability is good, but it hasn't been tested for a heavier environment yet, and it should be. 

This platform can be highly scalable. At the moment, there are 24 people using this solution within my organization. There are about ten engineers, two project managers, and five people from the IT department. The rest are other software engineers. Three people, the developers themselves, are involved with maintenance for the solution. 

I would rate the technical support as a three out of five.

The solution was already installed when I joined the company, so I'm not sure, but according to some team members, it took a few hours to set up. 

Our business partner handled the installation from the vendors side, and then we continued with our own team. 

I'm not sure about this product yet, so it is 50/50 whether I would recommend it to someone or not. 

I would rate this solution as a seven out of ten. Other similar products have similar features, so this solution doesn't have anything that is more advanced.