The AWS side uses list pricing from the AWS Transfer Family pricing page and the surrounding service pages (S3, VPC, Secrets Manager, Lambda) as of May 2026. Every line item in the result shows the math and links to the page you can verify it against. Transfer Family endpoints are billed per protocol, per hour — the meter runs around the clock whether or not a file moves.

The line items are only the AWS bill. Transfer Family moves files in and out of S3; the partner workflow, the file conversion, the audit log, and the screens your users see are yours to build in AWS Lambda code. AWS’s own published FICO build ran 145+ Terraform-managed resources with a custom dual-Lambda integration bridge and a custom Splunk audit pipeline — none of which shows up in the calculator, and all of which Files.com ships built in.

The Files.com side uses published Starter and Power annual pricing and the published overage rates. Every part you’d build on AWS — partner channels, transformation, scanning, the audit log, the UI, share links, PGP — ships inside that price. Want the full argument, not just the numbers? Read the Files.com vs. AWS Transfer Family comparison.