ioX-Bridge LoRaWAN Network Server

It sits between your gateways and your application. It handles device activation, tracks session state, discards duplicate copies of an uplink that reached several gateways, manages data rates, decodes the payload if you have given it a decoder, and delivers the result to wherever you have told it to. Gateways are radios; the network server is what makes a set of them behave like a network.

A network server moves data off the radio and hands it on. An IoT platform is what people log into: device inventory, dashboards, alerting, reporting and user accounts. They solve different problems and most deployments need both. ioX-Bridge is the network server and ioX-Pulse is the platform.

Any standards-compliant LoRaWAN gateway. If it runs the Semtech UDP packet forwarder, point it at your region's address and port. If it runs Basics Station, generate a client certificate in the console and set the gateway's LNS URI to the secure WebSocket endpoint for your region. No proprietary gateway is required and no specific vendor is preferred.

Use Basics Station if your gateway supports it. It runs over TLS with a client certificate issued for that specific gateway, so the connection is both encrypted and authenticated, and gateways attempting to connect without a certificate are refused. The UDP packet forwarder is supported because a great deal of deployed hardware runs it, not because it is the better choice.

Two ways, configured per network. An HTTP integration posts each event to your endpoint as JSON, with any headers you need, and you can pause and resume it without losing the configuration. Or subscribe over MQTT with TLS to a topic per device and event type. Both carry the same JSON: device identity, the raw payload, the decoded object, and signal quality.

Yes. Write a JavaScript decode function that receives the payload bytes and the port and returns named values, and whatever you return appears as the decoded object on every delivered event. Cayenne LPP is supported where a device already encodes it, and the vendor template catalog carries tested decoders for hardware already in it.

No. ioX-Bridge is a network server in its own right and you can connect whatever application you like to it over HTTP, MQTT or the API. The reverse is also true: if you want the layer above without building it, ioX-Pulse is already wired to it.

US915, EU868 and AU915, each with its own endpoint. A gateway's configured region has to match its frequency plan; when it does not, packets are dropped without an error, which makes it worth checking first when nothing is arriving.

Talk to us. ioX-Bridge environments are provisioned rather than signed up for, so there is no self-serve checkout for it. Tell us your gateway models and your regions and the conversation starts from something concrete.