Cloud Economics – MFT as a Service Explained


“As a service” is not a new concept for companies like Salesforce, Slack and other enterprise business application developers. However, for many organizations who are looking for managed file transfer (MFT) in the cloud, the “service” part is still not fully understood. Enterprise MFT as a service is what we do at Thru. Since we continue to field questions such as when do you do releases, can we have disaster recovery(DR) and what is the capacity, we would like to explain the basic concept of as a service in the context of MFT:

  • Software Updates – We serve the same software version and everyone has it. It’s always compatible with earlier versions. There is no downtime to the service and as a customer you don’t need to plan. It’s a service so we do all the work. On-premises agent upgrades are automatic.
  • Fault Tolerance / High Availablilty(HA) / DR – These come as standard. Non-HA is not an option. We are a service and our infrastructure is designed like other cloud services to ensure we have redundancy in place. Thru guarantees high availability with no single point of failure.
  • Load Balancing / Scalability – Thru is a cloud service: We auto-scale on demand. This is the beauty of our cloud-native elastic architecture.
  • Service Pricing – Thru service is “usage-based.” This means you pay for what you use or pay-as-you-go (PAYG) and also benefit from scale: The more you use, the less per unit you pay.

Cloud Versus On-Premises MFT Operational Costs

For decades, MFT solutions have been installed on-premises as part of a broader B2B integration architecture of systems such as ESBs and B2B gateways. Many companies are now migrating to cloud-native enterprise integration platforms as a service (EiPaaS) and want to know how MFT can align with a cloud-native integration framework.

IT leaders tell us one of the biggest problems they find with on-premises MFT is its significant capital and operational costs, such as

  • Software deployment and patches
  • Infrastructure deployment and patches
  • Backups and high availability
  • Data security
  • Server maintenance and energy footprint
  • System administrators and support staff

These costs consume a large portion of the IT budget even in the system’s lowest use periods making it inefficient to scale. With Thru’s cloud MFT service, companies only pay for what they use. It doesn’t require any on-premises deployment and delivers continuous updates—reducing maintenance and letting IT focus more on business and innovation.

To demonstrate the value of Thru’s usage-based pricing for MFT, let’s review the case study of one of our oil and gas customers.

Oil and Gas Enterprise Adopts Cloud-First Model for MFT

This oil and gas company generates and digests massive amounts of data to report processes such as seismic activity, drilling activity and production rates. To flow large data files between enterprise and partner systems, the company was using various on-premises FTP servers.

These legacy servers became time-consuming and costly to maintain so the search began for a cloud solution with the goal of eliminating on-premises equipment.

The company selected Thru’s cloud-native MFT service due to its consolidation of file exchange protocols, easy user experience and usage-based pricing model. Another driver was Thru’s out-of-the-box connector for the MuleSoft Anypoint Platform™, a cloud-native integration platform already adopted by the company. This solution simplified file transfer integrations with the company’s numerous systems such as SAP and Salesforce.

After replacing its on-premises solution with Thru, the company saw 10-times reduction in operating expenses and accelerated the delivery of business-critical data by 2.5 times.

To learn more about how this oil and gas enterprise benefits from cloud economics, click below to read the full case study.


Scroll to Top