S3-Compatible Object Storage in the EU You Can Pay for in Bitcoin

For a lot of teams, the hyperscalers have quietly become unreliable, not the technology, the access. A payment method gets declined, then the account is locked, and two years of backups sit in an S3 bucket you can no longer reliably reach.

The fix isn't exotic: S3-compatible storage, in a stable jurisdiction, that you can actually pay for.

The problem isn't the storage. It's the account.

Cards stop working. Accounts get frozen on a risk-model flag with no human to appeal to. A vendor you built your backups around becomes a vendor who can lock you out on a Tuesday. The pattern is the same everywhere: it isn't the technology that fails, it's the access, and it hits teams outside the comfortable middle of the map first.

Object storage itself is a solved problem. The S3v4 API is a de-facto standard, and every serious tool (rclone, restic, Veeam, Commvault) speaks it. What's missing for these teams is a provider that lives in a jurisdiction they trust, takes a payment method that actually clears, and won't disappear their data on an automated flag.

What ZERO-Z3 is: and what it isn't

ZERO-Z3 is S3-compatible object storage, hosted in the EU on our own network (AS215197). Full S3v4 API, so it drops into your existing tooling without a rewrite. €5/TB egress, no per-request charges. The cost side is broken down in S3 storage costs: the math.

Payment works the normal way, bank transfer (SEPA) and credit card via Stripe, and for teams whose cards don't clear, Bitcoin. That last part is the reason many customers find us: it's simply the option that works for them.

One thing we're deliberate about: this is legitimate EU infrastructure, not “bulletproof” or anonymous hosting. We're a German GmbH, GDPR-compliant, with a real contract and a real address. That's a feature, not a limitation. Your data sits under European law, not in a grey zone that can vanish faster than an AWS account.

Moving your data over

If your data is still reachable, migration is a single rclone command against both endpoints:

rclone sync s3-old:mybucket zero-z3:mybucket --progress

Point restic or Veeam at the ZERO-Z3 endpoint and your backup jobs keep running as before. Same API, different provider. One you can pay and one that won't lock you out. A step-by-step walkthrough lives in S3 data migration done right.

What to check before you switch

Be honest about a few things, because we'd rather you stay than churn:

• Latency and throughput. EU-hosted is great if your users or compute are near the EU. Don't take our word for it. We run s3compare.io, a public benchmark comparing S3 providers with open methodology and raw data.
• Your egress pattern. €5/TB egress is real money if you serve or restore a lot. Do the math against what you pay now.
• Your payment reality. If cards work fine for you, use SEPA or Stripe. If they don't, Bitcoin is there.

Migrating backups over is an afternoon's work, and the first invoice can be paid in Bitcoin. After that, storage should be boring again. That's the point.