Learn about billing modes and pricing for mPaaS components.
Billing mode
Individual mPaaS products
mPaaS products are billed based on usage. Multiple billing modes are available:
-
Free: Some components are free after activation. Usage thresholds and limits apply.
-
Prepaid: Supports resource packages and annual subscriptions. Reserve resources in advance at discounted rates.
-
Postpaid: Billed based on tiered usage at the end of each billing cycle. Default mode after service activation.
The following table lists the billing modes supported by each mPaaS component.
|
Component |
Prepaid mode |
Postpaid mode |
|
Version Upgrade |
Resource Package |
Not supported |
|
Mobile Gateway Service |
Resource Package |
Not supported |
|
Data Sync Service |
Resource Package |
Not supported |
|
Message Push Service |
Resource Package |
Not supported |
|
Basic Analysis |
Resource Package |
Not supported |
|
Custom Analysis |
Resource Package |
Not supported |
|
Performance Analysis |
Resource Package |
Not supported |
|
Mobile Security Armor |
Annual/Monthly Subscription |
Not supported |
|
Mini Program |
Integration is free. Mini Program release and analysis are billed based on mPaaS kernel, Mobile Gateway Service, H5 offline package devices, basic analysis devices, custom analysis devices, and performance monitoring devices. |
|
|
H5 Container and Offline Package |
Integration is free. The offline package release feature is billed by the number of H5 offline package devices. |
|
|
Frontend Framework and UI Component |
Free of charge |
|
|
Social Sharing |
Free of charge |
|
|
Device ID |
Free of charge |
|
|
Code Scanner |
Integration is free. The Code Scanner collects logs (scan counts, success/failure rates) for performance monitoring via the billable Mobile Analysis Service. Log reporting is enabled by default. Disable it in Log reporting. |
|
|
Datacenter |
Free of charge |
|
|
Location Based Service |
Free. Provides an endpoint for the Amap location service. Amap charges separately per Amap Open Platform Pricing. |
|
For mPaaS package
Mini Program package overview
The mPaaS Mini Program Package bundles core mobile platform services at discounted rates for SMEs and startups. Purchase a Mini Program package.
|
Mini Program Package (MAU: 10,000 - 100,000) |
|
|
Product feature |
Specification dimension |
|
Mini Program Release |
Custom App MAUs |
|
Basic Analysis |
Custom App MAUs |
|
Custom Analysis |
Custom App MAUs |
|
Performance Monitoring |
Custom App MAUs |
|
Mobile Gateway Service |
20 million calls/month |
|
mPaaS kernel |
Annual |
Purchase rules
-
Resource packages and bundled packages come in multiple specifications with tiered discounts.
-
Packages and resource packages take effect the next day (T+1) after purchase.
Billing rules
-
MAU definition: The number of unique monthly active terminal devices per App, used as the billable metric. If you have multiple Apps, device counts are aggregated across all Apps.
A device with multiple API calls in a statistical period counts as one device.
Calculated daily. On the first day of each month, the device count resets to zero.
-
In Mini Program package mode, usage exceeding the quota is billed on a postpaid basis:
Overage fee = Number of excess component devices × USD 0.03 per device.
Mobile Gateway Service overage is calculated separately: excess calls × USD 0.15 per 10,000 calls.
-
In resource package mode, usage exceeding the quota is billed on a postpaid basis:
For components other than Mobile Gateway Service, the overage fee = Number of excess devices × USD 0.03 per device.
For the Mobile Gateway Service component, the overage fee = Number of excess calls × USD 0.15 per 10,000 calls.
-
You can use packages and resource packages together. Package quota is consumed first, then resource package quota. Excess usage beyond both quotas is billed on a postpaid basis.
Overage fee for non-gateway components = Number of excess component devices × USD 0.03 per device.
Overage fee for the Mobile Gateway Service component = Number of excess calls × USD 0.15 per 10,000 calls.
-
In postpaid mode, tiered pricing applies based on usage. On the first day of each month, usage resets to zero for the new billing cycle.
mPaaS provides a free usage tier that is consumed first during billing.
Billing examples
-
A user purchases a Mobile Gateway resource package (10 million calls) for USD 60. By month-end, total usage reaches 13 million calls. The first 10 million are covered by the package. Overage: 3 million calls = 300 × 0.15 = USD 45.
-
A user purchases a one-year mPaaS Mini Program package for USD 55,440. During the year, Mobile Gateway usage exceeds the quota by 5 million calls. Overage: 500 × 0.15 = USD 75.
Billing cycle
-
Prepaid: The billing cycle matches the purchased service duration. Resource packages are valid for one year and remain active until expiration or full consumption.
-
Postpaid: Billed daily. Bills are generated within three days (T+3).
-
Package and resource package bills: Billed based on deduplicated monthly active terminal devices per App. Bills include resource package details and any postpaid overage. For tenants with multiple Apps, the bill may list only one App name for reference without affecting total accuracy.
Service price
Payment arrears
A bill is generated after each billing cycle. View your bill in the Personal Center in the console. Pay promptly to avoid service suspension.
Changes to billing mode for mobile development components
-
Mobile Delivery Service: Release Update API and Package Download Traffic replaced by Number of Version Release Devices and Number of H5 Offline Package Devices.
-
Mobile Analysis Service: Event tracking log reporting traffic, Historical log storage, and Diagnostic log pull count replaced by Number of devices for basic analysis, Number of devices for custom analysis, and Number of devices for App performance analysis.
-
Message Push Service: Number of pushed messages changed to Number of devices for message push.
-
Data Sync Service: Number of synchronized messages changed to Number of devices for data synchronization.
-
Mobile Gateway Service: billing item remains Number of API calls.
Billing item mapping:
|
Product feature |
Old billing item |
New billing item |
Feature description |
Functions |
|
Mobile Delivery Service |
|
Number of devices for version release |
Enables client app version upgrades with multitasking and multi-dimensional configurations. Console path: Mobile Delivery Service > Release Management. |
Functions or SDKs related to App version upgrades, along with Android/iOS configuration management, Whitelist management, and Release rule management. |
|
Number of devices for H5 offline package |
Bundles static resources (HTML, JS, CSS) into compressed packages for local loading, reducing network dependency for H5 pages. Console path: Mobile Delivery Service > Offline Package Management. For more information, see Offline Package overview. |
Functions and SDKs related to offline packages, along with Android/iOS configuration management, Whitelist management, and Publishing rule management. |
||
|
Mobile Analysis Service |
|
Number of devices for basic analysis |
Includes behavior analysis, retention analysis, page analysis, device analysis, page configuration, and metric calculation rules. Console path: Data Analysis > Mobile Analysis Service > Basic Analysis. For more information, see Basic analysis. |
Introduction to data overview, Behavior analysis, Retention analysis, Page analysis, Device analysis, Component usage analysis, Log management. |
|
Number of devices for custom analysis |
Multi-dimensional, real-time OLAP analysis of client-side custom events based on mPaaS instrumentation. Supports generating and saving reports with custom query conditions. Console path: Data Analysis > Mobile Analysis Service > Custom Analysis. For more information, see About custom analysis. |
Custom dashboard, Segment management, Event analysis, Funnel analysis, Trail analysis, Configure properties, Log management. |
||
|
Number of devices for App performance Analysis |
Includes crash, stutter, and freeze reports, plus iOS symbol table management. Console path: Data Analysis > Mobile Analysis Service > Performance Analysis. For a description of this feature, see Performance analysis. |
Crash reports, Lag report, Freeze reports, iOS symbol file management, Log management. |
||
|
Message Push Service |
Number of pushed messages |
Number of devices for message push |
Sends push messages via self-built or third-party channels, supporting console-based and API-based delivery. Console path: Operating > Message Push Service. For more information, see Message Push Service overview. |
|
|
Mobile Sync Service |
Number of synchronized messages |
Number of devices for data synchronization |
Provides a secure TCP/SSL data channel for proactive server-to-client data synchronization. Console path: Backgroud Connections > Mobile Sync Service. For more information, see Mobile Sync Service overview. |
|
|
Mobile Gateway Service |
Number of API calls |
Number of API calls |
Simplifies client-server data and communication protocols, improving development efficiency and network performance. Console path: Backgroud Connections > Mobile Gateway Service. For more information, see Mobile Gateway Service overview. |
For information about the prices of old mPaaS component billing items, see Legacy mPaaS component pricing. This information is for existing customers only.