Provision MFT in Thru or private cloud as budget and governance requires
Run Thru on any cloud
Thru offers multiple provisioning options: configuration in Thru data centers or in a private Azure or Amazon Web Services (AWS) cloud instance. Hybrid architecture extends MFT functionality to internal file transfers. These are orchestrated by our cloud and executed by runtimes installed on corporate networks. All files in internal flows are transferred inside the enterprise’s firewalls.
Thru runs in certified Azure data centers around the globe in the United States, United Kingdom, Germany and Australia. Your MFT application is ready for use and fully managed with 99.99% uptime. All data centers adhere to the highest standards to ensure all data is secure. Thru’s instances scale elastically and are highly available with disaster recovery measures in place.
Benefits of running in our cloud include
- Zero deployment or maintenance
- Automatic upgrade to new features
- Unlimited elasticity based on file transfer load
- Multiple geographic location options, based on data sovereignty requirements and network proximity
- Defense in depth with multiple levels of security
- High availability and disaster recovery
- Global routing acceleration service option
Virtual Private Cloud
Thru can run in your virtual private cloud on Azure or AWS if required by corporate governance or security. Flexible private cloud deployment options are available, where the environment can be managed by us or by you. Thru’s application deployment options include automated continuous delivery (CD) pipelines.
Our cloud supports internal file transfer use cases with the Thru Node, which is installed on-premises to transfer files between internal enterprise systems. Our node is orchestrated by our cloud. The cloud administration portal can re-configure, pause/resume, restart or update the node. Configurations will be retrieved by the node via outbound polling using an HTTPS connection. The node runs in a distributed configuration with auto-scaling, where multiple microservices are spawned on demand and/or executed concurrently to meet data transfer requirements. This distributed architecture automatically creates highly available configuration: If a microservice failure is detected, a new instance of the microservice is started.