Shareboxed
If you already pay for storage, sharing should not mean paying someone else to store the same bytes again. Shareboxed can upload straight into a bucket you own, on AWS S3, Cloudflare R2, Backblaze B2, MinIO or anything else that speaks the S3 API, and still hand you a proper sharing link at the end.
How the split works
The files go from your Mac directly into your bucket, under their own names, in a dated folder per upload. They never pass through us. What we keep is the least that still lets a link work: a read credential for that bucket, stored encrypted, and the file list of each share, encrypted with a password we cannot read.
When a recipient opens the link, their browser asks us to sign each download, and the bytes come straight from your bucket to them. Because we sign every download on request, a link can be revoked at any moment, something a plain presigned URL can never do.
Why not just use presigned URLs?
You can, and for one file to one colleague they are fine. Their limits show up quickly: S3 caps a presigned URL at seven days, there is no such thing as a link to a folder of files, and a URL that has been sent cannot be taken back. A Shareboxed link wraps your bucket in the things S3 does not do: one link for a whole batch, a password if you want one, revocation, and a download page a normal human can use.
Setting it up
The whole setup is one bucket and one narrowly scoped key, and the S3 guide walks through it with copy-paste CLI commands, including the optional cleanup rules that delete uploads after a week. Turning the sharing switch off deletes the credential we held and ends every link from that connection at once. Your files stay exactly where they always were: in your bucket.