Database proxy billing update

This topic describes the billing updates for database proxy in OceanBase Cloud.

Billing updates for Exclusive tier

• Newly charged cloud vendors: Exclusive tier database proxy will be fully charged. Existing Exclusive tier database proxies will be billed on a pay-as-you-go basis from the specified effective time. Exclusive tiern proxy instances created after that time will be automatically billed on a pay-as-you-go basis.

• Billing rule: Total cost for database proxy = Price per vCPU‑hour × Number of vCPU per node × Number of nodes × Duration.

• Proxy deployment modes: Exclusive tier will support three deployment modes: single-zone deployment, dual-zone active-active deployment, and dual-zone primary-standby deployment. The new deployment modes no longer support three-zone deployment.

Billing updates for Shared tier

General tier renamed to Shared tier. The free quota for the Shared tier across different cloud vendors is calculated as the combined vCPUs of all Shared proxy clusters within an OceanBase instance can be up to 1/4 of the total vCPUs of the OceanBase instance's full‑featured replica nodes. Existing General proxy clusters are not affected. However, if the total number of vCPUs of your existing General proxy clusters already exceeds the new free quota, any additional proxy clusters must use the Exclusive tier when creating new database proxy clusters.

Example: For a dual‑IDC 16 vCPU (1‑1) deployment, the Shared tier free quota for that OceanBase instance is 16 × 2 / 4 = 8 vCPUs. You could create one 4 vCPU dual‑node proxy cluster, or two 2 vCPU dual‑node proxy clusters, etc. The minimum size for a single proxy node is 0.25 vCPU. If the total number of vCPUs of all General proxy clusters already exceeds 8, new tenants or read‑only/read‑write split endpoints can only be backed by Exclusive proxy clusters.

Database proxy pricing