AIOZ Storage Explained: S3-Compatible Decentralized Storage

AIOZ Storage is S3-compatible object storage that runs on AIOZ's decentralized physical infrastructure network instead of a single company's data centers. That distinction matters more than it sounds: it means the same aws s3 commands, SDKs, and migration tools you already use work against it, while the actual bytes are spread across a network AIOZ does not own outright. This article covers what AIOZ Storage actually is, how S3-compatible it really is in practice, and what its own documentation does and does not back up with real numbers.

TL;DR:

• AIOZ Storage is a drop-in S3-compatible object store built on AIOZ DePIN.
• Pricing is $17/TB for storage and $5/TB for delivery, with no free tier.
• Data is encrypted with a passphrase AIOZ itself never holds.

What Is AIOZ Storage?

AIOZ Storage is an S3-compatible object storage service, meaning it implements the same API surface as Amazon S3 so existing tools, SDKs, and code that talk to S3 can point at AIOZ Storage instead with just a changed endpoint and credentials. What sets it apart from a typical S3-compatible provider is where the data actually lives: AIOZ Storage is built on top of AIOZ DePIN, AIOZ's decentralized physical infrastructure network, rather than a fixed set of company-owned data centers.

That single design choice shapes everything else in this article: how replication works, how billing works, and how the encryption model is built around a passphrase AIOZ itself does not retain.

How AIOZ DePIN Powers AIOZ Storage's Decentralization

AIOZ's own documentation defines AIOZ DePIN as a decentralized physical infrastructure network that rewards node operators for contributing computing, storage, transcoding, and streaming resources. AIOZ Storage rides on this same shared network rather than running its own dedicated server fleet, which is also why it is priced and positioned differently from a conventional cloud storage bill: the underlying capacity comes from a distributed set of independently operated nodes, not one company's leased data center space.

AIOZ's documentation states plainly that data replication happens automatically on this network: "AIOZ DePIN inherently supports replication by default." It does not publish a specific replication factor, node count, or geographic distribution for how copies of your data get spread across the network, worth knowing if your use case depends on a specific durability guarantee.

Is AIOZ Storage Really S3-Compatible?

Mostly yes, with one tradeoff worth knowing before you commit to it. AIOZ Storage documents five ways to talk to it: SDKs for JavaScript, Go, and Python, a Postman collection using standard AWS Signature authentication, and the plain AWS CLI pointed at a custom endpoint (--endpoint-url https://s3.aiozstorage.network). None of these require a bespoke AIOZ client. If you already have code built against boto3, aws-sdk-go-v2, or @aws-sdk/client-s3, repointing it at AIOZ Storage is mostly a matter of swapping the endpoint, region, and credentials.

The tradeoff shows up around encryption. AIOZ's own docs note that to get full end-to-end encryption alongside S3 compatibility, you need to set up additional tooling, specifically a self-hosted gateway, rather than getting both out of the box in the standard S3-compatible path. Server-side encryption is the default and requires no extra setup; end-to-end encryption is available, but it is a deliberate opt-in step, not a checkbox. How AIOZ Storage encryption actually works covers the full mechanics, including the exact key derivation chain and which mode actually keeps AIOZ's servers away from your plaintext.

What You Get: Access Control and No Free Tier

Every AIOZ Storage account is a root account that can create sub-users, described in AIOZ's docs as a "sophisticated multi-role-based user system" that lets a team share one account without sharing one set of credentials. Access itself is governed by access grants, a credential type that bundles read, write, list, and delete permissions with an expiration window, rather than a single static API key that lives forever.

One thing AIOZ Storage does not have: a free plan. Its own getting-started documentation states this directly. Billing is pre-paid, calculated hourly against both the storage you are using and the bandwidth you consume, with no trial tier to test the waters before you deposit funds.

AIOZ Storage Pricing at a Glance

Per AIOZ's own pricing page, storage costs $17 per TB per month and delivery (bandwidth) costs $5 per TB, billed hourly against a pre-paid account balance funded with AIOZ tokens converted to a USD-equivalent value at the current market rate. AIOZ's pricing page also lists a "Pay with $AIOZ" option; the payment documentation walks through this same token-deposit-to-balance flow in detail, rather than a separate direct on-chain payment path. Three hard limits apply per account: 100 buckets, 100 sub-users, and a 100 request-per-second rate limit. Fall behind on payment and AIOZ locks the account (data stays intact, just inaccessible) for a 3-day grace period before deleting unpaid data permanently.

Compared with Amazon S3 Standard, at roughly $23 per TB for storage and $92 per TB for the first tier of internet egress, AIOZ Storage's delivery pricing in particular is a large gap. That gap narrows against newer alternatives built specifically to undercut hyperscaler egress pricing: Cloudflare R2 charges $15 per TB for storage and $0 for egress outright, which is cheaper on both axes than AIOZ Storage's current rate card. AIOZ Storage's honest pitch against modern competitors is not "cheapest storage available." It is S3-compatible, decentralized, dramatically cheaper than AWS specifically, and backed by an access-control model most S3-compatible providers do not offer.

Decentralized vs Centralized Storage: What Actually Changes

The practical differences between AIOZ Storage and a conventional centralized S3-compatible provider come down to capacity, encryption defaults, and billing. Capacity draws on a network of independently operated nodes rather than one company's data centers, which is the source of both AIOZ Storage's cost structure and its "no single point of failure" pitch. Encryption defaults are stronger: AIOZ never retains your bucket passphrase, under either encryption mode, which is beyond what most centralized providers offer without extra configuration. Getting the strongest version of that guarantee, where AIOZ's servers never touch your plaintext at all, means opting into end-to-end mode rather than relying on the server-side default. Billing looks different too, with no free tier, no card-based subscription, and no monthly invoice in the traditional sense, just an AIOZ-token-funded balance metered hourly.

What does not change: the API. Your existing S3 tooling, SDKs, and migration scripts work against AIOZ Storage largely unmodified, which is the whole point of building on an S3-compatible surface instead of a proprietary one.

Frequently Asked Questions

Is AIOZ Storage compatible with existing S3 tools and SDKs?
Yes. AIOZ Storage documents JavaScript, Go, and Python SDKs, a Postman workflow using AWS Signature authentication, and support for the standard AWS CLI pointed at a custom endpoint, all without a bespoke AIOZ client.

Does AIOZ Storage have a free tier?
No. AIOZ's own documentation states there is no free plan. The service is pre-paid, with storage and bandwidth billed hourly against a funded account balance.

How much does AIOZ Storage cost?
$17 per TB per month for storage and $5 per TB for delivery, according to AIOZ's official pricing page, with no per-request fees published.

What happens if my AIOZ Storage account runs out of balance?
The account is temporarily locked (your data is retained, just inaccessible) for a 3-day grace period. If the balance is not settled within that window, AIOZ deletes the unpaid data permanently.

Is AIOZ Storage cheaper than AWS S3?
For delivery/egress, yes, dramatically: roughly $5 per TB versus AWS's roughly $92 per TB for the first tier of internet egress. For raw storage, the gap is smaller, and some newer alternatives like Cloudflare R2 now undercut AIOZ Storage on storage price and egress cost combined.

What are AIOZ Storage's account limits?
100 buckets per account, 100 sub-users per account, and a 100 request-per-second rate limit, per AIOZ's published usage-limit documentation.

Does AIOZ Storage encrypt my data by default?
Yes, with server-side encryption on by default. AIOZ does not retain your encryption passphrase either way, but the server-side default does have AIOZ's servers decrypting data to serve it back to you; only the opt-in end-to-end mode keeps AIOZ's servers away from your plaintext entirely.

Related Reading

• How AIOZ Storage Encryption Actually Works - the exact key derivation chain, the two encryption modes, and what AIOZ's docs do and do not disclose about them.
• Zero-Knowledge Encryption: AIOZ Storage Can't See Your Data - why AIOZ never holds your bucket passphrase, and what to actually do about backing it up.
• AIOZ Storage Access Control: Macaroons and Access Grants - how permissions, access grants, and sub-users work on top of the S3-compatible layer described here.
• Migrate from Amazon S3 to AIOZ Storage with rclone - the actual config change for moving an existing S3 bucket over.
• How AIOZ Storage Pricing Works - the full billing mechanics, a worked cost example, and how the rate card compares to AWS and modern alt-cloud providers.
• AIOZ Storage Glossary: Bucket, Passphrase, Macaroon - quick definitions for every term used across this series, and where AIOZ's own docs disagree on naming.
• What Is Amazon S3? Object Storage Explained - the general bucket/object/key model this article's S3-compatibility claim builds on, and what "S3-compatible" actually means industry-wide.
• How to Use AIOZ Storage Effectively: A Practical Checklist - a 7-item checklist synthesizing the setup, encryption, and access-control decisions covered across this hub into one actionable list.
• Data Durability vs Availability: What 11 Nines Means - what AWS and Google Cloud publish for both guarantees, and what AIOZ Storage's own documentation does and doesn't confirm about either.
• Hot vs Cold Storage: Storage Tiers and When They Matter - why AWS and Azure price storage differently by access frequency, and why AIOZ Storage's flat rate skips that decision entirely.
• What Is a CDN and How Does It Relate to Object Storage? - what AIOZ Storage's $5/TB delivery fee is actually paying for, and what its documentation does and doesn't confirm about the mechanism.
• RBAC vs ABAC vs Capability-Based Access Control Explained - the theoretical model behind AIOZ Storage's macaroon-based access grants, with NIST's own definitions for the two alternatives.
• The 3-2-1 Backup Rule: A Practical Framework Explained - where AIOZ Storage fits in a real backup strategy, and the one modern extension its documentation doesn't confirm.
• Setting Up a Self-Hosted S3 Gateway for AIOZ Storage - the full walkthrough for true end-to-end encryption, keeping AIOZ's servers away from plaintext entirely.
• Managing AIOZ Storage Buckets with Terraform, Step by Step - bringing AIOZ Storage into an existing infrastructure-as-code workflow alongside real AWS resources.
• Multi-Cloud Storage Disaster Recovery with AIOZ and S3 - using AIOZ Storage as a genuinely independent second provider alongside AWS S3.

References

• AIOZ Storage Documentation: S3 Compatibility
• AIOZ Storage Documentation: Decentralized Storage
• AWS S3 Pricing 2026 Guide
• AWS Documentation: What Is Amazon S3?