Object storage must be judged by durability and recovery, not just upload speed. SeaweedFS can expose an S3-compatible endpoint, but a production pilot needs the topology and security settings you would really operate.
Upload a mixed dataset with checksums. Test list, range read, multipart upload, deletion, and the S3 operations your application uses. Stop a volume server in staging and verify reads and repair behavior. Back up filer metadata, then restore the sample onto a fresh deployment. The SeaweedFS project documents its master, volume, filer, and S3 components.
Configure credentials and TLS explicitly; do not expose a test endpoint with permissive defaults. Compare capacity, latency, operational effort, and failure recovery with alternatives. A successful write is not proof that the object will still be readable after an incident.
Akousa