Home / Alibaba Cloud
Alibaba Cloud ACR Enterprise Edition / OSS-backed registries
www.alibabacloud.com/help/en/acr/product-overview/billing-deRegistrystorage/alibaba-cloud-acr-enterprise-edition-oss-backed-registriJSONcomparereport an errorprovider JSON
- Free allowance
- Enterprise Edition stores artifacts in YOUR OSS bucket, so 'registry storage' is just OSS storage and is billed as OSS pay-as-you-go.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| Free tier | Enterprise Edition stores artifacts in YOUR OSS bucket, so 'registry storage' is just OSS storage and is billed as OSS pay-as-you-go. There is no free allowance. unit none; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Identity | email (placeholder) not published |
|---|
| Egress | OSS outbound traffic is charged unless you disable public network access and pull only over a VPC endpoint. |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | oci oci |
|---|
| Tooling | oras / docker push; the registry is a façade over OSS. |
|---|
| Composes with | None — it inherits OSS pricing, which is metered. |
|---|
| Reliability | Documented here only because it explains a trap: several 'free registry' pages (Alibaba EE, Baidu CCR EE) are OSS/BOS front-ends whose real cost sits in the bucket. |
|---|
Evidence 1
More fields 1
| dead end | {"failure_class": "paid","why": "Enterprise Edition stores artifacts in YOUR OSS bucket, so 'registry storage' is just OSS storage and is billed as OSS pay-as-you-go. There is no free allowance.","retry_when": null,"first_recorded": "2026-10-21"} |
|---|
Unknown values 4
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read