Device registry
Every device is recorded with its identity, model, firmware version and site. No data is accepted without device authentication.
FIOTX Platform
The layer where your devices are registered, monitored, controlled and updated. Because it is container based, it runs the same way on your own server, in the cloud, or on an industrial PC at the site.
Capabilities
Everything an IoT project expects from the cloud
Telemetry and dashboards
High-resolution time-series storage, historical queries, site and device level dashboards, and export.
Remote control and shadow
Desired and reported state are kept apart, so a command issued while a device is offline is applied when it returns.
Alarms and events
Alarms from thresholds, state changes and loss of communication, with event history and notification flows.
FOTA campaigns
Firmware registry, signed images, staged rollout, version distribution and failure tracking.
LoRaWAN network server
An integrated network server: gateways, device activation and the uplink/downlink flow are managed in the same place.
Deployment
You decide where your data lives
The same platform runs in three different places. The choice is not a technical constraint but your data and operations preference — and it can be changed later.
In our managed cloud
The fastest start. Setup, backups, updates and monitoring are ours; you only put the devices in the field.
On your own server
On your in-house server or the cloud of your choice. Data never leaves your infrastructure; access and retention policy stay entirely yours.
On the edge device on site
Where connectivity is weak or not permitted, the platform runs on the device at the site; monitoring and control continue over the local network.
What stays the same in all three
- Same device, same interface. Changing where it runs makes no difference to the device or to the user experience.
- Identity is checked at the door. An unrecognised device cannot write data to the platform.
- It keeps working when the link drops. Control logic lives on the device in the field, so the site does not stop when the cloud is unreachable.
- Storage that scales. Device management does not slow down as telemetry history grows.
- The device connectsIt is recognised by its identity and starts sending data over an encrypted channel.
- Data is storedMeasurements are recorded so they can be queried historically.
- Rules runThresholds and state changes become alarms, and alarms become notifications.
- Commands go downA command from the dashboard reaches the device — or is applied when it comes back online.
- Data goes outThrough the API it can flow into your existing ERP, BMS or reporting systems.
Remote programming
PN Controls Studio — edit control logic from a browser
Programmable devices such as PN Connect IO Edge run their control logic on PN Controls Studio. The Studio service makes that diagram visible and editable remotely, so nobody has to drive to the site.
- Live viewThe control diagram running on the device and its current values are read straight from it.
- EditingAdd a component, write a value, link an output to an input.
- Signed deploymentThe change is signed and sent to the device over an encrypted channel; only our signature is accepted.
- ReversibleThe new version goes live on trial first; without confirmation the device returns to the working one.
- No interruptionA normal deployment does not reboot the device, so the site keeps running.
The control logic stays on the device
The point of PN Controls Studio is that automation does not depend on the cloud. When the link drops, pumps keep running, HVAC keeps being controlled and alarms keep being raised; once connectivity returns, data and event history are uploaded.
Our own component library ships input/output handling and cloud publishing inside the diagram itself, so the logic you build graphically talks to the platform without extra code.
Every change leaves a trace. Who changed what, and when, is held in a record that cannot be erased — which is usually what settles the arguments after commissioning.
Behind the scenes
PN Controls Portal — the device birth record
While FIOTX runs the field operation, the Portal holds the manufacturing and commercial life cycle of a device. The separation is deliberate: which batch a device came from and when its warranty started does not need to live in the same system as its current temperature reading.
- Product catalogue, production batches and device identity records
- Stock, partner orders and shipment preparation
- Warranty start, RMA and service tickets
- Firmware registry, FOTA campaigns, SBOM and vulnerability records
Production
Every board receives its identity on the line and enters inventory together with its test results.
Field
Warranty starts when the device is bound to a customer; service history follows the serial number.
Compliance
Bills of materials, vulnerability and incident records are kept ready for regulatory requirements.
Partners
Resellers and integrators see their own stock, orders and fault reports from their own accounts.
Let's walk through the platform
We can run a live demo against your own scenario and discuss deployment options on your infrastructure.