With so many file transfer solutions on the market, it can be a bit confusing to understand which features are included in which types of servers (and protocols). For example, an MFT server like JSCAPE by Redwood can also operate as an SFTP server, but the Enterprise Edition of Cerberus FTP Server by Redwood also contains an SFTP server with file transfer automation capabilities.
In today’s post, we’ll address the differences between an SFTP and MFT server to help clarify things for you.
What is an SFTP server?
An SFTP server uses the SSH2 File Transfer Protocol to transfer data with full end-to-end encryption. SFTP servers validate client access with a public/private key pair, and can use a number of different encryption methods to protect data in transit.
SFTP servers are more commonly set up to serve data on an ad hoc basis. They can include some automation, but capabilities will vary by provider. As an example, Cerberus FTP Server offers a number of automation tools and a SOAP API to enable an administrator to program their own automations.
For more on SFTP servers, check out our blog posts on SFTP servers.
What is an MFT server?
An MFT server provides an enhanced file transfer experience, typically through advanced automation tools, support for Electronic Data Interchange (EDI), data transformation and improved security monitoring (such as JSCAPE’s MFT Gateway).
MFT servers are designed to streamline and automate as much data handling as possible, making them the ideal tools for heavier workflow support in data-intensive environments.
Is Managed File Transfer (MFT) a file transfer protocol?
No. MFT servers use existing file transfer protocols (SFTP, FTPS, HTTPS, etc.) to perform their functions.
Some MFT servers do, however, use their own file transfer protocols. JSCAPE, for example, has developed the Accelerated File Transfer Protocol in order to provide higher data transfer speeds than other protocols.
Do MFT servers run on SFTP?
They certainly can. The file transfer protocol an MFT server uses can be specified by the administrator, and nearly all MFT servers support SFTP transfer. However, MFT servers are also capable of supporting a number of other file transfer protocols simultaneously and do not have to support SFTP transfer.
Are the use cases for MFT servers and SFTP servers different?
Although both types of file transfer servers do have some overlapping use cases, enough difference exists between them that we thought it would be helpful to review the different use case examples below:
- Client-driven transfer requests: If your organization primarily serves data on client requests, you’ll likely be just fine with an SFTP server. There’s no need for automation services in this use case, and you can also create a high degree of security with a combination of public/private keys and two-factor authentication.
- “One-to-many” data transfers: If your goal is to use your file server as the source point of frequent one-to-many transfers, such as sharing new documents throughout your organization or providing files to a partner network, an SFTP server would be able to handle this action as well but you may want to consider an MFT due to its flexibility in supporting different protocols and security levels depending on your transfer partners.
- Event-driven transfers: For any data transfers triggered by a system event, such as the receipt of a new order, an MFT server is likely the better choice due to its ability to support a broader range of automation scenarios and generally deeper customization options.
- EDI transfers: Electronic Data Interchange actions are better supported by MFT servers, as these transfers require communication in protocols such as OFTP or AS2 that SFTP servers don’t natively support. If your organization processes orders, manages inventory or tracks shipping and your data partners require EDI, an MFT server is the right tool.
- Data transformation: It’s not unusual for files and data to be received in a format that must be transformed to make them more useful. For example, files may be transmitted in ASCII format due to size constraints, but then must be turned back into a human-readable spreadsheet. MFT servers generally support varying levels of data transformation that SFTP servers do not.
- Transfer speed: While both SFTP and MFT servers generally handle high volumes at high speeds, the heavier encryption load in an SFTP transfer, combined with the fact that it is delivered over TCP, means that MFT servers may provide a faster speed at higher volumes. Many MFT servers support UDP file transfer protocols, which generally operate at faster speeds and are ideal for networks that experience significant latency (JSCAPE’s Accelerated File Transfer protocol uses UDP).
We hope that the above information has been helpful for you in better understanding the difference between SFTP and MFT servers. If you’d like to try a strong blend of both, why not download your Cerberus FTP Server trial.