ioX-Pulse - LoRaWAN IoT Platform

ioX-Pulse is an IoT device management platform for LoRaWAN networks. It decodes sensor payloads into named readings and presents them as live dashboards, alerts, and reports. Service providers also run it as a multi-tenant workspace, with a separate sub-account for each customer under their own brand.

Yes. Any standards-compliant LoRaWAN gateway connects over the Semtech UDP packet forwarder, and sensors from major manufacturers are already in the device profile library with tested decoders. If your device is not there, you can write a decoder yourself or ask us to add one.

A network server handles the radio side: authenticating devices, removing duplicate messages, and managing data rates. It hands you a payload. ioX-Pulse starts there: it decodes the payload into readings, stores the history, draws the dashboards, evaluates the alert rules, and controls who sees what. Most deployments need both. The network server underneath ioX-Pulse is ioX-Bridge.

Yes. You set the app name, menu and login logos, favicon, home-screen icon, and brand colors, and you can point your own domain at the workspace so customers never see another company's name. Sub-accounts inherit your branding, so every customer sees one consistent product.

Through a device profile. The profile holds a JavaScript decoder that converts the raw bytes into named fields, along with the field definitions and display defaults. You can start from the manufacturer library, clone an existing profile, or write a decoder from scratch and test it against a real payload before saving.

Two ways. The REST API under /api/v1 lets your application read history and send commands, with a live interactive reference and an OpenAPI document. Webhooks push five event types (new readings, devices going online or offline, and alarms triggering or clearing) to your endpoint as they happen, signed so you can verify they came from us.

It is marked offline once it has been silent past its threshold, 30 minutes by default and adjustable per device. A workflow can email or text you when that happens. Its status also shows on the device list and on any dashboard widget bound to it.

Yes. A dashboard can be shared as a link that opens in any browser with no sign-in, useful for a screen on a factory floor, or a customer who just wants to watch their own site. Links can be left open or protected with a password, are read-only by default, and can be revoked at any time.

Yes. Roles carry both visibility and permission settings, and both can be overridden, so a login that sees only Dashboards and can change nothing is a configuration rather than a special build. Access to an individual dashboard can also be limited to named people or to members of a particular site.

Yes. You can pick a plan and start a trial without a sales conversation. Your card is collected up front but not charged until the trial ends, and you can cancel before then.