The canonical AWS Security Blog post is titled “How Transfer Family can help you build a secure, compliant managed file transfer solution.” The word build is the honest read. AWS sells a building block. The full MFT product is the customer’s responsibility.
Every published AWS reference architecture chains Transfer Family with eight to fourteen more services — Lambda, Step Functions, EventBridge, SQS, DynamoDB, Secrets Manager, CloudWatch, CloudTrail, SNS — plus the UI, API, and auth stack you write yourself. AWS’s own Architecture Blog states the gap plainly: “Before this feature was released, the MFT architecture based on Transfer Family involved responding to Amazon S3 events within AWS Lambda functions. There was no overarching orchestration layer.”
Files.com is the buy side of that build-or-buy decision, with the buy side already done. SFTP, FTPS, FTP, WebDAV, AS2, Automations, Inboxes, Share Links, the Agent, PGP encryption, a complete audit log, and the REST API and SDKs in 8 languages — one product, one price. Your S3 bucket stays where it is; we mount it. Your Amazon SNS topic stays where it is; we publish to it.
Transfer Family bills $0.30/hour per protocol endpoint and $0.04/GB on top. The endpoint charge runs the same whether or not any bytes move, and the data-processing line climbs into five figures a month at multi-TB daily volume.
Because the endpoint charge accrues around the clock, teams resort to spinning endpoints up only on demand — which means giving up the managed-service availability the product was bought for.
Transfer Family added a Web App, but it runs on a different identity stack than the SFTP users. A partner who connects over SFTP cannot sign into the Web App with the same credentials.
Transfer Family has no first-class partner concept and no built-in transformation engine. Both end up as Lambda and Step Functions you own, test, and maintain forever.
Transfer Family is what it is — a protocol head with a growing set of adjacent primitives. The question isn’t whether it works. It’s what you, the customer, end up building and maintaining around it.
Partner onboarding. Transfer Family has no native partner concept — partners are IAM users plus a folder convention you invented. AWS’s own FICO reference architecture stands up 145+ Terraform-managed resources and a custom dual-Lambda solution precisely to bridge that gap. Files.com models partner exchange as a first-class object, with directional folders, enforced permissions, and per-partner analytics built in.
Transformation and content routing. Transfer Family has zero native transformation. Every JSON, XML, CSV, X12, EDIFACT, or HL7 v2 conversion is a Lambda you write. Files.com runs Extract, Transform, Verify at intake — built-in virus scanning, a transformation engine, and content extraction that routes files on what’s inside them.
Completed-upload events. Transfer Family streams uploads straight to S3, so S3 sees temporary .filepart objects that fire events mid-transfer. Downstream systems start processing incomplete files unless you build filtering to ignore the partials and wait for the final rename. Files.com fires file-arrival events only when the upload has completed end-to-end — partial files never appear in destinations and never trigger automations.
The first three rows alone — partner workflow, transformation, content routing — are the integration-engine work AWS sells you Lambda, Step Functions, and EventBridge to assemble yourself. Files.com runs all of it in the same product that moves the files.
Files.com Starter is $199/month with every protocol included. Transfer Family is $216/month per protocol endpoint (the published $0.30/hour rate at 720 hours), each protocol billed separately, before any bytes move.
SFTP, FTPS, FTP, WebDAV, and AS2 all run from one Files.com site. Transfer Family meters each protocol endpoint on its own hourly charge.
A first-class, hierarchical partner model with directional folders, enforced permissions, and per-partner and per-channel analytics. Transfer Family has no concept of a partner — you build it on DynamoDB, IAM, API Gateway, and a custom UI.
Built-in virus scanning, a transformation engine for JSON, XML, CSV, X12, EDIFACT, and HL7 v2, and content extraction that routes files on what’s inside them. On Transfer Family, each of these is a Lambda pipeline you own.
SFTP users, the web UI, share links, and SSO / SAML all use one identity model. Transfer Family’s Web App is a separate identity stack from its SFTP users.
Files.com support owns the entire MFT product end to end. AWS Support covers the services; the application you assembled on them is yours to operate. Files.com is also SOC 2 Type II, HIPAA BAA, and GDPR DPA at the application layer.
What buyers ask most when comparing Files.com to AWS Transfer Family.
Stay on Transfer Family and your team owns the build: the partner workflow, the transformation pipeline, the audit application, and the end-user UI all become Lambda and Step Functions you assemble, test, and maintain forever.
If you want the assembled product — every protocol, the partner workflow, the audit log, the automations, and the transformation engine running on day one, in front of the same S3 bucket you already have — that’s Files.com. Mount your bucket with the S3 integration, keep publishing to Amazon SNS, and procure through AWS Marketplace against committed spend. Start a free trial on a real workload before you commit.
Every protocol, the partner workflow, the audit log, and the transformation engine — in one product, in front of the S3 bucket you already have. Talk to our team or run a free trial on a real workload.
No pushy sales process