Your devices talk to one place

Una IoT Center sits between the networks your devices live on and the systems that want their readings. You configure the connection once; the Center receives every message, decodes it, shapes it the way each destination expects, and keeps delivering until it lands.

What it saves you

    One integration, not N×M
    Two device networks and three destination systems is six integrations to write and maintain. Here it is five connections you configure, and the Center handles every pairing between them.
    Each destination gets its own shape
    The same reading can arrive as a full envelope in one system and three bare fields in another. You pick the shape per pair, and preview it before saving.
    Delivery that keeps trying
    A destination that is down does not lose your data. Messages retry with backoff, and anything that exhausts its attempts waits in Dead letters for you to fix the cause and replay it.
    Raw bytes become named readings
    Attach a decoder to a device model and 00018d46… turns into index: 18.061, unit: "m3" — which is what your rules filter on and your destinations receive.
    Rules before delivery
    Drop the noise, send alerts somewhere different from routine readings, or answer a device with a downlink — as ordered rules, not code.
    Built for more than one customer
    Tenants nest, so an operator can hold resellers who hold end customers, each seeing only their own devices, projects and credentials.

Where to go next

Quickstart
Get one device delivering into one destination, end to end.
The pipeline
What happens to a message between arriving and being delivered.
Concepts
Tenants, projects, devices, integrations — the words the app uses.
Guides
Step-by-step for each thing you will actually set up.
Copyright © 2026