FileMage Reviews

My primary use case for FileMage is deploying a secure cloud-native SFTP and FTP gateway backed directly by AWS S3 to handle automated B2B file transfers and vendor data ingestion.

In my day-to-day operations, my external partners upload large financial data sets daily using FileMage for those automated B2B file transfers and vendor interactions. Before FileMage, I managed traditional Linux SFTP servers which required provisional local disk space and involved writing brittle cron scripts to sync files to the cloud. With FileMage, vendors upload files to an isolated SFTP folder and the data streams directly into my secure AWS S3 buckets in real-time, triggering my downstream process pipeline instantly.

I use FileMage to centralize credential management for external clients, allowing me to strictly isolate folder access using IAM roles without managing complex Linux permissions, which covers the main way I'm using FileMage.

In my experience, the best features FileMage offers are direct cloud storage backing, IAM and permission mapping, Let's Encrypt integration, robust audit logs, and a web-based admin UI.

Out of those features, I find myself relying on the web-based UI admin the most because it is a simple, clean dashboard for managing user keys and virtual folders. The direct S3 storage backend has made the biggest impact, completely eliminating disk space monitoring loads and automating the data transfer pipeline with custom synchronization scripts.

FileMage has positively impacted my organization by drastically modernizing our file transfer infrastructure, eliminating storage maintenance overhead, closing security gaps associated with legacy FTP setups, and significantly reducing vendor onboarding time.

I would like to see an enhanced web-based file manager for non-technical end-users, allowing them to easily preview or move files via GUI. I would also appreciate more native webhook destinations for event-driven automation and deeper out-of-the-box integration with identity providers like Okta for admin single sign-on.

The platform is very stable and lightweight in my experience, and most improvements would be minor quality-of-life updates for administration and advanced user management in larger corporate setups.

I give it a nine out of ten because I do not think it deserves a ten as it lags in some spaces, especially where large organizations are concerned. FileMage is self-hosted, not serverless, and manual high availability setup is difficult. The basic end-user web interface is a limitation. There is a lack of native complex workflow automation, so I think nine is appropriate.

My experience with integrating FileMage into my existing workflows and systems has been an overall turnaround for my organization. Earlier, I was having manual SFTP transfers, and now with FileMage, the transition has been significant. The setup was smooth, and FileMage has a web-based GUI that helps transfer files easily, which was needed by everyone for a long time. The overall process was smooth and well-received.

FileMage is highly stable and resilient in my production environment with zero unscheduled downtime.

FileMage's scalability is very good because the heavy lifting of storage scalability is offloaded to AWS S3, allowing it to handle large volume uploads and spikes in concurrent transfers without any issues.

My experience with the FileMage support team has been great. They are highly technical, responsive, and quickly helped clarify some initial questions I had around IAM role policy configuration during the setup.

I previously evaluated AWS Transfer for SFTP, but while it is a good managed service, the baseline hourly protocol cost and data transfer fee were far too high for my budget. FileMage gave me the same S3-backed functionality at a fraction of the cost, which is why I switched.

The setup process was incredibly fast, as I was up and running in less than an hour. The pricing model is highly cost-effective and predictable compared to managed SFTP alternatives. The hours spent on patching legacy Linux SFTP setups meant FileMage paid for itself within the first couple of months. Productivity has increased significantly for my team as FileMage is a much faster tool compared to traditional setups.

Although I do not have specific numbers, the ROI was clear immediately by bypassing expensive cloud-native file transfer protocols and saving engineering hours spent on patching legacy Linux FTP setups. FileMage paid for itself within the first couple of months.

My experience with pricing, setup cost, and licensing has shown that the setup process was incredibly fast. I was up and running in less than an hour. The pricing model is highly cost-effective and predictable compared to other cloud and managed SFTP alternatives, making it easy to justify to finance. The ROI was clear immediately.

I evaluated AWS S3 and AWS Transfer for SFTP before choosing FileMage.

The accuracy and reliability of output from FileMage's AI capabilities are incredibly reliable. File actions are transactional, and I have not experienced any corrupted file transfers or sync lag between the gateway and AWS.

FileMage has impacted my team's productivity and efficiency significantly. Out of those features, I find myself relying on the web-based UI admin the most because it is a simple, easy-to-manage dashboard for managing user keys and virtual folders. The biggest difference is the web-based UI and Let's Encrypt integration, robust audit logs, and a web-based admin UI.

The learning curve for new users or admins when adopting FileMage is comparatively quite easier as I have a GUI. New users in the traditional setup required too much to learn. If someone is already comfortable with cloud infrastructures, the easy part is distributed as per built-in machine through the cloud marketplace. Launching the instance, running the initial setup command, and mapping into a storage bucket takes less than an hour. The web admin panel handles things that usually required complex Linux configuration. The slight learning curve comes down to mapping cloud object patching, where someone has to translate traditional directory permission into cloud storage prefix and pair them correctly with IAM policies. If someone decides to go HA, they have to architect an external database configuration and a load balancer. The learning curve is very low for an experienced user, while for a new user, it is slightly higher, but for users who have knowledge, the learning curve is almost non-existent.

I find FileMage quite flexible when it comes to customizing workflows or integrations with other tools, as it becomes part of the cloud ecosystem. I deployed it on EC2, so it is very straightforward to connect it with the S3 bucket, making the integration smooth and becoming part of the ecosystem. From a technical and DevOps standpoint, FileMage is highly flexible, but it uses a building block approach. It does not feature a massive marketplace of native SaaS plugins; instead, it provides robust cloud standards, webhooks, a RESTful API, and native cloud provider support to fit into any pipeline.

When handling high volumes of file transfers or large data sets, FileMage performs exceptionally compared to traditional FTP servers, and I have not noticed any bottlenecks. Earlier, when I was using the traditional setup, I was facing numerous bottlenecks, but after switching, FileMage's performance profile is highly predictable because of its core architectural choice: in-memory file stream. Rather than caching incoming data onto a local hard drive, FileMage streams data blocks straight through the system's memory directly into cloud object storage like AWS S3 or Azure Blob.

I feel confident in my ability to handle disaster recovery and backup with FileMage, as I have backed up my EC2 EBS volume apart from relying specifically on FileMage. Since FileMage streams files directly to cloud object storage in real-time, data resilience depends entirely on my cloud provider. I have enabled cross-region replication on the target AWS S3 buckets, so if my primary region goes entirely offline, my file data is already safe and accessible in my secondary region. The FileMage instance layer contains user account, password, SSH, and virtual folders, so that needs to be safe. If using a single instance deployment, the action should be to use EBS snapshot, which I do. Therefore, I feel confident in disaster recovery while using FileMage.

Managing user access and permissions with FileMage is easy and without challenges, as I use IAM roles and permissioning is provided to the user from IAM itself. I do not find any challenges here in user access and permission since I have integration with AWS. Managing user access and permission in FileMage is highly intuitive and a massive quality-of-life upgrade over traditional Linux server admin. Instead of configuring complex Linux permission, ACL, and system groups via command line, everything is handled through a clean web administration portal or a REST API.

Others looking into using FileMage should consider it as it is highly affordable, highly reliable, scalable, and very good compared to other competitors and partners. I shifted directly and had used many options in comparison with FileMage, but I feel this is very reliable, and I have been using it for more than a year. I suggest other colleagues and users to shift to FileMage, share their experience, and look out for other better solutions and then compare them with FileMage. I have done this, and I find it a better tool than the competitors in the market which are available. I give FileMage a rating of nine out of ten.

FileMage serves as our primary solution for deploying a secure, cloud-native SFTP, FTP, and API gateway backed directly by AWS S3 to handle automated B2B file transfers and vendor data ingestion.

One example of how we use FileMage for automated B2B file transfers and vendor data ingestion is our automated vendor onboarding and reporting pipeline, where our external partners need to upload large financial data sets daily via SFTP. Before FileMage, we managed traditional Linux FTP servers which required provisioning local disk space and writing brittle cron scripts to sync files to the cloud. With FileMage, vendors upload files to an isolated SFTP folder, and the data streams directly into our secure AWS S3 buckets in real time, triggering our downstream process pipelines instantly.

We use FileMage to centralize credential management for external clients, allowing us to strictly isolate folder access using IAM roles without managing complex Linux permissions.

FileMage has positively impacted our organization by drastically modernizing our file transfer infrastructure, providing security gains associated with legacy SFTP setups, and significantly reducing vendor onboarding time.

We have achieved almost a 100% reduction in local storage cost and maintenance for file transfer, reducing manual user provisioning and configuration tasks from hours to just a few minutes for vendors.

The best features of FileMage that I value are direct cloud storage backing, IAM and permission mapping, Let's Encrypt integration, robust audit logging, and a web-based admin view.

Among those features, I find myself relying on the web-based UI the most because it provides a simple, clean dashboard for managing users, keys, and virtual folders, with automated SSL/TLS certificate management for SFTP saving considerable time. Files stream straight to AWS S3 without consuming local space, which is also a valuable feature to have.

The direct S3 storage backend of FileMage has made the biggest impact because it eliminates disk monitoring alerts and automates the data transfer pipeline without custom synchronization scripts.

To improve FileMage, I would appreciate seeing an enhanced web-based file manager for non-technical users and more native webhook destinations for event-driven automation.

Overall, the platform is very stable and lightweight, and most improvements would be minor quality-of-life updates for administrator tasks and advanced user management in larger corporate setups.

Native automated multi-region HA clustering configuration could be more seamless to set up out of the box.

I have been working in the DevOps and cloud infrastructure space for around five years.

FileMage is very stable and has demonstrated high stability and resilience in our production environment with zero unscheduled downtime.

FileMage's scalability is very good because all the heavy lifting of storage scalability is offloaded to AWS S3, and FileMage handles large volume uploads and spikes in concurrent transfers without any issues.

FileMage is easy to scale and represents a highly scalable platform.

The level of documentation and community support available for FileMage is very good. The support team has been great, highly technical, and responsive, quickly helping us clarify initial questions around IAM role policy configuration during setup.

We previously evaluated AWS Transfer for SFTP, and while it is a good managed service, the baseline hourly protocol cost and data transfer fees were far too high for our budget. We switched to FileMage, which gave us the same S3-backed functionality at a fraction of the cost.

Before choosing FileMage, we evaluated traditional options for SFTP where we provisioned a server, but they were not reliable and not useful for us, so we moved to FileMage.

The initial setup and configuration of FileMage for our team was easy as it was self-hosted rather than serverless.

For those comfortable with cloud infrastructure frameworks such as AWS, Azure, GCP, IAM roles, and networking, setting up FileMage is highly intuitive. FileMage is distributed as a pre-built machine through cloud marketplaces, so launching the instance, running the initial setup command, and mapping to a storage bucket takes less than an hour. The web admin panel handles configurations that usually require complex Linux setup.

We have seen a return on investment, which was clear immediately by bypassing expensive native cloud file transfer protocols and saving engineering hours spent on patching legacy Linux SFTP setups. FileMage paid for itself within the first couple of months.

Our experience with pricing, setup cost, and licensing has been excellent. The setup process was incredibly fast, with us up and running in less than an hour. The pricing model is highly cost-effective and predictable compared to other cloud-managed SFTP alternatives, making it easy to justify to our finance team.

I would advise others looking into using FileMage to clearly define your IAM roles and S3 bucket policy before deployment. If you configure your cloud permissions cleanly from the start, FileMage integrates perfectly and runs almost entirely on autopilot. I would rate this review a 9 out of 10.

Public Cloud

Amazon Web Services (AWS)

Our main use case for FileMage is to completely modernize our ingestion tier. I was a mainframe developer at a bank where our core banking system received massive daily financial data sets and transaction batches from external vendors and clearing houses. We managed this using traditional mainframe FTP or Connect:Direct earlier, which are the jobs running on z/OS, and we deployed FileMage as a secure cloud front-end gateway. External clients still connect via the standard SFTP but instead of the files hitting our mainframe storage pools directly, FileMage streams the incoming data blocks straight into our AWS bucket.

A specific example of a workflow where FileMage made a difference is the transferring of files from external vendors, which they used to transfer through FileMage, acting as the gateway between them and the mainframe system.

The best feature that FileMage offers, which we used, is the architectural feature of in-memory file streaming. We were mainly focused on storage optimization and security, while traditional Linux file transfer onto a hard drive requires constantly monitoring disk arrays to prevent bad space abends. We faced several mainframe abends related to space, so using FileMage handled that effectively and transferred to AWS S3 without landing a single byte on our mainframe local disk. Therefore, storage space abends became very infrequent after using FileMage, which led to a significant reduction in CPU cost from the mainframe side.

The in-memory file streaming and storage optimization impacted my daily operations positively as CPU consumption became less. Before using FileMage, we were getting bad space abends, such as the S37 abend code in mainframe that were reduced significantly. Memory issues were also reduced significantly because we were not directly getting files from the external vendors to the mainframe; we used FileMage as the gateway, which pushed the files to AWS S3, and from there, the mainframe could pull whatever files were needed without having any abend issues.

FileMage has positively impacted my organization by reducing the costs we faced because of high CPU consumption due to numerous job abends. The number of incidents we used to get because of the abends were significantly reduced, and file transfer became easy.

FileMage can be improved in a couple of areas where it lags for heavy banking setups. Because we process files originating from legacy core banking systems, we deal extensively with EBCDIC encoded files, and FileMage doesn't offer native configurable code pages or character translation tables on the gateway to convert EBCDIC to ASCII or UTF-8. We had to build an automated AWS Lambda pipeline to convert the files once they landed in S3. The native file manager for end users is a bit basic and could use more advanced workflow automation tools.

I used FileMage when I was in the banking domain for two years.

FileMage's scalability is good because the application delegating the storage scales on the cloud back-end. Since it offloads all storage weight to AWS S3, FileMage comfortably processes massive concurrent file spikes and high volume data during business hours.

Customer support was good for FileMage, and technical support was excellent. They were responsive and experts, supporting throughout the transition period of our project. I would rate customer support as nine on a scale of one to ten.

Previously, all external transfers hit our mainframe directly via FTP or legacy MFT tools, and we evaluated AWS Transfer for SFTP as a cloud alternative, but the hourly protocol cost and variable data fees were prohibitive. FileMage offered the exact same secure S3 backing functionality at basically lower cost, which is why we chose FileMage over AWS Transfer.

I don't exactly remember specific numbers, but twenty percent of CPU reduction happened because we used to receive a lot of files, and it reduced a significant number of CPU. It was a long time ago, so I don't remember exactly.

I have not recently used FileMage's AI capabilities, governance, and security features, so I have no information about these areas. I used this a few years back and don't have any information on the AI capabilities.

My advice for other banking teams looking into using FileMage is to clearly architect your AWS IAM roles and S3 bucket access policies before deploying. If your cloud security permissions are clean from day one, FileMage integrates seamlessly and runs almost entirely on autopilot. FileMage is an amazing way to bridge old legacy vendor requirements with modern cloud bank architectures without risking mainframe security, making it a good gateway. I would rate this product nine on a scale of one to ten.

On-premises

Amazon Web Services (AWS)