Is this IoT device platform a hosted SaaS we subscribe to?

No. You get building blocks — device models, API hooks, and UI starting points — that you brand, host, and operate. ParticLIO does not run your production application or customer data plane.

How does this relate to standard hardware and OEM/ODM?

Start with standard devices joined to your LNS. OEM/ODM makes those devices your SKUs. The IoT platform layer gives you a branded app surface on top — same product-led path from standard products through custom hardware into a solution you own.

Who owns the LoRaWAN network server?

You do. Devices and gateways point at your LNS. The software layer consumes decoded payloads and fleet state from the stack you operate; we do not insert a ParticLIO-hosted network in the middle.

What does a total-solution engagement include?

Hardware platforms for the field, optional OEM/ODM for your brand, and software building blocks for the app layer — with a clear handoff so hosting, LNS, and customer data stay under your control.

IoT platform map with placed sensor devices and site telemetry

Software platform

An IoT device platform you host and operate

Device models, APIs, and application building blocks partners brand and run — ParticLIO does not operate customer networks or host your production stack.

Quick answer

Device models, APIs, and application building blocks partners brand and run — ParticLIO does not operate customer networks or host your production stack. Partners who want a branded application layer on top of ParticLIO hardware — and who operate the network and platform themselves.

The problem we solve

Hardware without a device and app layer leaves partners stitching tools together. They need a starting platform they can brand — while keeping ownership of operations and data.

Partners who want a branded application layer on top of ParticLIO hardware — and who operate the network and platform themselves.

What we ship

Device models and onboarding patterns aligned with our hardware
API and integration hooks for partner applications
White-label UI starting points for dashboards and alerts
Documentation for partners who run their own infrastructure

Product photos

Hardware and reference examples for this line. Public tiles are credited and are not ParticlIO SKUs.

Public application dashboard example — Shiunu / Wikimedia Commons · CC BY-SA 4.0 · example UI, not a ParticlIO product

Digital-twin floor plan with device placement

Hardware bring-up next to the firmware the platform decodes

Spec highlights

Indicative starting points — confirmed per product and project.

Device models

Aligned with ParticLIO sensor, fire, IAQ, and gateway families

APIs

Hooks for dashboards, alerts, and third-party apps

UI layer

White-label dashboard and alert starting points

Hosting

You host and operate — no ParticLIO production SaaS lock-in

LNS

Works with the network server you choose and run

Handoff

Documentation for onboarding, payloads, and partner ops

Platform building blocks

The base you start from — so customization stays focused on what makes the product yours.

Device models aligned with ParticLIO hardware families

Onboarding and provisioning patterns for partner fleets

API hooks for dashboards, alerts, and third-party apps

White-label UI starting points you brand and host

Handoff so you own hosting, data, and network-server choice

Software layer

This is the device and application layer that sits above ParticLIO hardware: models, APIs, and white-label UI you brand and host. Payloads from sensor nodes, fire, IAQ, and gateways land in your LNS first; the platform building blocks help you present and act on that data without ParticLIO operating your network or production stack.

Explore the IoT platform →

Example product starting points

White-label monitoring portal starter
Device onboarding / fleet model pack
Alert and dashboard UI kit
Vertical app shell (fire / IAQ / industrial)

Browse products →

Where partners use it

Typical applications — scope is confirmed per project, not sold as a vertical package.

Partner-branded monitoring portals on top of ParticLIO devices

Vertical apps for fire, IAQ, or industrial sensing

Integrators who want a starting UI without a SaaS lock-in

Brands that already operate their own cloud or BMS stack

OEM / ODM on this base

Start from a standard product platform. Change the parts that make it yours.

Brand, UI, and workflow for your customers

Device models and alert rules for your application

Hosting and operations under your control

APIs into your existing BMS, SCADA, or cloud stack

How engagement works on this platform

Same path across every platform: start from what we ship, customize, then choose OEM, ODM, or full NPI.

Step 1

Start from a platform

Pick a line we already ship — sensor node, fire alarm, IAQ, gateway, or IoT platform — so you are not drawing a blank schematic.

Step 2

Customize what matters

Sensors, enclosure, payload, branding, and marks. Keep the radio, power, and mechanical base that already works.

Step 3

OEM, ODM, or full NPI

Brand a proven LoRaWAN base when you need speed. ODM when the design should be yours. Full NPI when you need electronics through tooling.

Typical deliverables

Platform building blocks and integration guides

White-label configuration for your brand

Hardware–software alignment with ParticLIO devices

Handoff so you own operations and customer data

How this platform fits the ladder

Products → this platform → capabilities → OEM/ODM into a total solution you own.

Services

IoT hardware design and manufacturing — PCB, firmware, enclosure, and assembly in one flow.

See services

Process

How a project runs from NDA and architecture through pilot and production.

Process

Why ParticlIO

One team for OEM/ODM LoRaWAN — design-house depth with manufacturing follow-through.

Why ParticlIO

Contact Us

Tell us about your custom hardware program. An engineer will read it.

Related capabilities

Engineering stack behind this product line.

RF & firmware OEM / ODM programs Engagement process Certify & produce OEM / ODM

Frequently asked questions

Ready to start a project on this platform?

Tell us your target market, marks, and what should change on the standard base. We reply with a sample and engagement plan — not a software subscription.

Other platforms

Sensor node

MCU, radio, power, and enclosure base

Wireless smoke detector — ceiling-mount LoRaWAN life-safety endpoint

Fire alarm

Smoke, CO, heat, and alarm hardware

Public commercial LoRaWAN sensor family — indoor and modular nodes

Indoor air quality

CO₂, VOC, temperature, and humidity

Gateway

LoRaWAN gateway platform