Public record of AeroFTP tests across two distinct workflows: integration / capability runs (does it work, on which provider, with which command) and performance benchmarks (how fast does it work, measured against other clients on the same link or contributed by the community).
This section is not user-facing documentation. For usage guides see Getting Started.
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 |
How fast it works. Two kinds of record: comparative batteries, where AeroFTP and other clients run the same cells on the same link with integrity checks on every download, and community rounds of aeroftp-cli benchmark against real provider accounts.
| Document | Scope |
|---|---|
| Comparative battery 2026-10-03 | AeroFTP 4.2.1 against rclone and Cyberduck CLI on SFTP, FTP with TLS, WebDAV and S3, two passes |
| DAG engine review, September 2026 | Before and after measurements of the transfer fixes that shipped in 4.2.0, rclone as the control on every row |
| Community Benchmark | Performance rounds contributed by the community through the benchmark issue template |
| 2026-05-07 baseline | Historical: maintainer reference run on v3.7.3 / v3.7.4, 35 sanitized reports, fixes shipped in 5 commits. Later releases changed several of these numbers |