This topic describes the billing mode and pricing for mPaaS products.
Billing mode
For single product of mPaaS
mPaaS products are billed based on usage. Multiple billing mode are available:
Free: Some components are free to use after activation. Note that usage thresholds and limits apply.
Prepaid: This is a prepaid billing mode that supports resource packages and annual subscriptions. You can reserve resources in advance and receive greater discounts to maximize your savings.
Postpaid: This is a post-paid billing mode where you are billed based on tiered usage at the end of a billing cycle. This is the default billing mode after you activate a service.
The following table shows the billing mode 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 | Integrating the Mini Program component is free of charge. However, when you use Mini Program release and Mini Program analysis, they are billed based on the mPaaS kernel, Mobile Gateway Service, H5 offline packages devices, basic analysis devices, custom analysis devices and performance monitoring devices. | |
H5 Container and Offline Package | Integrating the H5 Container and Offline Package components is free of charge. However, when you use the offline package release feature, it is billed based on the number of devices for H5 offline packages. | |
Frontend Framework and UI Component | Free of charge | |
Social Sharing | Free of charge | |
Device ID | Free of charge | |
Code Scanner | Integrating the Code Scanner component is free of charge. However, when you use the Code Scanner component, logs are collected to obtain information such as the number of scans, successful scans, and failed scans to monitor and analyze performance. The log collection process relies on the billable Mobile Analysis Service and therefore incurs fees. Log event tracking for the Code Scanner component is configured during the initial setup, and log reporting is enabled by default. To disable it, see Log reporting. | |
Datacenter | Free of charge | |
Location Based Service | Using the Location Based Service is free of charge. The service provides an endpoint for the Amap location service. For more information about Amap's billing, see Amap Open Platform Pricing. | |
For mPaaS package
Mini Program package overview
The mPaaS Mini Program Package prioritizes the core services of the mobile development platform and provides more favorable and convenient customized solutions for small and medium-sized enterprises (SMEs) and startups. For more information, see 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 packages are available in multiple specifications, with discounts varying by specification.
Packages and resource packages will take effect the next day (T+1) after purchase.
Billing rules
Definition of MAUs: Monthly active devices are defined as the number of unique terminal devices for an App, which is a billable item. The system calculates the number of unique monthly active devices for each App. If you have multiple Apps under your account, the counts for each App are aggregated.
A device that calls an API multiple times during a statistical period is counted as one device.
This billable item is calculated daily. On the first day of each month, the system resets the device count to zero and begins recounting.
In the Mini Program package mode, usage that exceeds the quota is billed on a postpaid basis:
Overage fee = Number of excess component devices × USD 0.03 per device.
If the Mobile Gateway Service component usage exceeds the quota, the overage fee is calculated separately. Mobile Gateway Service overage fee = Number of excess calls × USD 0.15 per 10,000 calls.
In the resource package mode, usage that exceeds 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 purchase and use packages and resource packages at the same time. When billing, the package quota is consumed first, followed by the resource package quota. If both quotas are exhausted, any excess usage 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, a tiered pricing mode is used based on the usage of billable items. On the first day of each month, the system resets the usage to zero and begins recounting for the new tiered billing mode.
mPaaS provides a certain amount of free usage, which constitutes the first pricing tier. This free usage is consumed first during billing.
Billing examples
A user spends USD 60 at the beginning of the month to purchase a resource package for the mPaaS Mobile Gateway service that includes 10 million calls. By the end of the month, the user has made a total of 13 million Mobile Gateway calls. The first 10 million calls are covered by the resource package. The remaining 3 million calls are considered overage. The overage fee is 300 × 0.15 = USD 45.
A user spends USD 55,440 to purchase a one-year mPaaS Mini Program package. During the year, the user exceeds the Mobile Gateway call quota by 5 million calls. The overage fee is 500 × 0.15 = USD 75.
Billing cycle
Prepaid: For packages and annual/monthly subscriptions, the billing cycle corresponds to the purchased service duration. For resource packages, the validity period is one year. After you purchase a resource package, the corresponding service is available until the package expires or is fully consumed.
Postpaid: The billing cycle is daily. Bills for the previous day's usage are typically generated within three days (T+3).
Bills for packages and resource packages: Packages and some component products are billed based on the number of deduplicated monthly active terminal devices for a single App. The bill shows the billing details for the resource package and any postpaid overage. If a tenant has multiple Apps, the bill may list only one App name for reference, but this does not affect the accuracy of the total bill.
Service price
Payment arrears
After each billing cycle, a bill is generated. You can view your current bill in the Personal Center in the console. To prevent service suspension, please pay the bill as soon as possible.
Changes to billing mode for mobile development components
The two billing items related to the Mobile Delivery Service feature, Release Update API and Package Download Traffic, have been changed to Number of Version Release Devices and Number of H5 Offline Package Devices based on business scenarios. Users can purchase these items based on actual business needs.
The three billing items related to the Mobile Analysis Service feature, Event tracking log reporting traffic, Historical log storage, and Diagnostic log pull count, have been replaced by three business-scenario-based billing items: Number of devices for basic analysis, Number of devices for custom analysis, and Number of devices for App performance analysis. You can purchase them based on your business needs.
The billing item related to the Message Push Service feature, Number of pushed messages, has been changed to Number of devices for message push.
The billing item related to the Data Sync Service feature, Number of synchronized messages, has been changed to Number of devices for data synchronization.
The billing item related to the Mobile Gateway Service feature 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 | Allows clients to upgrade to new versions. You can create multitasking and multi-dimensional upgrade configurations. This corresponds to the Mobile Delivery Service > Release Management page in the console. For more information, see Android 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 | An offline package bundles static resources such as HTML, JavaScript, and CSS files into a compressed package. The client pre-downloads the offline package and loads it locally. This minimizes the impact of network conditions on H5 pages. This corresponds to the Mobile Delivery Service > Offline Package Management page in the console. For more information, see Offline Package overview. | Functions and SDKs related to offline packages, along with Manage configurations for Android/iOS, Manage whitelists, and Manage release rules. | ||
Mobile Analysis Service |
| Number of devices for basic analysis | The Basic Analysis feature mainly includes behavior analysis, retention analysis, page analysis, device analysis, page configuration, and metric calculation rules. This corresponds to the Data Analysis > Mobile Analysis Service > Basic Analysis page in the console. 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 | Custom Analysis performs multi-dimensional, real-time custom analysis of client-side custom events using online analytical processing (OLAP) based on mPaaS custom instrumentation. This meets the unique requirements of different cloud businesses. You can also generate and save different reports on the frontend based on different query conditions and scenarios. This corresponds to the Data Analysis > Mobile Analysis Service > Custom Analysis page in the console. For more information, see About custom analysis. | Custom dashboard, User group management, Event analysis, Funnel analysis, Trajectory analysis, Configure attributes, Log management. | ||
Number of devices for App performance Analysis | App Performance Analysis mainly includes crash reports, stuttering reports, freeze reports, and iOS symbol table management. This corresponds to the Data Analysis > Mobile Analysis Service > Performance Analysis page in the console. For a description of this feature, see Performance analysis. | Crash report, Lag report, Stuck report, iOS symbol table management, Log management. | ||
Message Push Service | Number of pushed messages | Number of devices for message push | You can use Message Push Service (MPS) to send various types of push messages. Supported push channels include self-built channels and third-party channels. Supported push mode include console-based pushes and API-based pushes. Select the appropriate push type, channel, and method based on your business scenario. This corresponds to the Operating > Message Push Service page in the console. For more information, see About Message Push Service. | |
Mobile Sync Service | Number of synchronized messages | Number of devices for data synchronization | Provides a secure data channel based on Transmission Control Protocol (TCP) and Secure Sockets Layer (SSL). It can proactively synchronize business data from the server to the client App in a timely, accurate, and orderly manner. This corresponds to the Backgroud Connections > Mobile Sync Service page in the console. For more information, see About Mobile Sync Service. | |
Mobile Gateway Service | Number of API calls | Number of API calls | Simplifies the data and communication protocols between the mobile client and the server. This significantly improves development efficiency and network communication performance. This corresponds to the Backgroud Connections > Mobile Gateway Service page in the console. For more information, see About Mobile Gateway Service. |
For information about the prices of old mPaaS component billing items, see Pricing details for legacy mPaaS billable items. This information is for existing customers only.