Product pricing
Updated at：2025-11-14
The product of Baidu Log Service (BLS) adopts a postpaid bill type, with real-time billing based on actual use. The specific rules are as follows:
Billing rules
- Active read-write Shard charge item: Daily billing with daily statements. For example, active read-write Shard configured on April 15 appears in the bill of April 16.
- Additional charges: Billed per minute, rounded up if less than one minute. Deducted hourly, with charges applied and bills generated at the top of the hour (Beijing Time). Billing occurs within one hour after the end of the current cycle. For instance, charges for 10:00-11:00 would be billed before 12:00, based on the system's billing time.
- Ensure the account is debt-free before using the service.
Charging standards
Log service billing pricing
Log service charge items are classified into pricing and free credit quota. For specific charging standards, refer to: Log Service Billing.
Charge
The log write traffic and log storage space compression ratio are about 25%, subject to the actual compressed data of users
| Charge item | Charge | Billing formula | Price | Free credit quota |
|---|---|---|---|---|
| Log write traffic (compressed) | Billing is based on compressed log data volume. For example, 10 GB raw data generates 1.5 GB (compression rate of 15%) write traffic when uploaded to log service. | Write traffic (compressed) × unit-price per GB | $0.045/GB | 500 M/month |
| Index traffic | Index traffic is calculated based on the volume of index data generated when the logs (uncompressed) are built. Note: (1) Index traffic will only be generated after indexing is enabled. (2) If both full-text indexing and key-value indexing are enabled, index traffic will not be calculated repeatedly. Full-text indexing (i.e., the size of the complete log) will be used as the basis for index traffic calculation. When only key-value indexing is enabled, index traffic correlates with the number of indexed fields and their value sizes. For example, if original log data is 4GB and the fields with key-value indexing enabled and their values total 2GB, the corresponding index traffic is 2GB. Reasonable configuration of key-value index fields can reduce product use cost. | Indexing traffic × unit-price per GB | $0.0875/GB | 500 M/month |
| Log delivery traffic | The traffic-based billing for log delivery to BOS according to logs (uncompressed) | Delivery traffic × unit price per GB | RMB 0.05/GB | None |
| Standard storage space for log (compressed) | Billing is based on the standard storage space of the user's compressed log data volume. For example, if the original log data volume is 10 GB and the compressed log data volume is 1.5 GB (compression rate of 15%), the corresponding log storage volume is 1.5 GB | Standard log storage (compressed) × unit-price per GB × storage duration | $0.002875/GB/day | 500 M/month |
| Infrequent access storage space for log (compressed) | Billing is based on the infrequent access storage space of the user's compressed log data volume. For example, if the original log data volume is 10 GB and the compressed write traffic is 1.5 GB (compression rate of 15%), the corresponding log storage volume is 1.5 GB | Infrequent access storage for log (compressed) × unit-price per GB × storage duration | $0.007353/GB/day | None |
| Standard storage space for indexing | Billing is based on the standard storage space occupied by the index when the logs (uncompressed) are built | Standard storage for index × unit--price per GB × storage duration | $ 0.002875/GB/day | 500 M/month |
| Index infrequent access storage space | Billing is based on the infrequent access storage space occupied by the index when the logs (uncompressed) are built | Infrequent access storage for index × unit--price per GB × storage duration | $0.000762/GB/day | None |
| Read-write shard | Count of active read-write shards used by users | Read-write shard count × unit-price of daily read-write shard | $0.01/unit/day | 31 * days/region/month |
| SMS count | SMS count used for log alarms | SMS count × SMS unit-price | RMB $0.0068/SMS | 500 SMS/region/month |
| Speech count | Speech count used for log alarms | Speech count × speech unit-price | $0.02206/SMS | None |
Insufficient balance reminders and debt handling
Insufficient balance reminder
- The system checks if your account balance (including available coupons) is enough to cover the next three days' costs based on your bill amount from the past three days. If the balance is insufficient, a renewal reminder will be sent.
- The system checks if your account balance (including available coupons) is enough to cover the next day's costs based on your bill amount from the past day. If the balance is insufficient, a renewal reminder will be sent.
Debt handling
- At the start of every hour, Beijing Time, the system checks if your account balance can cover the current BLS bill (e.g., at 11:00 Beijing Time, it checks if the balance is enough to pay the bill from 10:00 to 11:00). If not, it results in a debt, and a debt notification will be sent.
- If a debt occurs, services will be suspended immediately, and a service suspension notice due to debt will be sent. After suspension, all data read/write operations will be disabled, but LogStore data will be preserved for 7 days at a certain cost. If no recharge is made within 7 days, all data will be deleted. The system will send a release notice one day before and at the time of release.