Paqett Console · for device makers, integrators and software firms

Your fleet and its data, in one console.

For teams whose devices run on Paqett. LoRaWAN and cellular side by side: what is reporting, what each device sent, and the same data from the API.

Not publicly available yet. Contact us to take part in testing.

Built for the engineer who gets the call

The console uses the API's own words and keeps the raw values in view. It answers three questions without a support ticket.

  1. Is everything reporting?

    Overview lists what needs a look, worst first, with the likely cause beside it.

  2. What is this device doing?

    Readings, health and the raw messages it sent, on one page per device.

  3. How do I get the data out?

    Browse it, export it, or copy the API call that returns exactly what you are looking at.

In the console today

Devices, data and keys

One table for the fleet, health in it

Every device with its state, last heard, battery and signal. Filter to the silent ones in a click. Open a device for its readings, health, raw messages and settings.

The explorer and the API return the same thing

Pick devices, fields and a time range, and read the result as a chart or a table. Export it, or take the request and run it from your own code with a key you made a minute ago.

Organisations, projects and an audit log

Split a fleet into projects, invite your team, require two-step sign-in and see who changed what. When Paqett support looks at your account, that is in the log too.

What we are building next

More of the device, in the same console

In the order we expect to ship it. Tell us which one you are waiting for.

  1. Device certificates for MQTT

    Devices that connect direct, each with its own X.509 certificate.

  2. Firmware over the air

    Signed releases, staged rollouts and a way back.

  3. Alerts you set yourself

    Rules as a form, previewed on stored readings, with a log of who was told.

  4. Gateways and SIMs

    Their own pages: traffic, sessions, data used and the devices behind each one.

  5. Writing to devices

    Set a value, watch it go from queued to delivered to acknowledged.

  6. Location

    Tracks, fixes and geofences for devices that move.

Further out

Where the platform is heading. Not scheduled yet, so tell us what would matter to you.

  1. Wi-Fi and Matter

    More radios beside LoRaWAN and cellular, in the same tables and the same API.

  2. Registered at the factory

    Devices enrolled as they are built, so they report from first power-on.

  3. Live data

    Readings pushed over WebSocket as they arrive, beside the REST API.

  4. A stack of your own

    Broker, database and firmware service dedicated to one customer, where shared hosting will not do.

  5. Datasets for physical AI

    Every reading timestamped, located and traced to its sensor, packaged to train and test models.

  6. Data licences

    Opt in to offer your data to buyers who need it, as datasets or feeds, so it helps pay for its own capture.

Not publicly available yet · open for testing

Have devices that need a home?

Tell us what they are, how they connect and how many. We will say plainly whether the console fits today. Pricing follows the infrastructure a deployment needs, not the device count.