AIOZ Stream Pricing Explained: A Full Cost Breakdown

Most video infrastructure pricing pages end in a "contact sales" button. AIOZ Stream's doesn't: storage, delivery, and transcoding are each a flat published rate, billed from one wallet, with no quote to request and no volume tier to qualify for first. Here is the full rate card, how the billing actually works, and the one real tradeoff that comes with paying in tokens instead of a fixed monthly invoice.

TL;DR:

• AIOZ Stream charges $0.02/GB/month for storage, $0.02/GB for delivery, and $0.01-0.05/min for transcoding depending on resolution.
• Everything bills from one AIOZ token wallet with a 0.01 AIOZ minimum deposit, no negotiated contract, no separate billing relationship per service.
• Because the wallet is funded in a token with a floating price, the effective cost of a deposit in your local currency isn't fixed the way a traditional invoice is.

The full rate card

How the billing actually works

Every AIOZ Stream account gets an auto-generated wallet that holds AIOZ tokens, and only AIOZ tokens; depositing a different token risks losing it permanently, since the wallet isn't built to hold anything else. The minimum deposit is 0.01 AIOZ, converted at the live AIOZ/USDT market rate at the moment you deposit. From there, usage across all three services (storage, delivery, transcoding) draws down the same balance, and a daily usage history in the dashboard tracks exactly what was consumed and what it cost. Whatever mix of storage, delivery, and transcoding a given month actually used shows up on the same statement, instead of three separate bills to reconcile against each other.

The tradeoff worth knowing about

A traditional cloud invoice is denominated in your local currency and doesn't move once the rate is set. AIOZ Stream's rates are denominated in dollars, but the wallet itself holds AIOZ tokens, and tokens get converted at whatever the market rate happens to be at deposit time. That means the per-GB and per-minute rates are fixed, but how much local currency you actually need to fund a given amount of usage shifts with the token's price. There's no hidden fee or markup buried in that, it's a direct consequence of billing through a token wallet rather than a bank-denominated account, and it's worth budgeting for if you're used to a cloud bill that never moves between invoices.

A worked example: what a mid-sized VOD library might cost

Say a library holds 500GB of encoded video, serves 2,000GB of delivery in a given month, and that month you transcode 100 hours of new source footage. The transcoding line is where people usually get surprised: the rate card bills per minute of output, not per minute of source, and adaptive bitrate delivery means one hour of source typically becomes several output renditions, not one. Assume three renditions per source hour, a reasonable middle ground for an SD-to-HD ladder:

Transcoding dominates the bill in this example, not because the per-minute rate is high, but because it's multiplied by however many renditions your ABR ladder actually produces. A library that only needs one rendition per source hour would see that same transcoding line drop to $60, for a $110 total. The lesson isn't the specific dollar figure, it's that the rendition count is the real lever on this line item, more than the per-minute rate itself.

How this compares to a negotiated cloud contract

Most enterprise video infrastructure pricing isn't actually published; getting a real number means a sales call, and the number you get often depends on your committed monthly spend rather than a rate card anyone can look up in advance. AIOZ Stream's three rates are the same for every account, visible before you sign up for anything, and don't change based on how much you commit to spend. The transcoding line specifically has already been checked directly against AWS's and Google Cloud's own published transcoding prices, including where AIOZ Stream isn't the cheapest option, in a dedicated transcoding pricing comparison, since a full three-way price comparison across every service is a bigger claim than one rate card can back up on its own.

Frequently Asked Questions

Do storage, delivery, and transcoding get billed separately?
No. All three draw from the same AIOZ token wallet balance, tracked in one daily usage history rather than three separate invoices.

Is there a minimum monthly spend or contract?
No. The only minimum is a 0.01 AIOZ deposit to fund the wallet; there's no committed monthly spend or contract term.

Does the per-GB or per-minute rate change with volume?
No. The published rates are flat regardless of how much storage, delivery, or transcoding you use.

Why would my bill differ month to month if the rates are fixed?
Two reasons: your actual usage changes, and the wallet is funded in AIOZ tokens converted at the market rate at deposit time, so the local-currency cost of topping up isn't fixed the way a traditional invoice would be.

Can I deposit a different cryptocurrency into my AIOZ Stream wallet?
No. The wallet is built to hold AIOZ tokens only; depositing a different token risks losing it permanently.

Related Reading

• AIOZ Stream Transcoding Pricing vs AWS and Google Cloud: the full numeric comparison for the transcoding line specifically
• One DePIN, Three Workloads: why storage, compute, and delivery sharing one network is also why they share one bill
• What Is AIOZ DePIN: how token-based compensation to node operators is what makes this pricing model possible

References

• AIOZ Stream payment documentation: the official source for the rates and wallet mechanics described above
• Video Streaming APIs: What Developers Actually Need to Know, Mux: general background on how video infrastructure pricing is typically structured