If you host with AnonyMD, you're already used to infrastructure that puts privacy first. We're currently evaluating whether to add a new service to that lineup: S3-compatible object storage, paid for the same way as everything else here — in crypto, with no ID required.
Nothing is finalized yet. This post exists to explain what the service would actually be, and to ask whether it's something you'd use.
"S3" refers to the API standard originally introduced by Amazon's Simple Storage Service, which has since become the de facto standard for object storage. Unlike the disk attached to your VPS, object storage isn't a filesystem you mount — it's accessed over HTTPS through a straightforward API, using tools like rclone, restic, or any other S3-compatible client.
In practice, people use it for things like:
If you're running any kind of self-hosted service, there's a decent chance you've run into a spot where this would have been useful.
Most S3-compatible storage providers ask for the same kind of billing verification as any other cloud service — a card, an address, sometimes more. There have historically been a handful of providers offering crypto payment without identity verification in this specific niche, but in the time we've spent researching this, that field has narrowed considerably — more than one option that used to serve this space has shut down or quietly scaled back.
That's a real part of why we're considering this: it's genuinely useful infrastructure that's gotten harder to access without giving up privacy along the way.
The rough shape of the plan, subject to change based on what we hear:
We don't want to build this speculatively and hope people show up — we'd rather hear from real interest first. If this is something you'd use, or you have a rough sense of how much storage you'd need, reach out through our contact form. Even a quick "yes, I'd use this for X" helps us figure out whether it's worth building out properly.