Page Comparison

ClearBlade IoT Core

...

This page provides ClearBlade IoT Core pricing details.

...

pricing (USD)

Overview

Cloud ClearBlade IoT Core is priced according to the data volume used in a calendar month:

Data volume is based on data exchanged by devices that are connected to Cloud ClearBlade IoT Core. There is no charge for create, read, update, and delete operations through the device manager.

If you use ClearBlade IoT Core with Cloud Pub/Sub, then you will also be billed separately for consuming Cloud Pub/Sub resources.

^*The minimum charge is for a 1024-byte message:

• For messages that are smaller than 1024 bytes, a charge for 1024 bytes will be applied. For example, if a device sends 25 bytes in an MQTT message, the charge for that message will be 1024 bytes × price/MB for the applicable monthly data volume tier.

• For messages that are larger than 1024 bytes, the charge will be _messagesize × price/MB for the applicable monthly data volume tier.

Billable messages

MQTT

• CONNECT

• PUBLISH (both cloud - and device-bound)

• PUBACK (ack of device configuration, cloud-bound)

• SUBSCRIBE

• PINGREQ

...

• CONNACK

• PUBACK (publish telemetry or state , from cloud to device)

• SUBACK

• PINGRESP

• DISCONNECT

• UNSUBSCRIBE

• UNSUBACK

Compressed HTTP requests

As noted in Using the HTTP Bridgebridge, a device can send gzip-compressed data to Cloud ClearBlade IoT Core over the HTTP bridge.

Billing for telemetry Telemetry event payloads 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 Cloud ClearBlade IoT Core over an MQTT connection. Even if the devices don't send any telemetry events or state data over a one month period, they will still send PINGREQ messages to Cloud ClearBlade IoT Core in order to keep the MQTT connection alive. The PINGREQs’ frequency of the PINGREQs depends on the each connection’s keep-alive value for each connection. Even though a PINGREQ may be only a few bytes, any messages smaller than 1024 bytes are still charged as if they were 1024 bytes , because 1024 bytes it is the minimum data size used for billing.

If you set the keep-alive value for your devices to 15 minutes, then each device would send a PINGREQ at least every 15 minutes. The total data volume for just the PINGREQ messages would be 27.47 GB, calculated as follows:

...

Taking into account the free data volume up to 250 MB , and the fact that the $0.0045 price per MB is $0.0045 in the 250 MB to 250 GB range, the pricing per month would use the following this formula:

(27.47 GB - 250 MB) * $0.0045 = $125.46

...

Say that you have 10,000 devices connected to Cloud 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. The 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

Taking into account the free data volume up to 250 MB , and the fact that the $0.0045 price per MB is $0.0045 in the 250 MB to 250 GB range, the pricing per month would use the following this formula:

(27.46 GB - 250 MB) * $0.0045 = $125.41

...

Say that you have 50,000 devices connected to Cloud 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

Taking into account the free data volume up to 250 MB , and the fact that the price per MB changes changing to $0.0045 in the 250 MB to 250 GB range, the pricing per month would use the following formula:

...

Consider a case where you have 50,000 devices connected to Cloud 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. The 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

Taking into account the free data volume up to 250 MB , and the fact that the price per MB changes changing from $0.0045 in the 250 MB to 250 GB range to , $0.002 in the 250 GB to 5 TB range, and then to $0.00045 for anything above 5 TB, the pricing per month would use the following this formula:

(250 GB - 250 MB) * $0.0045 + (5 TB - 250 GB) * $0.002 + 13.1 TB * 0.00045 = $17,305.99

What's next

...

Read the Google Cloud IoT Core documentation.

...