Enterprise instances (subscription)
IoT Platform Enterprise instances use the subscription billing method. The purchase price covers the total cost. You are not charged extra on a pay-as-you-go basis for usage, such as message communications or device connection duration.
The following information is for reference only. The actual fees are specified on your bill.
On the IoT Platform instance purchase page, you can select the specifications to view the Configuration Fee. For more information, see Purchase an Enterprise instance.
Region limits
Enterprise instances can be activated in all regions supported by the IoT Platform console: China (Shanghai), China (Beijing), China (Shenzhen), Japan (Tokyo), Singapore, Germany (Frankfurt), US (Silicon Valley), and US (Virginia).
Billable items
Billable item | Description | Notes |
Type | Supports Standard and Premium types. | The instance type itself is not billable. Billing is based on the resource specifications that you select for the instance. The unit price of resources varies by instance type. For more information, see Differences between Enterprise instance types and features. |
Availability | Supports Standard (99.95% Service-Level Agreement (SLA)) and High Availability (99.99% SLA). |
|
Concurrent online devices | This is the maximum number of devices that can be online at the same time in an instance. The number of devices that you can create is 10 times the selected specification. The available specifications are displayed on the purchase page. | After you purchase an instance, you are not charged extra for the selected specifications during the validity period. |
Uplink and downlink message TPS | The total uplink and downlink Transactions Per Second (TPS) for messages between devices and IoT Platform. This is independent of message size. The available specifications are displayed on the purchase page. | |
Message forwarding TPS | The total TPS for server-side subscriptions and data forwarding for messages between IoT Platform and your server-side. This is independent of message size. The available specifications are displayed on the purchase page. | |
Time series data storage IOPS | This is the total number of rows written and read per second. By default, the limit is based on a ratio of 90% writes and 10% reads. For example, if the input/output operations per second (IOPS) is 1,000, the maximum write IOPS is 900 and the maximum read IOPS is 100. You can select an IOPS value from 100 to 1,000,000. A free quota of 100 time series storage IOPS is provided. For pricing and usage details, see the "Time series data storage IOPS" section below. For more information about time series storage, see Overview of time series data storage. | This feature is available only for Standard and Premium instances. |
Time series data storage space | This is used to write and read time series data reported by devices. You can select a storage space from 1 GB to 200,000 GB. A free quota of 1 GB is provided. For pricing and usage details, see the "Time series data storage space" section below. | |
Offline data storage space | This is used to back up and analyze historical data reported by devices. You can select a storage space from 10 GB to 200,000 GB. A free quota of 10 GB is provided. For more information about offline storage, see Overview of offline storage. For pricing and usage details, see the "Offline data storage space" section below. | This feature is available only for Standard and Premium instances in the China (Shanghai), China (Beijing), China (Shenzhen), Singapore, and US (Virginia) regions. |
Data processing unit | DataService Studio and Operations and Maintenance (O&M) statistics services consume data processing units (CUs). You can select from 1 to 10,000 CUs. A free quota of 1 CU is provided. For pricing and usage details, see the "Data processing unit" section below. | |
OTA feature |
When you initiate a device OTA update, IoT Platform pre-deducts the number of updates based on the assumption that all specified devices will be successfully updated. The corresponding number of updates is consumed after a device is successfully updated. If a device fails to update (for example, the OTA task fails or is canceled), the pre-deducted updates are returned. |
|
Link WAN | This service is supported and enabled by default only for Premium instances in the China (Shanghai) region. For more information, see the Alibaba Cloud Link WAN documentation. | The Alibaba Cloud Link WAN service is provided free of charge only for Premium instances in the China (Shanghai) region. |
The pricing and consumption rules for data processing units (CUs), time series data storage IOPS, time series data storage space, and offline data storage space are described in the following sections.
Resource consumption for each feature is measured in real time. Your total consumption cannot exceed your purchased specifications. Make sure to purchase sufficient resource specifications for your business needs.
Data processing unit
The following features are billed at the same unit price (CNY/unit/month).
Pricing:
Region | Billing (CNY/unit/month) |
China (Shanghai), China (Beijing), China (Shenzhen) | 50 |
Singapore, US (Virginia) | 100 |
CU consumption is measured to one decimal place. The CU consumption rules for each feature are as follows:
DataService Studio
The total CU consumption is the sum of the CUs consumed by the following features.
The CU consumption rules for each feature are as follows:
The unit CU consumption, computational complexity coefficient, and data volume coefficient for the following features are defined in the following table:
CU consumption formula:
CU Consumption = Unit Feature CU Consumption × Computational Complexity Coefficient × Data Volume Coefficient.Feature
Unit feature CU consumption
Computational complexity coefficient definition (minimum 1)
Data volume coefficient definition (minimum 1)
Feature document
Back up products
0.1
Number of backed up products × 1. Minimum value: 1.
CEILING(Maximum data volume of a backup job during the instance lifecycle / 10 GB). Minimum value: 1.
Back up IoT Twin Engine data source
0.1
Number of backed up twin spaces × 1. Minimum value: 1.
CEILING(Maximum data volume of a backup job during the instance lifecycle / 10 GB). Minimum value: 1.
Cloud product data source integration
0.5
Fixed at 1.
For tasks with a daily sync period: CEILING(Data volume integrated / 5 GB). Minimum value: 1.
1
Fixed at 1.
For tasks with an hourly sync period: CEILING(Data volume integrated / 5 GB). Minimum value: 1.
Flink real-time data integration
0.1
Fixed at 1.
CEILING(Outbound data volume for integration / 1 GB). Minimum value: 1.
DataWorks batch data integration
0.3
Fixed at 1.
CEILING(Outbound data volume for integration / 10 GB). Minimum value: 1.
Derived metrics
0.5
0.5 × Number of expressions. Minimum coefficient: 1. Maximum coefficient: 5.
CEILING(Maximum data volume of a single task during the instance lifecycle / 10 GB). Minimum value: 1.
Data parsing
1
Filter and transform operators: CEILING(Number of operators / 10). Maximum value: 3.
Neighboring message calculation and conditional transform: Number of operators × 1.5.
Window aggregation and timeout interpolation: Number of operators × 2.
The minimum coefficient is 1.
CEILING(Message TPS / 50). Minimum value: 1.
SQL analysis (daily scheduling)
0.5
CEILING(Number of SQL keywords / 5). Maximum value: 10.
NoteNumber of SQL keywords = Number of JOINs + Number of GROUP BYs + Number of ORDER BYs + Number of DISTINCTs + Number of window functions + MAX(Number of INSERTs, UPDATEs, DELETEs, SELECTs)
CEILING(Maximum data volume of a single task during the instance lifecycle / 10 GB). Minimum value: 1.
SQL analysis (hourly scheduling)
2
If you enable statistics for preset metric tables in DataService Studio, CUs are consumed based on the number of activated devices for each metric table.
For more information about enabling statistics for preset metric tables, see Manage preset metric tables. The billing details for the related preset metric tables are as follows.
Type
Preset metric table name
Tier by number of activated devices
CUs consumed
Device statistics
Ranking of device network protocol distribution on any given day
Ranking of device SDK version distribution to date
Ranking of device network protocol distribution to date
Ranking of device province/region distribution to date
Ranking of device category distribution on any given day
Ranking of device category distribution to date
Ranking of device region distribution on any given day
Daily device count statistics for any time period
Device count statistics to date
Ranking of device SDK version distribution on any given day
Ranking of device network connection method distribution to date
Ranking of device network connection method distribution on any given day
0 to 5,000
0.25
5,001 to 20,000
0.5
20,001 to 50,000
1
50,001 to 100,000
1.5
If the number of activated devices is greater than 100,000, a new tier is created for every 100,000 devices:
n = Number of activated devices / 100,000.1.5 × n
Operating condition statistics
Daily device online duration statistics for any time period
Daily device connection count statistics for any time period
Daily device uplink and downlink message statistics for any time period
0 to 5,000
0.5
5,001 to 20,000
1
20,001 to 50,000
1.5
50,001 to 100,000
2
If the number of activated devices is greater than 100,000, a new tier is created for every 100,000 devices:
n = Number of activated devices / 100,000.2 × n
Event statistics
Daily statistics on events reported by devices for any time period
0 to 5,000
0.5
5,001 to 20,000
1
20,001 to 50,000
1.5
50,001 to 100,000
2
If the number of activated devices is greater than 100,000, a new tier is created for every 100,000 devices:
n = Number of activated devices / 100,000.2 × n
ImportantIf the result of the division is not an integer, round it up.
O&M statistics
Enabling the device, operating condition, and event statistics services under O&M statistics consumes CUs. The consumption rules are as follows:
Tier by number of activated devices | CUs consumed by device statistics | CUs consumed by operating condition statistics | CUs consumed by event statistics |
0 to 5,000 | 0.5 | 1 | 1 |
5,001 to 20,000 | 1 | 2 | 2 |
20,001 to 50,000 | 2 | 3 | 3 |
50,001 to 100,000 | 3 | 4 | 4 |
If the number of activated devices is greater than 100,000, a new tier is created for every 100,000 devices: Important If the result of the division is not an integer, round it up. | 3 × n | 4 × n | 4 × n |
Device diagnostics
Enabling the diagnostic metrics, smart baseline, batch analytics, and diagnostic analysis services under Device Diagnostics consumes CUs. The consumption rules are as follows:
Tier by number of activated devices | CUs consumed by diagnostic metrics | CUs consumed by smart baseline | CUs consumed by batch analytics | CUs consumed by diagnostic analysis |
0 to 5,000 | 0.5 | 1 × Number of smart baselines | 1 | 1 |
5,001 to 20,000 | 2 | 3 × Number of smart baselines | 3 | 3 |
20,001 to 50,000 | 5 | 7 × Number of smart baselines | 7 | 7 |
50,001 to 100,000 | 10 | 14 × Number of smart baselines | 14 | 14 |
If the number of activated devices is greater than 100,000, a new tier is created for every 100,000 devices: Important If the result of the division is not an integer, round it up. | 12 × n | 16 × n | 16 × n | 16 × n |
Time series data storage IOPS
DataService Studio uses time series storage IOPS to write and read device time series data.
Pricing:
Region | Billing (CNY/1,000 IOPS/month) |
China (Shanghai), China (Beijing), China (Shenzhen) | 55 |
Japan (Tokyo), Singapore, Germany (Frankfurt), US (Silicon Valley), US (Virginia) | 110 |
Time series data storage space
DataService Studio uses time series storage space to back up and store data from Thing Specification Language (TSL) models (properties, services, and events) reported by devices and data from custom topics configured through time series storage rules.
Pricing:
Region | Billing (CNY/GB/month) |
China (Shanghai), China (Beijing), China (Shenzhen) | 0.5 |
Japan (Tokyo), Singapore, Germany (Frankfurt), US (Silicon Valley), US (Virginia) | 1 |
Offline data storage space
DataService Studio uses offline storage space to back up and store device data assets.
Pricing:
Region | Billing (CNY/GB/month) |
China (Shanghai), China (Beijing), China (Shenzhen) | 0.2 |
Singapore, US (Virginia) | 0.4 |
Billing cycle
The billing cycle for a subscription resource is the same as the purchase period of the order, in UTC+8. A billing cycle starts at the exact second a resource is activated or renewed and ends at 00:00:00 on the day after its expiration date.
Yearly and monthly subscription billing cycles are based on calendar years and calendar months.
Billing formula
Final price = Total price of billable items per instance × Number of instances × Subscription duration.
The number of instances that you can purchase for each Alibaba Cloud account is limited. The specific limit is displayed on the purchase page.
Overdue payments and renewal policy
For more information, see Overdue payments and renewals.
Upgrade and downgrade instructions
After you purchase an instance, you can upgrade or downgrade its configuration as needed.
When you upgrade or downgrade an instance, you cannot change the subscription duration. The remaining service duration of the instance does not change.
Upgrade
When you upgrade an instance, you must pay the price difference.
The price difference is calculated as follows: (Daily price of the instance after the upgrade - Daily price of the instance before the upgrade) × Remaining days until the instance expires.
On the Instance Overview tab of the IoT Platform console, click the edit
icon in the upper-right corner of the instance card.Click Upgrade.
Select the new instance specifications and complete the purchase.
For more information about the specifications, see Specifications.
Downgrade
When you downgrade an instance, you receive a refund for the disabled or downgraded features.
The refund is calculated as follows: (Daily price of the instance before the downgrade - Daily price of the instance after the downgrade) × Remaining days until the instance expires.
On the Instance Overview tab of the IoT Platform console, click the edit
icon in the upper-right corner of the instance card.Click Downgrade.
Select the new, lower instance specifications and complete the purchase.
The actual refund amount is the amount shown on the downgrade page.
Resource usage and bills
Log on to the IoT Platform console. In the top menu bar, choose .
In the navigation pane on the left, choose .
Refund policy
For an Enterprise Edition instance, if the purchased resources exceed your business requirements, you can submit a ticket to cancel the resource plan. For more information about the refund rules, see Refund policy.
References
To purchase an Enterprise instance that meets your business needs, see Purchase an Enterprise instance.
For the billing methods for device connection duration and message count of legacy public instances, see Public instances.
For the billing methods for resource specifications of Enterprise instances, see Enterprise instances.
FAQ
For answers to frequently asked questions about activating or using Enterprise Edition instances and public IoT Platform instances, see FAQ about IoT Platform instances.
For answers to frequently asked questions about billing for purchasing or trying an IoT Platform instance, see FAQ about IoT Platform billing.
For answers to frequently asked questions about billing for trial Alibaba Cloud products, see FAQ about trials.
For answers to frequently asked questions about payments for purchasing and renewing Alibaba Cloud products, see FAQ about payments.
For answers to frequently asked questions about topping up your Alibaba Cloud account, see FAQ about top-ups.