SFTP
The secure protocol most partners reach for. Tested against OpenSSH, WinSCP, Cyberduck, Paramiko, .NET, and the long tail of clients partners actually bring. SCP is supported too, for clients that need it.
Retire The Old FTP Box
The single most common reason teams come to Files.com is this one: they have an aging in-house SFTP server — or a fragile EC2 instance, or a legacy file-transfer appliance — carrying real partner traffic, and they want it gone. No more patching cycle when a vulnerability hits. No more firewall negotiation every time a new partner needs whitelisting. No more box in a DMZ that one person knows how to keep alive.
Files.com operates one of the largest cloud SFTP services in the world, on a high-availability pool of servers across multiple regions. Your partners keep connecting exactly the way they always have — same protocol, same credentials, same client — and you stop running the infrastructure underneath it. Every session is captured in an immutable audit log you can search or stream to your security tools.
Every Protocol Your Partners Already Use
Whatever a partner brings to the table, Files.com speaks it — so onboarding a new connection never starts with "can you switch protocols?"
FTPS
FTP wrapped in TLS encryption, in every common mode. The right answer when a partner’s system only speaks FTP but your security rules require the traffic be encrypted on the way across.
FTP
Plain FTP for the legacy partner who has nothing else. It is supported but turned off by default, so you opt in deliberately rather than leaving an unencrypted door open.
WebDAV
The protocol that lets a folder mount as a network drive in Windows, macOS, or Linux. Partners and apps that speak WebDAV connect to the same files, no extra client to install.
Why Run It On Files.com Instead Of Your Own Server
Nothing To Patch When A CVE Hits
Our SFTP and FTP stack is bespoke code we wrote and own — not a fork of OpenSSH. When the next OpenSSH vulnerability lands and everyone else scrambles to patch, the patching here is ours to handle, not yours.
It Just Works With Whatever A Partner Brings
After 15+ years in production, the server has seen the quirky clients, old libraries, and off-spec setups partners show up with — and handles them. You stop debugging someone else’s FTP client.
Front Storage You Already Own
The endpoint can sit directly in front of your Amazon S3 bucket, Azure Blob, or Google Cloud Storage. Partners connect over SFTP; the bytes land in your storage. No data migration required.
Reach On-Prem With No Firewall Change
Drop the Files.com Agent on a server in your datacenter and SFTP traffic terminates against that storage over an outbound-only connection. No inbound listener exposed to the internet, no DMZ, no VPN.
You Need More Than A Port — You Need A Platform
Plenty of companies sell “an SFTP product.” But SFTP is just a tunnel from one point to another. What matters is what sits on each end of that tunnel — and that is where Files.com gives you a platform instead of a bare pipe.
If a person is on the other end, Files.com gives them governed share links and inboxes, a real web interface, and desktop and mobile apps — not a bare login prompt. If a system is on the other end, a file arriving over SFTP can kick off an automated workflow that routes, transforms, and tracks what comes through. You came in searching for SFTP; the platform is what you actually needed.
SFTP & FTP Questions
What technical buyers ask before they move partner traffic off their own SFTP server and onto Files.com.
Give Every Partner A Place To Connect
Start a free trial, stand up SFTP, FTP, FTPS, and WebDAV endpoints in minutes, and point them at storage you already own. Retire the box in the corner and let Files.com run the server.
No credit card required • Free for 7 days • Live in minutes