I had previously used seaweedfs, which has more moving parts but seems more feature-rich. It was overkill for a homelab, so I went to garage.
Garage is very stable, but the metadata engine / file MUST live on NVMe. Otherwise it gets slow on small files. It also lacks features like per bucket retention settings and stuff. It really is "just" a S3 bucket.
The trouble I had with SeaweedFS was that the docs I found were rather sparse. Garage, on the other hand seemed pretty well documented.
The very first thing Garage did after I installed it on a test three-node cluster is get corrupted and lose files.
No thanks.
For testing/dev setups you can turn sync off and get some performance back but that's only useful for cases where losing data is okay.