Comparison Item | Pay-as-You-Go |
Billing method | Postpaid: Billed hourly. Pay after usage. Settlement cycle: Upon activation, one hour's fee will be frozen in your cloud account. At the top of every hour (UTC+8), the fee for the previous hour will be settled automatically. Product Pricing: Tiered pricing based on usage duration, with hourly rates decreasing tier by tier. For specific pricing, see Product Pricing. If the duration is greater than 0 days and less than or equal to 4 days, the first-tier pay-as-you-go pricing applies. If the duration is greater than 4 days and less than or equal to 15 days, the second-tier pay-as-you-go pricing applies. If the duration is greater than 15 days, the third-tier pay-as-you-go pricing applies. Note: After instance scale-out, scale-in, or isolation, the pricing calculation restarts from Tier 1. The price of pay-as-you-go tier 3 is basically the same as that of yearly/monthly subscription. |
Key rules | Termination: Instances can be terminated at any time, with fees settled per second based on usage. Payment overdue: When the account balance is insufficient, instances will be released after the grace/retention period is exceeded. For specific overdue handling mechanisms, see Payment Overdue Policy. |
Key strength | Highly flexible, with on-demand resource purchase and release to adapt to business fluctuations. |
Applicable Scenario | Business with significant traffic fluctuation and temporary needs (such as development and testing and promotional campaigns). |
Billing Items | Description |
Billable Item | Billing is based on instance specifications (CPU and memory configurations) and storage capacity, encompassing the consolidated costs of the following core resources. Core component: Mongod node's CPU and memory resources, which handle core features such as data storage, query processing, and transaction execution. Extension component (for sharded clusters only): Mongos routing node's CPU and memory resources, which handle cross-shard request scheduling, load balancing, and query optimization. Storage resources refer to the dedicated disk capacity used by Mongod nodes for persistent storage of documents, indexes, and metadata. Due to variations in infrastructure costs (such as the power supply, network bandwidth, and data center Ops) and local market policies across different regions, the storage unit price is independently set for each region. For price details, see Product Pricing. |
Pricing Description | Tiered pricing: Node prices are reduced as node capacity increases. For specific pricing, see Product Pricing. Architectural differences: Replica sets and sharded clusters adopt different specification tiers and pricing standards due to variations in performance, features, and complexity. Replica sets are divided into 4 specification tiers: less than 128 GB, equal to 128 GB, equal to 240 GB, and equal to 512 GB. Sharded clusters are divided into 2 specification tiers: less than 512 GB and equal to 512 GB. Different regions implement independent pricing tables based on infrastructure cost variations. Free tier (Mongos nodes): Mongos routing nodes provide a free tier (3 nodes for single-AZ, 6 nodes for multi-AZ), with additional nodes charged separately. |
Calculation Formula | For purchasing replica set instances or sharded cluster instances, see Billing Formula for fee calculation. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback