MyQttHub.com
Focus on your MQTT IoT project
MyQttHub.com provides highly scalable support for MQTT, based on Akka and Scala technology.
Using an open protocol like MQTT you will be able to interconnect your devices and share messages.
See startup guideWeb panel to manage your Cloud MQTT platform. Direct connect with your context domain engine.
Web panel allows to manage devices, passwords, published messages, do PUBLISH, manage subscriptions.
MyQttHub supports TLS/SSL/HTTPS for secure MQTT-TLS and HTTPS communications.
Moreover, you can control source IP allowed to connect for all your devices, including MQTT administrator user.
This will provide you additional security to deploy your cloud IoT project, avoiding unauthorized access.
You can use this platform for system interconnection in a way they are isolated from each other (no direct connection), but at the same time connected.
This provides system isolation by providing system decoupling techniques. This allows to separate systems that are producing data from those consuming and processing them.
You can filter subscribe, publish and by content. Filters can be configured for certain topics and limited to certain users.
Filters docStore your important messages in a durable manner and in the order they were received. This is stashing.
From this storage you can resend messages, view and download them, and much more.
Stashing docYou can publish messages using the web panel (without needing a MQTT client). This publish operation can be done in a general domain way or directed to a certain device. This is very useful to debug and direct testing with a certain device.
| Open | Micro | Starter | Basic | Standard | Profesional | Premium | |
|---|---|---|---|---|---|---|---|
Users/Devices Max users/devices that can be created in the MQTT HUB. These users/devices represents a single clientId +userName +password combination that can access to your MQTT HUB. Note Devices/Users are exchangeable terms used to refer to the same thing: a MQTT device connecting to the platform, but also a user using that MQTT credential connecting through the web interface, but also an authenticated device/user connecting to the platform using the HTTPS+json API. All these examples are devices/users connecting to the platform. |
100 | 200 | 500 | 1.000 | 2.000 | 4.000 | 6.000 |
Panels Max number of panels/dashboard that can be created for a particular MQTT HUB. |
3 | 5 | 10 | 20 | 40 | 70 | 140 |
Max connections Max concurrent MQTT connections that can be accepted for this MQTT HUB. If limit says 50 max connections, it means you can have 79 devices registered but only at most 50 connected concurrently (at the same time). If these devices connect, exchange, and disconnect, then they use a connection slot while they are connected, and they leave a free connection slot available when they disconnect. That is, this limit represents max available slots for holding concurrent connections for your MQTT hub. |
50 | 100 | 250 | 500 | 1.000 | 2.000 | 3.000 |
Storage As part of the MQTT protocol you need storage to sustain QoS1 and QoS2 messages in transition. Also you need storage to hold pending to deliver messages for offline subscriptions. MyQttHub.com also provides different features like Stashing which also store messages for you to handle them afterwards. All these elements need storage. |
10MB | 100MB | 200MB | 500MB | 1GB | 2GB | 2.5GB |
Max subscriptions per conn. As part of the MQTT protocol you send SUBSCRIBE messages to subscribe topics or a set of topics. Each time a device sends a SUBSCRIBE it becomes parts of its session and sustain with the rest of subscriptions the set of topics filters that will match messages to be delivered for these devices issuing those SUBSCRIBE messages. An individual SUBSCRIBE message represents one subscription. This limit provides an upper max active subscriptions that can be sustained by a single connection. |
50 | 100 | 100 | 100 | 100 | 100 | 100 |
Max subscriptions As part of the MQTT protocol you send SUBSCRIBE messages to subscribe topics or a set of topics. Each time you send SUBSCRIBE it becomes parts of its session and sustain with the rest of subscriptions the set of topics filters that will match messages to be delivered for these devices issuing those SUBSCRIBE messages. An individual SUBSCRIBE message represents one subscription. This limit provides an upper max active subscriptions for the complete hub, considering all active subscriptions that are created by all connections (offline and online). In case an active connection, created by a device/user, wants to create another subscription (SUBSCRIBE), then both limits are checked. Both must be under limits to successfully SUBSCRIBE. |
250 | 500 | 1.250 | 2.500 | 5.000 | 10.000 | 15.000 |
Max message size This is the max message size limit. PUBLISH messages must be under or up to this limit. See https://support.asplhosting.com/t/how-messages-are-counted-by-myqtthub-message-quotas/46 |
4KB | 32KB | 32KB | 32KB | 64KB | 64KB | 128KB |
Msg. measuser size For MyQttHub.com it is not the same sending small messages than bigger ones. If you send bigger messages than the Message Measurer Size, it will be allowed but more message quota unit will be consumed. See all details at: https://support.asplhosting.com/t/how-messages-are-counted-by-myqtthub-message-quotas/46 |
0.5KB | 4KB | 4KB | 4KB | 4KB | 4KB | 4KB |
Messages/minute Max amount of messages that can be send/relayed by your MQTT Hub each minute. See https://support.asplhosting.com/t/how-messages-are-counted-by-myqtthub-message-quotas/46 for all details. |
300 | 600 | 1.000 | 2.000 | 3.000 | 6.000 | 9.000 |
Messages/hour Max amount of messages that can be send/relayed by your MQTT Hub each hour. See https://support.asplhosting.com/t/how-messages-are-counted-by-myqtthub-message-quotas/46 for all details. |
800 | 2.000 | 4.000 | 8.000 | 12.000 | 24.000 | 36.000 |
Messages/day Max amount of messages that can be send/relayed by your MQTT Hub each day. Day account starts at 00:00 midnight each day. See https://support.asplhosting.com/t/how-messages-are-counted-by-myqtthub-message-quotas/46 for all details. |
10.000 | 24.000 | 48.000 | 96.000 | 144.000 | 288.000 | 432.000 |
Messages/month Max amount of messages that can be send/relayed by your MQTT Hub each month. Month account starts at 1th, 00:00 midnight each month. In order to send the message, all limits (minute, hour, day or month) must not be exahusted. See https://support.asplhosting.com/t/how-messages-are-counted-by-myqtthub-message-quotas/46 for all details. |
310.000 | 720.000 | 1.440.000 | 2.880.000 | 4.320.000 | 8.640.000 | 13.120.000 |
MQTT TLS protection Support to create security MQTT TLS connections (8883 standard secure port for MQTT-tls) |
|||||||
REST HTTPS API Access to HTTP+json API to manage and control your MQTT Hub. See details: https://support.asplhosting.com/t/rest-api-to-manage-myqtthub-service/86 |
|||||||
Forum access Support to issue support requests to community support forum. See https://support.asplhosting.com/c/myqtthub-en |
|||||||
Private messaging Full private topic tree visibility. Your MQTT hub will not share MQTT topic tree with other MQTT Hub: your MQTT hub will have complete private and isolated MQTT namespace without any prefix. In effect, a dedicated MQTT broker. |
|||||||
Technical Support Technical support through forum or using private support@myqtthub.com to resolve questions. |
- | ||||||
Manage several domains Subscribed plans have support to handle several MQTT hub plans using a single credential and also to have different MQTT admin users on the same plan. To support multi-domain or multi-admin configurations all MQTT hubs involves must be working with a subscribed plan. |
- | ||||||
| Open | Micro | Starter | Basic | Standard | Profesional | Premium | |
| Subscription Anual (See conditions) |
- | €/month |
€/month |
€/month |
€/month |
€/month |
€/month |
MyQttHub.com provides public community support through its forum (https://support.asplhosting.com/c/myqtthub-en). Use support forum as your primary source of support. It is plenty of documentation, cases an articles that will help you develop your IoT project.
If still you need privated dedicated support through mail or by phone, please contact use to know your case: support@myqtthub.com
In case you need different limit configurations, higher connection limits, including deploying MyQttHub.com on premise, please, contact us: support@myqtthub.com
