...
ClearBlade IoT Core is priced according to the data volume used in a calendar month:
Monthly data volume | Price per MB | Registered devices | Minimum charge* |
|---|---|---|---|
Up to 250 MB | $0.00 | Unlimited, within QPS maximums | 1024 bytes |
250 MB to 250 GB | $0.0045 | Unlimited, within QPS maximums | 1024 bytes |
250 GB to 5 TB | $0.0020 | Unlimited, within QPS maximums | 1024 bytes |
5 TB and above | $0.00045 | Unlimited, within QPS maximums | 1024 bytes |
Data volume is based on data exchanged by devices connected to ClearBlade IoT Core. There is no charge for create, read, update, and delete operations through the device manager.
...
Compressed HTTP requests
As noted in Using the HTTP bridge, a device can send gzip-compressed data to ClearBlade IoT Core over the HTTP bridge.
Billing for telemetry Telemetry event and device state payloads payload billing is calculated using the each request’s uncompressed size of each request.
For example, if a telemetry event payload was 256 KB before compression, and the compressed payload is 10 KB, you will be charged for the uncompressed 256 KB data, not the compressed size.
...
Say that you have 10,000 devices, each of which is connected to ClearBlade IoT Core over an MQTT connection. Even if the devices don't send telemetry events or state data over one month, they will still send PINGREQ messages to ClearBlade IoT Core to keep the MQTT connection alive. The PINGREQs’ frequency depends on each connection’s keep-alive value. Even though a PINGREQ may be only a few bytes, any messages smaller than 1024 bytes are still charged as they were 1024 bytes because it is the minimum data size used for billing.
...
Say that you have 10,000 devices connected to ClearBlade IoT Core. Each device sends one HTTP request every 30 minutes, and each request is 1024 bytes in size. Each HTTP request results in a response, and even though a response may be only a few bytes, the minimum billing 1024-byte size of 1024 bytes applies. Therefore, the total data volume in a month would be 27.46 GB, calculated as follows:
Requests
...
10,000 devices * 48 messages/device per day * 30 days * 1024 bytes = 13.73 GB
Responses
...
10,000 devices * 48 messages/device per day * 30 days * 1024 bytes = 13.73 GB
Total data volume
...
13.73 GB (Requests) + 13.73 GB (Responses) = 27.46 GB
...
Say that you have 50,000 devices connected to ClearBlade IoT Core. Each device sends one HTTP request every 30 minutes, and each request is 5 bytes in size. Any messages smaller than 1024 bytes are still charged as if they were 1024 bytes because 1024 bytes is the minimum data size used for billing. Each HTTP request results in a response, and even though a response may be only a few bytes, the same minimum 1024-byte size of 1024 bytes applies. The total data volume in a month would be 137.32 GB, calculated as follows:
Requests
...
50,000 devices * 48 messages/device per day * 30 days * 1024 bytes = 68.66 GB
Responses
...
50,000 devices * 48 messages/device per day * 30 days * 1024 bytes = 68.66 GB
Total data volume
...
68.66 GB(Requests) + 68.66 GB (Responses) = 137.32 GB
...
Consider a case where you have 50,000 devices connected to ClearBlade IoT Core. Each device sends one HTTP request every minute, and each message is 8192 bytes in size. Each request results in a response, and even though a response may be only a few bytes, any messages smaller than 1024 bytes are still charged as if they were 1024 bytes because 1024 bytes is the minimum size used for billing. Therefore, the total data volume in a month would be about 18.1 TB, calculated as follows:
Requests
...
50,000 devices * 1,440 messages/device per day * 30 days * 8192 bytes = 16.1 TB
Responses
...
50,000 devices * 1,440 messages/device per day * 30 days * 1024 bytes = 2 TB
Total data volume
...
16.1 TB (Requests) + 2 TB (Responses) = 18.1 TB
...