Estimate OSS costs across storage classes, data transfer, API requests, lifecycle transitions, and CDN acceleration.
Last verified: May 2026
$0.005 per 10K requests
$0.001 per 10K requests
$0.087/GB outbound data transfer.
Output will appear here...Alibaba Cloud Object Storage Service (OSS) bills on stored capacity, requests, and outbound traffic, with multiple storage classes (Standard, IA, Archive, Cold Archive) and CDN integration. The OSS Cost Estimator models a workload's storage volume, monthly egress, request count, and CDN usage to produce an itemized monthly bill so storage-vs-egress-vs-requests trade-offs are explicit.
Standard: hot data, lowest retrieval cost, highest storage cost. IA (Infrequent Access): cheaper storage, higher retrieval cost, suitable for monthly-access patterns. Archive: cheap storage, several-hour retrieval delay, suitable for true archives. Cold Archive: cheapest storage, longest retrieval, suitable for compliance retention. Each lower tier has a minimum storage duration that, if violated, incurs a penalty.
Enabling Alibaba Cloud CDN in front of OSS replaces origin egress with cached delivery at the edge. CDN egress is billed separately (usually lower per GB), and cache hits don't count against OSS bandwidth. For a high-traffic static site, CDN can reduce origin bandwidth by 80-95%.
You're considering moving a 2 TB asset library from S3 to OSS. The estimator models 2 TB Standard storage, 500 GB monthly egress, 1.5 million GETs, and 30,000 PUTs. Total cost: about 30% lower than the current S3 bill, plus the CDN integration is simpler since both are Alibaba services. Migration scheduled for next sprint after a smaller pilot validates the cutover process.
The estimator takes storage capacity per tier, monthly egress, request count by type (GET, PUT, etc.), and CDN configuration as inputs. It applies the published per-GB and per-1000-request rates, accounts for minimum storage duration where applicable, and produces an itemized monthly bill. CDN modeling uses a configurable cache hit ratio (default 90%) to estimate origin offload.
Don't use Archive or Cold Archive for working data — the retrieval fees and minimum storage duration penalties wipe out the savings if access is more than rare. Use them for true archives only.
Set lifecycle rules to clean up incomplete multipart uploads. They're silent storage leaks and can accumulate to gigabytes of partial chunks if not pruned.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.