What is the best LoRaWAN IoT platform to build dashboards and alarms for my clients?

Look for four things: integrations with the network server you already use, a separate portal per client, alarms that reach people on the channels they answer, and white label. Cloud Studio IoT covers the four: it connects to seven LoRaWAN network servers, gives each client its own users, dashboards and alarms, notifies by email, SMS, WhatsApp, voice call and push, and carries your brand from €100 a month.

Do I need a network server as well as the platform?

Yes. The network server manages the radio network and decodes the payloads; the platform builds the application on top. Cloud Studio IoT does not include its own network server: it connects to The Things Stack, ChirpStack, LORIOT, ThingPark X, Helium, Orbiwise and IoT Creators, public or private.

Can each client see only its own devices?

Yes. Each client has its own portal, users and permissions, and sees only the devices, dashboards and alarms assigned to it. You keep a central view over all of them. The shared plan includes one client, the dedicated instance ten, and the on-premise plan fifty.

Can I use my own brand and domain?

Yes. White label covers the logo, the colors, the domain and the notification templates, and it is included in every plan. On a dedicated instance there are two levels: your brand on the instance and, if you want, a different brand for each client.

Which LoRaWAN devices are supported?

Any device your network server can decode. The public device library documents the payload and the decoder of 385 models from Milesight, Dragino, Decentlab, Netvox, Elsys and other manufacturers, and when a model is missing our engineers write the driver.

How do alarms reach my clients?

Through five channels: email, SMS, WhatsApp, voice call and push notification in the mobile app. Each alarm has its own recipients, so a low tank level can call the technician on duty while a weekly summary goes to the manager by email.

How much does it cost?

A fixed monthly fee by plan. €100 a month covers one client and up to 50 devices on a shared instance, with white label, API and MQTT. €550 a month is a dedicated instance with 10 clients and 250 devices. Larger or on-premise deployments are quoted. Sensors and gateways are bought separately.

Can I mix LoRaWAN with other devices?

Yes. Devices that speak MQTT or HTTP connect directly, and Modbus or OPC UA equipment connects through a software gateway installed at the edge. They share dashboards and alarms with the LoRaWAN sensors.

LoRaWAN IoT platform

LoRaWAN IoT platform: dashboards and alarms for each of your clients

LoRaWAN sensors

Gateways

Your network server

IoT platform

Client portals

LoRaWAN sensors

Gateways

Your network server

IoT platform

Client portals

Connect the LoRaWAN network server you already use, give every client its own portal with dashboards, alarms and reports, and deliver it all under your brand. Built for integrators, device makers and service operators.

See the device library

What is a LoRaWAN IoT platform?

A LoRaWAN IoT platform is the application layer that sits after the network server. The network server handles the radio side: it joins devices, removes duplicates and decodes payloads. The platform turns those values into something a client can use: dashboards, alarms, reports, user accounts and history. If you sell a service to several clients, the platform also has to keep each client's devices and data apart and carry your brand, and that is the part a network server console does not cover.

It starts at the network server

The platform receives decoded uplinks from The Things Stack, ChirpStack, LORIOT, ThingPark X, Helium, Orbiwise or IoT Creators, and can listen to several of them at once. You keep the network you already run.

Dashboards per client

Maps, charts, tables and synoptics over live and historical data. Each client gets the dashboards built for its sites, and a dashboard can be shared through a public link when no login is wanted.

Alarms that reach people

Threshold alarms and automation rules per device or group, with notifications by email, SMS, WhatsApp, voice call and push. Each client defines who is notified and when.

One instance, many clients

Multi-tenancy means one platform serves all your clients, and each one logs in and sees only its own devices and data. You manage every client from a single central view.

Network server console vs LoRaWAN IoT platform

The console is made for whoever runs the network. The platform is made for whoever uses the data.

Attribute

Network server console

LoRaWAN IoT platform

Made for

The engineer who runs gateways and devices

The client who needs to see and act on the data

What it shows

Frames, signal quality and join status

Dashboards, maps, history and reports

Alarms

Network events, if any

Thresholds and rules, notified by email, SMS, WhatsApp, voice call and push

Clients

Applications and API keys

A portal per client with its own users and permissions

Brand

The network provider's

Yours: logo, colors, domain and notifications

Other protocols

LoRaWAN only

LoRaWAN next to MQTT, HTTP and industrial equipment

The key difference

You need both: the network server gets the data off the air, and the platform is what your client opens every morning.

How to set up a LoRaWAN service for your clients

Five steps from the first sensor to a client logging into a portal with your logo.

Connect your network server

Keep your network

Link the network server you already use. There are ready-made integrations with The Things Stack, ChirpStack, LORIOT, ThingPark X, Helium, Orbiwise and IoT Creators, and one instance can receive from several of them. Cloud Studio IoT does not run its own network server, so there is nothing to migrate.

Supported protocols

The Things StackChirpStackLORIOTThingPark XHelium

What integrators build on it

The same platform and the same sensors, packaged as a different service for each market.

Tank and water monitoring

Level and pressure sensors for a portfolio of clients, each with its own tanks, thresholds and alarm contacts.

Tank monitoring

Buildings and offices

Air quality, occupancy and temperature per building, with a portal for each owner or facility manager.

Smart building

Energy and submetering

Electricity, water and gas meters read over LoRaWAN, with consumption reports sent to each client on a schedule.

Energy management

Agriculture and irrigation

Soil moisture, weather and valve status per farm, with each grower seeing only its own plots.

Smart irrigation

Cold chain

Temperature in cold rooms and fridges for shops, labs and pharmacies, with alarms that reach whoever is on duty.

Cold chain monitoring

Cities and public services

Environmental sensors, parking and waste across a municipality, with public dashboards for citizens.

Smart city

LoRaWAN for your clients with Cloud Studio IoT

A white-label, multi-tenant platform for the companies that build IoT services, with more than 150,000 connected devices.

Seven network servers, no lock-in

The Things Stack, ChirpStack, LORIOT, ThingPark X, Helium, Orbiwise and IoT Creators, several at once. Change network without touching your clients' dashboards.

White label on every plan

Your logo, colors and domain from the first plan. On a dedicated instance each of your clients can carry its own brand too.

Not only LoRaWAN

MQTT and HTTP devices connect directly, and Modbus or OPC UA equipment through a software gateway installed at the edge. One portal for everything a client has.

Monthly, from €100

€100 a month for one client and 50 devices on a shared instance. €550 a month for a dedicated instance with 10 clients and 250 devices. On-premise for larger rollouts.

See plans and pricing

LoRaWAN platform questions

What integrators ask before putting their clients on it.

From the hub

LoRaWAN guides and case studies

Tools and in-depth guides for each part of the topic. Every one links back here for the full picture.

LoRaWAN device library

Payload formats, decoded uplink examples and official decoders for 385 LoRaWAN sensors from Milesight, Decentlab, Dragino, Netvox and more.

LoRaWAN SCADA

How LoRaWAN sensors reach a SCADA through the network server, what they replace and where wired SCADA still wins.

Ultimate Guide to LoRaWAN: How It Works, Benefits, and Real-World Applications

Protocol deep-dive — radio classes, network architecture, security, and where LoRaWAN fits versus other LPWAN options.

LoRaWAN vs. NB-IoT — protocol differences that matter

Unlicensed spectrum and kilometers per gateway vs cellular spectrum and SIM-managed devices — pick the right fit for your project.

LoRaWAN, NB-IoT, Mioty: choosing IoT connectivity

Each LPWAN protocol trades range, power, and licensing differently. The decision framework for your next deployment.

LORIOT + Cloud Studio: a LoRaWAN integration

How the LORIOT network server plugs into Cloud Studio so devices land in the platform with one config click.

Browse the hub

LoRaWAN IoT platform

Put your first client on its own portal

Start with a pilot of up to 50 devices on your network server and add clients as you sign them.

Talk to an engineer

LoRaWAN IoT platform

LoRaWAN IoT platform: dashboards and alarms for each of your clients

LoRaWAN sensors

Gateways

Your network server

IoT platform

Client portals

LoRaWAN sensors

Gateways

Your network server

IoT platform

Client portals

See the device library

What is a LoRaWAN IoT platform?

It starts at the network server

Dashboards per client

Maps, charts, tables and synoptics over live and historical data. Each client gets the dashboards built for its sites, and a dashboard can be shared through a public link when no login is wanted.

Alarms that reach people

Threshold alarms and automation rules per device or group, with notifications by email, SMS, WhatsApp, voice call and push. Each client defines who is notified and when.

One instance, many clients

Multi-tenancy means one platform serves all your clients, and each one logs in and sees only its own devices and data. You manage every client from a single central view.

Network server console vs LoRaWAN IoT platform

The console is made for whoever runs the network. The platform is made for whoever uses the data.

Attribute

Network server console

LoRaWAN IoT platform

Made for

The engineer who runs gateways and devices

The client who needs to see and act on the data

What it shows

Frames, signal quality and join status

Dashboards, maps, history and reports

Alarms

Network events, if any

Thresholds and rules, notified by email, SMS, WhatsApp, voice call and push

Clients

Applications and API keys

A portal per client with its own users and permissions

Brand

The network provider's

Yours: logo, colors, domain and notifications

Other protocols

LoRaWAN only

LoRaWAN next to MQTT, HTTP and industrial equipment

The key difference

You need both: the network server gets the data off the air, and the platform is what your client opens every morning.

How to set up a LoRaWAN service for your clients

Five steps from the first sensor to a client logging into a portal with your logo.

Connect your network server

Keep your network

Supported protocols

The Things StackChirpStackLORIOTThingPark XHelium

What integrators build on it

The same platform and the same sensors, packaged as a different service for each market.

Tank and water monitoring

Level and pressure sensors for a portfolio of clients, each with its own tanks, thresholds and alarm contacts.

Tank monitoring

Buildings and offices

Air quality, occupancy and temperature per building, with a portal for each owner or facility manager.

Smart building

Energy and submetering

Electricity, water and gas meters read over LoRaWAN, with consumption reports sent to each client on a schedule.

Energy management

Agriculture and irrigation

Soil moisture, weather and valve status per farm, with each grower seeing only its own plots.

Smart irrigation

Cold chain

Temperature in cold rooms and fridges for shops, labs and pharmacies, with alarms that reach whoever is on duty.

Cold chain monitoring

Cities and public services

Environmental sensors, parking and waste across a municipality, with public dashboards for citizens.

Smart city

LoRaWAN for your clients with Cloud Studio IoT

A white-label, multi-tenant platform for the companies that build IoT services, with more than 150,000 connected devices.

Seven network servers, no lock-in

The Things Stack, ChirpStack, LORIOT, ThingPark X, Helium, Orbiwise and IoT Creators, several at once. Change network without touching your clients' dashboards.

White label on every plan

Your logo, colors and domain from the first plan. On a dedicated instance each of your clients can carry its own brand too.

Not only LoRaWAN

MQTT and HTTP devices connect directly, and Modbus or OPC UA equipment through a software gateway installed at the edge. One portal for everything a client has.

Monthly, from €100

€100 a month for one client and 50 devices on a shared instance. €550 a month for a dedicated instance with 10 clients and 250 devices. On-premise for larger rollouts.

See plans and pricing

LoRaWAN platform questions

What integrators ask before putting their clients on it.

From the hub

LoRaWAN guides and case studies

Tools and in-depth guides for each part of the topic. Every one links back here for the full picture.

LoRaWAN device library

Payload formats, decoded uplink examples and official decoders for 385 LoRaWAN sensors from Milesight, Decentlab, Dragino, Netvox and more.

LoRaWAN SCADA

How LoRaWAN sensors reach a SCADA through the network server, what they replace and where wired SCADA still wins.

Ultimate Guide to LoRaWAN: How It Works, Benefits, and Real-World Applications

Protocol deep-dive — radio classes, network architecture, security, and where LoRaWAN fits versus other LPWAN options.

LoRaWAN vs. NB-IoT — protocol differences that matter

Unlicensed spectrum and kilometers per gateway vs cellular spectrum and SIM-managed devices — pick the right fit for your project.

LoRaWAN, NB-IoT, Mioty: choosing IoT connectivity

Each LPWAN protocol trades range, power, and licensing differently. The decision framework for your next deployment.

LORIOT + Cloud Studio: a LoRaWAN integration

How the LORIOT network server plugs into Cloud Studio so devices land in the platform with one config click.

Browse the hub

LoRaWAN IoT platform

Put your first client on its own portal

Start with a pilot of up to 50 devices on your network server and add clients as you sign them.

Talk to an engineer