Skip to content
BloberThe Safest, Easiest Way to Move Cloud Files
Articles
On this page

Decentralized and Web3 S3-Compatible Storage (Storj, Filebase, and More)

· 4 min read · Updated

Add as preferred source
Copy page
View as MarkdownOpen in ChatGPTOpen in Claude
Decentralized and Web3 S3-compatible storage backed by node networks

Decentralized storage spreads your data across a network of independent nodes instead of one company's data centers. Day to day, you reach it through an S3-compatible gateway, which puts a standard S3 API in front of the decentralized backend, so your existing S3 tools can write to IPFS, Sia, or a node network without touching the underlying protocol. Below are the decentralized and Web3 providers with such a gateway, and how to connect each one.

This is one category in our complete list of S3-compatible storage providers. Each of them connects to Blober through the generic S3-Compatible provider, provided the gateway supports the common S3 operations Blober uses: you enter the gateway endpoint and the keys the network issues.

Storj

Storj is decentralized cloud storage where files are encrypted, split, and erasure-coded across thousands of independent nodes worldwide. S3 tools talk to its hosted S3-compatible gateway, which handles all of that for them.

  • Endpoint format: gateway.storjshare.io, with regional gateways gateway.eu1.storjshare.io, gateway.us1.storjshare.io, and gateway.ap1.storjshare.io.
  • Addressing: virtual-hosted.

S3 credentials are generated from an access grant in the Storj console. Storj is globally distributed by default; when an S3-compatible tool requires a region, set it to global[1]. Use a large multipart cutoff for very large files. Storj also appears on our object storage specialists page.

Filebase

Filebase is an S3-compatible gateway that stores objects on decentralized networks (IPFS, and historically Sia and Storj) and gives you a familiar S3 API and console.

  • Endpoint format: s3.filebase.io.
  • Addressing: both path-style (https://s3.filebase.io/<bucket>/<key>) and virtual-hosted (https://<bucket>.s3.filebase.io/<key>) are supported.

Filebase uses a single global endpoint and the region auto. Public-bucket reads should use the virtual-hosted URL, which the Filebase CDN serves[2].

4everland

4everland is a Web3 infrastructure platform whose Bucket service has an S3-compatible API backed by IPFS and Arweave. It is built for hosting and pinning assets on decentralized networks while you keep the S3 workflow.

  • Endpoint format: endpoint.4everland.co.
  • Addressing: virtual-hosted.

Generate keys in the 4everland dashboard. The documented S3-compatible endpoint is https://endpoint.4everland.co[3].

Akave

Akave provides decentralized object storage with an S3-compatible interface (Akave O3) aimed at data availability for AI and Web3 workloads.

  • Endpoint format: the S3-compatible gateway endpoint issued in your Akave account.
  • Addressing: virtual-hosted.

The production gateway address is account-specific, so confirm the endpoint host and credentials in the Akave console. Akave's docs list akave-network as the region value for its decentralized S3 interface and show hosted endpoints such as https://o3-rc2.akave.xyz for specific environments[4].

How the gateway pattern works

Most decentralized networks were not designed around the S3 API. A gateway makes them usable from ordinary tools by translating S3 calls into the network's native operations: pinning to IPFS, contracts on Sia, erasure-coding across Storj nodes, and so on. From your side, it is an endpoint and a pair of keys.

For the same reason, Blober can treat a decentralized gateway like a normal S3 target for common object operations. You point the S3-Compatible provider at the gateway and transfer as usual, without dealing with the network protocol.

A few practical points for decentralized targets:

  • Some gateways do not implement S3 server-side copy. Blober then streams the copy through your computer, so transfers still work.
  • Listing and metadata behavior can differ. Treat these stores as S3-compatible for the common operations (browse, upload, download) and confirm any advanced behavior with the provider.
  • Encryption is often built in, but check where it happens. Networks like Storj encrypt and erasure-code data before it leaves the hosted gateway, yet the gateway still handles the upload. Add client-side encryption if your threat model requires that the gateway itself never sees plaintext.

Frequently asked questions

Is decentralized storage really S3-compatible? Through the gateway, yes. The networks use their own native operations underneath, and the gateway translates S3 calls into them, so you connect to the gateway endpoint with S3 keys and standard S3 tools work.

Can I move data from AWS S3 to Storj or Filebase? Yes. The gateways speak S3, so in Blober you set the S3 bucket as the source and the gateway endpoint as the destination.

Do these keep my data private? Several encrypt data before it is distributed, Storj among them. The details differ between networks, so check each provider's encryption model.

Why might a transfer behave differently than to AWS? Some gateways limit server-side copy or return listings differently. When native copy is unavailable, Blober falls back to copying through your computer and the transfer still completes.