What is our primary use case?
We deploy Axway Amplify to a server hosted on AWS, but it isn't a cloud SaaS solution. We use it for large-scale file transfers. Our client had multiple vendors with whom they exchanged payroll and shipment-related files. We use Amplify externally to exchange files with vendors and internally on our 500 servers, which talk to each other using the files. All the file transfers transfer for that client went through this application, including the encryption, file check, etc.
How has it helped my organization?
Before implementing Axway, we were doing script-based point-to-point file transfers using a shell script. That means if a file has to go from server A to server B, we have to open a network port within those two servers. It got kind of messy as the number of servers and the file transfer requirements grew.
Axway consolidated all of our communications into one platform, simplifying network and port management. Now, all we have to do is open one port to this application, and we can remove all the firewall rules on that port. It's much more straightforward to manage from a security perspective. We used to rely on an archaic FTP solution, but Axway features SFTP, so it was an improvement security-wise.
What is most valuable?
Deploying certificates and encryption-decryption are effortless with Axway. It features a single pane of glass view, where you can view all the file transfers going on inside your organization.
What needs improvement?
One area of improvement is troubleshooting. When a transfer fails, they provide little information about the login, which makes troubleshooting difficult. Also, file transfer scheduling is primitive. By that, I mean you can't define a complex schedule, like scheduling a job to run at particular hours multiple times in a day.
Also, Axway Amplify doesn't have built-in analytics, so you need to use another product for that. It would be helpful if they could do some basic analytics, like statistics for a 24-hour period. I'd like to see something simple that shows how many file transfers came in and went out from the environment, and how many failed.
I would also like to see Axway implement online patch management. We have to take the application completely offline to apply the patch and then restart. Other applications support online patch management, so I would appreciate it if they could do something similar. Of course, a restart would still be required, but online patch management could significantly reduce our downtime.
For how long have I used the solution?
I have three years of experience with Axway Amplify, but I switched roles about two months ago, so I no longer use it.
What do I think about the stability of the solution?
Axway is stable up to a certain point, but when the number of file transfers multiplies, the application sometimes crashes. You have to do thorough capacity planning if you are adding more and more file transfers to the platform.
Let's say we have 500,000 transfers, and everything is smooth. We'll start to see problems if the number of transfers surges to one million in a day. We had to do lots of capacity building to avoid this, like server provisioning and increasing the CPUs and memory. Your infrastructure needs to keep up with your file transfer growth.
What do I think about the scalability of the solution?
We had a two-node cluster, and you can do a three-node cluster easily, but I don't think they support more than three nodes. There are some limitations, but we could handle a million transfers a day just fine with two nodes. We have around 50 users logged into Axway daily checking the transfers and related stuff.
How are customer service and support?
Axway technical support is great. I would probably give them an eight or nine out of 10. My only problem is that they don't provide enough support on the weekend. Everything else is good apart from that.
How would you rate customer service and support?
How was the initial setup?
Setting up Axway Amplify is straightforward. First, we set up a two-node cluster, and it took us around a couple of days to deploy the application after that. Including the server build and all the network configuration, it took about three weeks total. Then it took another week to get it into production.
What about the implementation team?
Axway provided support during our deployment. One support engineer was assigned to our account for around four weeks during our production deployment.
What was our ROI?
In the past, we needed multiple IT personnel to set up the file transfers. Now we have a three-person team handling all file transfer requests for the entire organization. That's a massive return on investment. We used to have 20 to 30 people doing that stuff, but that has been reduced to only three or four.
What's my experience with pricing, setup cost, and licensing?
I don't know the exact cost of the Amplify license, but the support agreement costs around $30,000 annual.
What other advice do I have?
I rate Axway Amplify nine out of 10 because it's easy to deploy, use, and create jobs. Job creation is straightforward. It doesn't take long to set up a job, and you can quickly get on with it. You can get started with production within a week after deploying.
If you're implementing Amplify, I recommend thorough capacity planning before deploying. If you don't have that many transfers, you are probably fine, but you need to be mindful of growth in transfers. As our systems become increasingly complex, we see more and more transfers happening. If you're starting multiple new projects, the number of transfers will increase by 20 to 30 percent. You have to pay attention to resource utilization and do capacity planning.
Which deployment model are you using for this solution?
Public Cloud