This topic describes the billing rules and pricing for Mobile PaaS products.
Billing models
Starting May 13, 2024, mPaaS components are billed on a per-component or per-plan basis.
Individual mPaaS product billing
mPaaS products are billed based on usage and offer the following billing models:
Free: Some components are free of charge. You can use them after activation. Be aware of the usage thresholds and limits.
Subscription: A prepaid billing model that lets you reserve resources in advance. This model offers significant discounts, helping you save on costs.
Pay-as-you-go: A postpaid billing model where you are billed for your usage at the end of each billing cycle. This is the default billing model after you activate a service.
The following table lists the billing models supported by each mPaaS component.
Component | Subscription model | Pay-as-you-go model |
Version Upgradation | Resource plan | Not supported |
Hotpatching | Resource plan | Not supported |
Mobile Gateway | Resource plan | Not supported |
Data Synchronization | Resource plan | Not supported |
Message Push | Resource plan | Not supported |
Basic Analysis | Resource plan | Not supported |
Custom Analysis | Resource plan | Not supported |
App Performance Analytics | Resource plan | Not supported |
Performance Monitoring | Resource plan | Not supported |
Intelligent Delivery | Resource plans | Support |
Ant Dynamic Card | Subscription | Not supported |
Mobile application security hardening | Subscription | Not supported |
mPaaS kernel | Subscription | Not supported |
Audio and video calls | Not supported | Support |
Mini Program | The Mini Program component is free to integrate. However, when you use the mini program publishing and mini program analysis features, you are billed for the mPaaS kernel, Mobile Gateway, H5 offline package devices, basic analysis devices, custom analysis devices, and performance monitoring devices. | |
H5 container and offline package | The H5 container and offline package components are free to integrate. However, when you use the offline package publishing feature, you are billed based on the number of H5 offline package devices. | |
Frontend framework and UI components | Not billed | |
Social sharing | Not billed | |
Device ID | Not billed | |
Scan | The Scan component is free to integrate. However, when you use the Scan component, logs are collected to obtain information such as the number of scans, successful scans, and failed scans to monitor and analyze scan performance. The log collection process relies on the billable mobile analytics service, which incurs fees. Log instrumentation for the Scan component is configured during the initial setup, and log reporting is enabled by default. To disable it, see Log reporting switch. | |
Unified storage | Not billed | |
Location | The Location service is free to use. The Location service provides an endpoint for the Amap Location service. For Amap billing details, see Amap Open Platform Pricing. | |
mPaaS plan sales
Subscription plan overview
mPaaS plans include key services from the Mobile PaaS platform. They offer affordable and convenient customized solutions for small and medium-sized enterprises (SMEs) and startups. For more information, see Purchase a subscription plan.
Basic Plan
Monthly Active User (MAU) range: 100 to 100,000.
Basic Edition: Suitable for apps in their early stages, with fewer than 100,000 MAUs, and for individual developers.
Standard Edition: Suitable for users with fewer than 100,000 MAUs and for individual developers.
Professional Edition: Suitable for users with fewer than 100,000 MAUs and for individual developers.
Subscription plan options
Plan type | Basic Plan (MAU: 100 - 100,000) | ||
Product feature | Basic Edition | Standard Edition | Professional Edition |
Version Upgradation | - | Custom App MAUs | Custom App MAUs |
H5 offline package | - | Custom App MAUs | Custom App MAUs |
Hotpatching | Custom App MAUs | Custom App MAUs | Custom App MAUs |
Mobile Gateway | 10 million calls/month | 50 million calls/month | 700 million calls/month |
Data Synchronization | - | - | Custom App MAUs |
Message Push | Custom App MAUs | Custom App MAUs | Custom App MAUs |
Basic Analysis | - | - | Custom App MAUs |
Custom Analysis | - | - | Custom App MAUs |
App Performance Analytics | - | Custom App MAUs | Custom App MAUs |
Performance Monitoring | - | - | Custom App MAUs |
Purchase rules
Resource plans and packages are available in multiple specifications. Discounts vary depending on the specifications you purchase.
You can purchase a plan only once before it expires. However, you can upgrade to a higher-tier plan during its validity period. The price difference for the upgrade is charged automatically.
Plans and resource plans take effect on the day after purchase (T+1).
Billing rules
Monthly active devices: A billable item that represents the number of unique terminal devices for an application. The system counts the unique monthly active devices for each application. If you have multiple applications under your account, their device counts are aggregated. A device that calls an API multiple times within a statistical period is counted as a single device. The device count is updated daily. On the first day of each month, the system resets the device count to zero and begins a new counting period.
For plans, usage that exceeds the quota is billed on a pay-as-you-go basis. The overage fee is calculated as follows: Number of overage component devices × CNY 0.1/device. However, overage for the Mobile Gateway component is calculated separately: Overage call volume × Pay-as-you-go unit price per call for Mobile Gateway.
For resource plans, usage that exceeds the quota is billed on a pay-as-you-go basis. For components other than Mobile Gateway, the overage fee is calculated as follows: Number of overage devices × CNY 0.1/device. For the Mobile Gateway component, the overage fee is calculated as follows: Overage call volume × Unit price per call for Mobile Gateway.
You can use plans and resource plans concurrently. Quotas are consumed in the following order: plan quota, then resource plan quota. Any usage exceeding both quotas is billed on a pay-as-you-go basis. For components other than Mobile Gateway, the overage fee is calculated as follows: Number of overage component devices × CNY 0.1/device. For the Mobile Gateway component, the overage fee is calculated as follows: Overage call volume × Unit price per call for Mobile Gateway.
The pay-as-you-go model uses tiered pricing. On the first day of each month, usage is reset to zero for the new billing cycle. mPaaS provides a free usage tier, which is always consumed first.
Billing examples
A customer purchases a resource plan for the mPaaS Mobile Gateway service for CNY 160, which includes 10 million calls. By the end of the month, their total call volume is 13 million. The first 10 million calls are covered by the resource plan. The remaining 3 million calls are billed as overage. The overage fee is 300 × CNY 0.2 = CNY 60.
A customer purchases a 6-month Standard Edition multi-component plan for mPaaS for CNY 13,452. During the subscription period, they exceed the Mobile Gateway call quota by 5 million calls. The overage fee is 500 × CNY 0.2 = CNY 100.
Billing cycle
Subscription: For subscription plans, the billing cycle corresponds to the purchased service duration. Resource plans are valid for one year. The resources in a resource plan can be used until the plan expires or the resources are fully consumed, whichever comes first.
Pay-as-you-go: This model uses a daily billing cycle. Bills are generated daily, but there may be a delay of up to three days (T+3) for charges to appear.
Plan and resource plan bills: Plans and some components are billed based on the number of unique monthly active devices for a single application. The bill displays details for the resource plan and any pay-as-you-go overage charges. If a tenant has multiple applications, the bill displays the details under a single, randomly selected application. This does not affect the accuracy of the total bill.
Service price details
Overdue payments
A bill is generated after each billing cycle. You can view your bills in the User Center of the console. To avoid service suspension, please pay your bills promptly.
Changes to billing models for mobile development components
The two billable items for the Real-time Release feature, Publish update API and Package download traffic, have been replaced with three billable items based on business scenarios: Version release devices, Hotpatching devices, and H5 offline package devices. You can purchase these items based on your business needs. For example, if you only need to hotpatch online issues without releasing a new version, you only need to purchase the Hotpatching devices item.
The three billable items for the Mobile Analytics feature, Instrumentation log reporting traffic, Historical log storage, and Diagnostic log pull count, have been replaced with three billable items based on business scenarios: Basic analysis devices, Custom analysis devices, and App Performance Analytics devices. You can purchase these items based on your business needs.
The billable item for the Message Push feature, Number of pushed messages, has been changed to Number of message push devices.
The billable item for the Data Synchronization feature, Number of synchronized messages, has been changed to Number of data synchronization devices.
The billable item for the Performance Monitoring feature remains Number of performance monitoring devices.
The billable item for the Mobile Gateway feature remains Number of API calls.
Billable item mapping:
Product feature | Old billable item | New billable item | Capabilities | Functional item |
Real-time Release | Publish update API Package download traffic | Version release devices | Lets clients upgrade to new versions. You can create multitasking and multi-dimensional upgrade configurations. This corresponds to the Real-time Release > Release Management page in the console. Feature overview: Android Release Management. | Features or SDKs related to app version upgradation, along with Android/iOS Configuration Management, HarmonyOS Configuration Management, Whitelist Management, and Release Rule Management. |
Hotpatching devices | Hotpatching is used to fix online issues without releasing a new version. This corresponds to the Real-time Release > Hotpatch Management page in the console. Feature overview: Hotpatching overview. | Features or SDKs for app hotpatching, along with Android/iOS Configuration Management, HarmonyOS Configuration Management, Whitelist Management, and Release Rule Management. | ||
H5 offline package devices | 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 then loads it locally. This minimizes the impact of network conditions on H5 pages. This corresponds to the Real-time Release > Offline Package Management page in the console. Feature overview: Offline package overview. | Features and SDKs for offline packages, along with Android/iOS Configuration Management, HarmonyOS Configuration Management, Whitelist Management, and Release Rule Management. | ||
Mobile Analytics | Instrumentation log reporting traffic Historical log storage Diagnostic log pull count | Device count 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 Analytics > Basic Analysis page in the console. Feature overview: Basic Analysis. | Data Overview, Behavior Analysis, Retention Analysis, Page Analysis, Device Analysis, Component Usage Analysis, Log Management. |
Device Count 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 special requirements of different cloud services. It also lets you generate and save different reports on the frontend based on different query conditions and scenarios. This corresponds to the Data Analysis > Mobile Analytics > Custom Analysis page in the console. Feature overview: About Custom Analysis. | Custom Dashboard, Group Management, Event Analysis, Funnel Analysis, Path Analysis, Configure Properties, Log Management. | ||
App Performance Analytics device count | App Performance Analytics mainly includes crash reports, stuttering reports, ANR reports, and iOS symbol table management. This corresponds to the Data Analysis > Mobile Analytics > App Performance Analytics page in the console. Feature overview: App Performance Analytics. | Crash Report, Stuttering Report, ANR Report, iOS Symbol Table Management, HarmonyOS NEXT Symbol Table Management, Log Management. | ||
Message Push | Number of pushed messages | Number of message push devices | You can use MPS to push various types of messages. Supported push channels include self-built channels and vendor channels. You can push messages from the console or using APIs. Choose the appropriate push type, channel, and method based on your business scenario. This corresponds to the Efficient Operation > Message Push page in the console. Feature overview: Message Push overview. | Data Overview, Message Management, Message Template, SMS Supplement Service. |
Data Synchronization | Number of synchronized messages | Number of data synchronization devices | Provides a secure data channel based on Transmission Control Protocol (TCP) and secure sockets layer (SSL) to actively sync business data from the server-side to the client app in a timely, accurate, and orderly manner. This corresponds to the Backend Service > Data Synchronization page in the console. Feature overview: Data Synchronization overview. | Add Configuration, Service Management, Query Data Synchronization Operation Records. |
Performance Monitoring | Number of performance monitoring devices | Number of performance monitoring devices | Performance Monitoring analysis covers five dimensions: network, application startup, page performance, H5 performance, and crash analysis. This corresponds to the Data Analysis > Performance Monitoring page in the console. Feature overview: Mobile Performance Monitoring overview. | Network Analysis, Startup Analysis, Page Performance, H5 Performance, Crash Analysis, Monitoring and Alerts. |
Mobile Gateway | Number of API calls | Number of API calls | Simplifies the data and communication protocols between the mobile client and the server, significantly improving development efficiency and network communication performance. This corresponds to the Backend Service > Mobile Gateway page in the console. Feature overview: Mobile Gateway overview. | API Management, API Group, Data Model, API Analysis, Gateway Management. |
For information about the pricing of previous mPaaS component billable items, see Pricing of old mPaaS component billable items. This information applies only to existing customers.