Weik.io Cloud

MQTT brokers

An MQTT broker in Weik.io Cloud receives messages from your machines and devices over TLS, and an event source brings them into a Weik.io channel.

Create an MQTT broker See the prices

What you get

Every MQTT broker has:

MQTT 3.1.1 and MQTT 5 over TLS at <name>.mqtt.weikio.cloud on port 8883
Clients that sign in with a user and a password or with a client certificate
Topic access for each client, to publish, to subscribe or both
Retained messages, so a new subscriber gets the last value of each topic
An event source in your workspace that turns the messages into events

Sizes and prices

MQTT brokers, monthly prices
Size	Connections	Price
S	1,000 connections	€39 a month
M	10,000 connections	€99 a month
L	50,000 connections	€249 a month

Connections are the clients connected at the same time. You move a broker to a larger size in the console, and its address and clients stay. Prices are monthly, in euros and excluding VAT.

How it connects to Weik.io

The event source in your workspace subscribes to the topics you choose and publishes each message into a channel as an event, and your integrations read that channel like any other.

An event that a reader still fails after its last retry goes to the dead letters, where weikio deadletters lists it and sends it to the reader again.

plant/event-sources/plant-readings.yaml

apiVersion: weik.io/v1
kind: event-source
metadata: { name: plant-readings, project: plant }
spec:
  type: mqtt5
  parameters:
    brokerUrl: "ssl://plant-mqtt.mqtt.weikio.cloud:8883"
    topic: "plant/+/readings"
    username: acme-workspace
    password: "{{plant-mqtt-password}}"

The event source subscribes to the readings of every machine in the plant and publishes them into the channel plant-readings. It runs the same way in a workspace and in a Weik.io you install yourself, and Event sources in the docs lists the other systems a source can read.

Where it runs

Brokers: Hetzner's Helsinki data centre park in Finland, which is ISO/IEC 27001 certified
Messages: On the broker in Helsinki, and in your workspace's channel once the event source publishes them

Read the sovereignty list

Questions

Which MQTT versions does a broker accept?

MQTT 3.1.1 and MQTT 5, both over TLS on port 8883.

Can devices sign in with certificates?

Yes, with client certificates, or with users and passwords. You choose the method for each client.

Can a self-hosted Weik.io read the broker?

Yes, an event source in your own installation subscribes to the broker with a client of its own.

What does a connection mean in the sizes?

One client connected to the broker. A size S broker accepts 1,000 clients at the same time.

Create an MQTT broker

The console creates the broker with its first client and shows the address your devices connect to.

Create an MQTT broker See the prices