| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Managed file transfer | Data platform | 2% | 10 of 97 | 7% | 14 | accepted challenger |
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-5.4 mini | 0 | 0 | 0 | 1 | 1 |
| Gemini 3.5 Flash | 0 | 1 | 0 | 0 | 1 |
| Perplexity Sonar | 0 | 1 | 1 | 0 | 2 |
| Grok 4.1 Fast | 0 | 0 | 0 | 0 | 0 |
| Mistral Small | 0 | 0 | 1 | 0 | 1 |
| DeepSeek V4 Flash | 0 | 1 | 0 | 0 | 1 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 3 | 0 | 0 | 3 |
| Kimi K2 | 1 | 0 | 0 | 0 | 1 |
| GLM 4.7 FlashX | 0 | 1 | 0 | 0 | 1 |
| MiniMax M2.5 | 0 | 0 | 0 | 0 | 0 |
| GPT-6 Luna | 0 | 0 | 1 | 0 | 1 |
| Muse Glimmer 30B | 0 | 1 | 1 | 0 | 2 |
Verbatim evidence the judge attached to positive labels.
“Start with Files.com or AWS Transfer Family” Kimi K2 · MFT · paraphrase prompt · first choice
“consider migrating to a more secure MFT provider or a purpose-built cloud storage service (like AWS Transfer Family or Azure Data Box)” GLM 4.7 FlashX · MFT · negative prompt · alternative
“Best for seamless cloud integration, enables fully managed SFTP, FTPS, and FTP transfers directly into Amazon S3 or EFS” Muse Glimmer 30B · MFT · comparative prompt · alternative
“best if your company already runs heavily on AWS and wants managed SFTP endpoints plus transfer logs” Perplexity Sonar · MFT · paraphrase prompt · alternative
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“users note costs can rise quickly for low-volume or intermittent transfers” GPT-5.4 mini · MFT · budget prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 43 of the 45 answers that named AWS Transfer Family and are not a share of its labels.
186 of the 186 domain citations in answers naming AWS Transfer Family came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read October 5, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
What AWS Transfer Family's own pages state, read October 5, 2026: aws.amazon.com/aws-transfer-family, aws.amazon.com/aws-transfer-family/mft, aws.amazon.com/aws-transfer-family/as2, aws.amazon.com/aws-transfer-family/faqs, aws.amazon.com/aws-transfer-family/pricing. A claimed page can correct any of them.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when AWS Transfer Family's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as AWS Transfer Family, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for AWS Transfer Family by email, built from the raw record of the edition. It shows: