Skip to content
AeroFTP Test Reports
Public record of AeroFTP tests across two distinct workflows: integration / capability runs (does it work, on which provider, with which command) and community performance benchmarks (how fast does it work, with statistical aggregates).
Purpose
- Operational evidence: for each area, a matrix showing what works on which provider with which command.
- Reproducibility: exact commands and Docker environments documented so anyone can re-run.
- Transparency: we publish every passing test, every environment, and every methodology.
This section is not user-facing documentation. For usage guides see Getting Started.
Capability and integration
Binary checks: a feature works on a provider, or it does not. Driven by Docker harnesses and provider-by-provider matrices.
| Document | Scope |
|---|---|
| Provider Coverage Matrix | Coverage class and score for supported providers |
| S3-compatible providers | AWS, Backblaze, Storj, Wasabi, Cloudflare R2 |
| WebDAV providers | Koofr, FeliCloud, InfiniCloud JP, DriveHQ |
| Docker matrix 2026-04-18 | FTP, SFTP, WebDAV, S3/MinIO on local containers |
| AeroAgent capability matrix | 25 AeroAgent capabilities tested with Gemini and Cohere |
Performance and benchmarks
Statistical numbers: how many Mbps, what p50, p95, latency. Driven by aeroftp-cli benchmark runs against real provider accounts, sanitized JSON reports submitted by the community.
| Document | Scope |
|---|---|
| Community Benchmark | Performance rounds, contributed by the community via issue #177 |
| 2026-05-07 baseline | Maintainer reference run, 35 sanitized reports, 5 fixes shipped |