All Products
Search
Document Center

Tair (Redis® OSS-Compatible):Tair Serverless KV billing

Last Updated:May 13, 2026

Fees for Tair Serverless KV consist of computing resource fees (RCU/WCU) and storage space fees.

Billable items

Redis-compatible version

  • Computing resource consumption (pay-per-operation)

    • Read operations (RCU): One RCU is consumed for every 4 KB of data read per request. Data smaller than 4 KB is calculated as 4 KB.

      For example, reading 1 KB or 4 KB of data consumes 1 RCU. Reading 7 KB (4 KB + 3 KB) of data consumes 2 RCUs.

    • Write operations (WCU): One WCU is consumed for every 512 B of data written per request. Data smaller than 512 B is calculated as 512 B.

      For example, writing 200 B of data consumes 1 WCU. Writing 1 KB (1024 B = 512 B × 2) of data consumes 2 WCUs. Writing 1.2 KB (1228 B ≈ 512 B × 2.4) of data consumes 3 WCUs.

    Examples of CU calculations for common commands

    Category

    Calculation rule

    Scan commands for primary keys

    (such as SCAN, KEYS)

    1 base RCU plus RCUs based on the total size of scanned keys.

    General commands

    (such as DEL, EXISTS)

    Consumes n WCUs, where n is the number of keys.

    KV structure

    (such as String)

    Write

    (such as SET)

    Key does not exist

    WCUs are calculated based on key size + value size.

    Key exists

    The operation has two steps: a read that consumes RCUs based on the key size, and a write that consumes WCUs based on key size + value size.

    Read

    (such as GET)

    Key does not exist

    Consumes 1 RCU.

    Key exists

    RCUs are calculated based on key size + value size.

    KKV structure

    (such as Hash, Set, Zset, List, Geo)

    Write

    (such as HSET)

    Key does not exist

    WCUs are calculated based on key size + field size + value size.

    Key exists, field does not exist

    First, a read operation consumes RCUs based on the key size. Then, a write operation consumes WCUs based on key size + field size + value size.

    Key and field exist

    This operation has three steps. First, reading the key consumes RCUs based on its size. Second, reading the old value consumes RCUs based on key size + field size + old value size. Finally, the write consumes WCUs based on key size + field size + new value size.

    Read

    (such as HGET)

    Key does not exist

    Consumes 1 RCU.

    Key exists, field does not exist

    RCUs are calculated based on the key size.

    Key and field exist

    The operation consumes RCUs based on the key size, plus additional RCUs based on key size + field size + value size.

    Scan-type

    (such as HSCAN)

    Key does not exist

    Consumes 1 RCU.

    Key exists

    2 base RCUs, plus additional RCUs based on the total size of scanned fields and values (if values are returned).

  • Storage space usage

    You are billed for the actual hourly storage space usage of an instance, measured in gigabytes (GB). Storage usage under 20 GB is billed as 20 GB. Usage over 20 GB is rounded up to the nearest integer.

    For example, 15 GB of storage is billed as 20 GB, and 50.2 GB of storage is billed as 51 GB.

DynamoDB-compatible version

  • Computing resource consumption (pay-per-operation)

    • Read operations (RCU): One RCU is consumed for every 4 KB of data read per request. Data smaller than 4 KB is calculated as 4 KB.

      For example, reading 1 KB or 4 KB of data consumes 1 RCU. Reading 7 KB (4 KB + 3 KB) of data consumes 2 RCUs.

    • Write operations (WCU): One WCU is consumed for every 1 KB of data written per request. Data smaller than 1 KB is calculated as 1 KB.

      For example, writing 1 KB of data consumes 1 WCU. Writing 2 KB (2 KB = 1 KB × 2) of data consumes 2 WCUs. Writing 2.2 KB (2.2 KB ≈ 1 KB × 2.2) of data consumes 3 WCUs.

  • Storage space usage

    You are billed for the actual hourly storage space usage of an instance, measured in GB. Storage usage under 20 GB is billed as 20 GB. Usage over 20 GB is rounded up to the nearest integer.

    For example, 15 GB of storage is billed as 20 GB, and 50.2 GB of storage is billed as 51 GB.

Pricing

Available regions

RCU

WCU

Storage

China (Beijing), China (Shanghai), China (Hangzhou), China (Shenzhen)

USD 0.026 per million requests

USD 0.052 per million requests

USD 0.00029 per GB-hour

Indonesia (Jakarta), Singapore

USD 0.03 per million requests

USD 0.063 per million requests

USD 0.00035 per GB-hour

Billing method

Billable item

RCU

WCU

Storage

Usage statistics

  • The system counts the RCUs and WCUs consumed by an instance each second.

  • Total consumption is aggregated daily.

  • Usage is billed per million requests and rounded up to the next full million.

  • The system calculates the average hourly storage usage (in GB) for the instance. If the usage is less than 20 GB, it is billed as 20 GB.

  • The total consumption is aggregated daily.

  • Usage is billed per GB and rounded up to the nearest integer.

Daily fee calculation formula

Fee = CEILING(Total daily requests / 1,000,000) × Unit price

Fee = Total daily GB-hours × Unit price

Billing cycle

Daily

Daily

Billing examples

  • Example 1: Low-usage scenario

    Assume an instance in the China (Beijing) region has the following usage for a day:

    • Total RCUs consumed: 1.1 million

    • Total WCUs consumed: 0.2 million

    • Storage usage: 30 GB for 18 hours and 50 GB for 6 hours

    Daily fee calculation:

    1. RCU fee:
      Billable requests: 1.1 million, rounded up to 2 million.
      Fee: 2 million × USD 0.026 per million requests = USD 0.052














































    2. WCU fee:
      Billable requests: 0.2 million, rounded up to 1 million.
      Fee: 1 million × USD 0.052 per million requests = USD 0.052














































    3. Storage space fee:
      Billable usage: (18 hours × 30 GB) + (6 hours × 50 GB) = 840 GB-hours
      Fee: 840 GB-hours × USD 0.00029 per GB-hour = USD 0.2436














































    Total daily fee = RCU fee + WCU fee + storage space fee = 0.052 + 0.052 + 0.2436 = USD 0.3476.

  • Example 2: High-usage scenario

    Assume an instance in the China (Shanghai) region has the following usage for a day:

    • Total RCUs consumed: 11.8 million

    • Total WCUs consumed: 5.3 million

    • Storage usage: 500 GB for 6 hours, 450 GB for 13 hours, and 600 GB for 5 hours

    Daily fee calculation:

    1. RCU fee:
      Billable requests: 11.8 million, rounded up to 12 million.
      Fee: 12 million × USD 0.026 per million requests = USD 0.312














































    2. WCU fee:
      Billable requests: 5.3 million, rounded up to 6 million.
      Fee: 6 million × USD 0.052 per million requests = USD 0.312














































    3. Storage space fee:
      Billable usage: (6 × 500) + (13 × 450) + (5 × 600) = 11,850 GB-hours
      Fee: 11,850 GB-hours × USD 0.00029 per GB-hour = USD 3.4365














































    Total daily fee = RCU fee + WCU fee + storage space fee = 0.312 + 0.312 + 3.4365 = USD 4.0605.