What's your use-case? What do you want to achieve?
Using blob storages as filesystems doesn't work well and could - with B2's pricing structure - became excessively expensive. Blob storages are designed for easily writing and reading individual blobs. Filesystems are designed for random access, listing, traversal, etc.
It's for storing a few terabytes of fairly static media (for the most part, write-once). The codebases using it don't natively support object storage (and will be in Docker containers).
It's on a Hetzner server, and Backblaze (even after the price increase) will be a lot cheaper than normal drives, although their storage box option is probably better value over about two GB.
But the thing is: B2 is cheap for storage, but retrieval and traversal are very expensive. And if that happens transparently on the filesystem (because you accidentally run grep or the service in question regularly hashes the files or something), you would implicitly download everything stored. And IIRC retrieval costs ten times the storage costs... each time.)
Backblaze recently revised B2 storage, it's gone up by $1 and they offer free egress equal to I believe 2x or 3x the data you have stored with them. Let me try find a link to this...
I plan to switch over later when it makes sense to - the nice thing about Backblaze is that it scales with your storage, whereas with Hetzner you have to jump from 1 TB to 5 TB.