IoT Hub

  • IoT networks
    MQTT, REST, Sigfox, LoRa
  • IoT routes
    Multi-cloud compatible
  • Security
    Per-device TLS certificate
  • Hub/Device metrics
  • MQTT protocol
    Fully compliant, all QoS levels
  • MQTT version
    MQTT 3.1.1
  • Developer tools
    API, CLI & Terraform
Smart City
Industry 4.0
Smart Home
Available Regions
  • Paris
  • Shared, Dedicated or HA Plan
  • Pay as you go
  • 50,000 free messages
Free shared plan

Included Features

  • IoT Networks
  • Virtual Devices
  • IoT Routes
  • Identification and Security
  • Metrics
  • Message Filters
  • Quality of Services 0, 1 & 2
  • Retained Messages

IoT Hub, the perfect bridge between your objects and your business applications

Do you need help to build your project or to find a partner to expose your data?


Our technical teams can support you from prototyping to the production of complete IoT solutions.

With 20 years of expertise in server set-up, we have forged strong links with hardware manufacturers. Nevertheless, if you already have hardware expertise, we can also guide you to open-source solutions, connect you with software vendors that allow you to expose your data, or assist you in setting up and developing a cloud architecture.

Contact us

Simple & Predictable Pricing

Scaleway IoT Hub is a resilient and multi-protocol message broker with export capabilities. It comes in three flavors: shared, dedicated and highly-available.

PlanConnected DevicesIncluded MessagesAdditional MessagesPrice


10 included

50,000 msg/month

(~1 msg/min)





2 millions msg/month

(~50 msg/min)



High Availability


10 millions msg/month

(~250 msg/min)



Message size unit: 4kB (a 10kB message = 3 messages billed)

The message journey, from the device to any cloud

IoT Hub Features Overview

IoT Networks

Scaleway IoT Hub has been natively developed with the MQTT protocol. Nevertheless, we also support other IoT communication protocols such as Sigfox or LoRa to let you build your applications and give value to your data no matter how your device communicate with the cloud. These connections between your devices and the message broker are called IoT Networks.

Virtual Devices

A virtual device is a representation of a device or an application that is connected to the cloud. Through a Hub, the virtual device exchanges messages with other Devices and cloud services. Devices use the MQTT protocol to send and receive messages with the Hub. The Hub provides per-device usage metrics, security, and filters. See this page for more information.

IoT Routes

Scaleway IoT Hub is compatible with other elements of the Scaleway ecosystem and with other cloud provider or third party applications.  The IoT Routes provide a gateway between these cloud services and your IoT Hub. Several IoT Routes can be currently used:
Object Storage, to store your metrics in a S3 compatible Object Storage Bucket.
Database, to store your connected objects received information in a PostgreSQL database.
REST routes give you millions of possibilities to connect with either your instances, your Serverless functions or with third party applications.

Identification and Security

Each Device has a unique identifier that is used both for API calls and for MQTT connections (as the MQTT Client Identifier). To obtain a secure communication between a Hub and a Device, the MQTT connection may be protected by TLS. Any Device can use TLS to connect, but it is possible to bypass it: this is the allow/deny insecure toggle. There are three modes of connection: Mutual-authentication TLS, Server-authentication TLS or Plain (no security).


Metrics can be displayed at your Hub level or at your devices level and they give a complete report of the usage of your assets. The metrics interface includes a message counter and your devices activity overview over a chosen period of time. See this page for more information.

Message Filters

Message filters allow you to control which topics a device can publish and subscribe to. There is a publish filter and a subscribe filter, each filter operates independently. You can either accept topics in the list (and reject others) or reject topics in the list (and accept others). Topics in the lists may contain MQTT wildcards.

Quality of Services 0, 1 & 2

MQTT’s Quality of Service levels determine how the relationship between the sender and the receiver should unfold when they are communicating.
Three levels exist in the protocol:
QoS 0 – “At most once”, also known as “fire and forget”, the message is not guaranteed to be received by the receiver
QoS 1 – “At least once”, this level guarantees that a message sent will be received but doesn’t prevent it from being received multiple times
QoS 2 – “Exactly once”: This level of service guarantees that the message sent won’t be received multiple times

Retained Messages

The Hub can be asked to keep a copy of the last message published on a topic. In such case, a subscriber will immediately receive it upon subscription. This is called a retained message and allows to keep track of the last known state of your system. In this case the publisher of message will asked the Broker to keep this message in memory by adding a Retain flag in the message. Any subscriber will immediately receive the last memorized message published on the subscribed topic.

A project? Contact us:

What is the value of your data?

Smart Cities

Connected cities creates new opportunities and new usages. For exchanges to be smoother and decision to be taken rapidly, the cities have to be connected to gather the more information possible. With Scaleway IoT Hub, we give you a way to quickly gather theses pieces of information and forward them to your added-value application. No matter if you want to connect traffic lights or parking places to improve traffic or if you connect public trashes to create a new waste management solution, you can use our highly available message broker to forward your millions of small messages.

Industry 4.0

IoT is one of the major component behind the industry 4.0 concept, along with 3D impression, Industrial Artificial Intelligence and Augmented Reality. What is certain is that the next industrial revolution will be connected to the cloud. By connecting your machines to our highly available message broker, start gathering data from your factory to improve your products quality, predict when your machine will fail or even have a better monitoring of your workflows.

Smart Home

From air quality sensors to connected alarms to intelligent heating, connected homes create a safer home, help to consume better while improving the quality of life of your customers. Homes connected objects can be directly connected to the cloud or can centralize their messages to a hub that is very often, also connected to the cloud. With our IoT Hub, we want to give an affordable solution to gather IoT messages and to forward them to your applications where your added value has been developed.

You have a project? Contact us:

Why Choose Scaleway IoT Hub

Fully MQTT Compliant

Our DevOps have developed the message broker to be fully compliant with the MQTT protocol. This includes the three levels of Quality of Service (0, 1 & 2), the “retained message” and “last will” features. The role of the message broker is to handle all the MQTT logic (pub/sub operations, messages routing logic). The currently used underlying broker is Mosquitto.

Production Ready

You can choose between three plans: A shared plan, a dedicated plan and a highly available to closely follow your needs. For production environment, we recommend to use a dedicated or a highly available plan. With the high availability plan, your managed message broker will be replicated on our infrastructure to always forward your critical IoT messages to your cloud services.

Kickstart Applications

Whether you want to quickly develop a Proof of Concept or you want to test the IoT Hub, we developed IoT kickstart applications that can be easily deploy on our virtual instances. Four major use cases are currently available with the kickstart applications: Data visualization with time-series databases and Grafana, logging with ElasticSearch and Kibana and flow programming with NodeRED and Serverless to use custom Functions as a Service.


Push your IoT messages to Scaleway Ecosytem

Frequently Asked Questions

What is IoT Hub?

IoT Hub is an IoT Platform as a service, it sits between connected devices and business-specific software. All kinds of connected devices supporting the MQTT protocol can be connected to IoT Hub.

How secure is Scaleway IoT Hub?

Scaleway IoT Hub was designed with security in mind. Therefore, we implemented mutual authenticated TLS as the default authentication method. Each device needs its certificate+key pair to connect to the hub.
For devices not supporting secure connections, it is possible to also enable plaintext and server-only TLS authentication.

What is a IoT message ?

MQTT is a Publish/Subscribe protocol (more info on the MQTT protocol here).
A message is the base unit for data transmission, it mainly contains :
  • topic: the message information type identifier, such as fr/paris/weather.   Devices that have subscribed to a topic will receive any message published to this topic.
  • payload: the actual data to be transmitted. Can be anything (temperature, image, notification, …) in any format (binary, xml, json, yaml, …)

What is Deny/Allow insecure connection?

Each Device has 2 different levels of security:
  • Deny insecure connection: in this mode, the only way for a Device to connect to a Hub is to use TLS with mutual authentication.
    This is the strongest security setting.
  • Allow insecure connection: in this mode, a Device can connect using TLS with mutual authentication as before, but can also connect with TLS with server-side authentication only, and with no TLS at all.
    This is the weakest security setting.

My software/library limits MQTT client ID to 23 characters, what should I do?

If you fall into this situation, you can type your Device ID in the MQTT Username field. If no valid Device ID is found in the MQTT client ID field but one is found in the MQTT Username field, the one found in the Username field will be used as client ID.

What is a Device ID and a Client ID?

A Device ID is a unique identifier for a device. It is used in calls to the IoT API to designate a specific device.
It must also be used as the MQTT Client Identifier field during connection.
If your software doesn’t have a setting for Client ID, you can use the Device ID in the Username field instead. If no Device ID is found in the client ID field, but it is present in the Username field, the one used in the Username field will be used as the Client ID.

Start using Scaleway IoT Hub to gather your connected objects messages

A project? Contact us: