Industries
We don't sell industry playbooks. We design and build the LoRaWAN and IoT hardware those environments actually run — sensor nodes, detectors, IAQ, and gateways.
LoRaWAN IAQ, occupancy-adjacent sensing, and life-safety endpoints for a BMS you already run.
LoRaWAN ceiling and wall IAQ, occupancy-adjacent sensing, and life-safety endpoints that report into a BMS or monitoring stack the customer already owns. Indoor gateways sit on the same band plan.
Typical hardware
Battery-first outdoor nodes — air, water, and climate on a multi-year radio budget.
Battery-first outdoor and indoor nodes: radio, power, and gasket designed together so a multi-year budget is measured, not hoped.
Typical hardware
Long-range soil, weather, and leak nodes plus outdoor gateways. No new field cabling.
Long-range, low-power end nodes and outdoor gateways. Enclosure UV and seal choices sit in the same review as the radio.
Typical hardware
Condition-monitoring LoRaWAN nodes and gateways that report into the stack you operate.
DIN / pole / enclosure options, RS-485 or sensor hooks on a shared radio base, and firmware that reports into the stack you operate.
Typical hardware
Small battery end-nodes: sleep current, wake strategy, and abuse tested before volume.
Small, battery-first nodes: sleep current, wake strategy, and mechanical abuse tested before anyone talks volume.
Typical hardware
IAQ, comfort, and smoke/CO hardware that looks like a commercial product, not a lab box.
IAQ and comfort sensing plus life-safety SKUs that look like a commercial product — CMF and install geometry, not a lab box.
Typical hardware
LoRaWAN product families — not a stock industry collage, and not a factory tour.
Life safety
Battery LoRaWAN detectors with marks scoped per SKU and market. Start from a reference unit, then CMF, pack-out, and payload.
Continue this threadBuildings
CO₂, VOC, temperature, humidity in a documented LoRaWAN uplink. Ceiling or wall housing designed to be tooled.
Continue this thread
Field nodes
Sleep current and wake strategy are designed and measured. Outdoor gaskets sit in the same review as the antenna.
Continue this threadEdge
Band, backhaul, and enclosure variants. You run the LoRaWAN network server.
Continue this threadSensor node, fire, IAQ, gateway, and an IoT software layer. Start here when you do not want a blank schematic.
Hardware platform
A proven end-node platform — MCU, LoRaWAN radio, power path, and enclosure options — so partners add sensors, branding, and payloads instead of starting from a blank schematic.
Fire safety
Smoke, CO, heat, and related alarm hardware as a product line partners customize — housing, marks, and panel integration — while we handle LoRaWAN and manufacturing.
Building sensing
Indoor air quality and environmental sensing — CO₂, VOC, temperature, humidity — with LoRaWAN payloads partners adapt for BMS and building automation.
Network edge
Gateway hardware as a customizable platform — regional band, backhaul, enclosure, and antenna — so partners ship network edge devices under their brand.
Software platform
Device models, APIs, and application building blocks partners brand and run — ParticLIO does not operate customer networks or host your production stack.
Anonymous project notes — problem, what we did, what the partner kept. No customer names.
Problem. An outdoor environmental node needed IP-rated housing. The first ID concept boxed the antenna and killed range.
What we did. Electronics and industrial design sat in one review: antenna keep-out, gasket, and wall thickness. 3D print for feel, CNC for RF and fit, then mold-ready CAD.
What they kept. A housing that still meets the radio budget. The partner owns the CAD, keep-out drawing, and DFM notes.
Problem. A facility node needed extra I/O and a different battery than the reference. The team did not want to buy a steel tool on an unproven layout.
What we did. Schematic and layout with RF and battery isolation on pass one. Automated DFM, then a small SMT run and bring-up report.
What they kept. Working prototypes and a file set (Gerbers, BOM, pick-and-place) ready for pilot — without a second vendor re-learning the board.
Problem. The same end-node family had to join EU868, US915, and AS923 networks with one payload map.
What we did. Firmware variants on a shared radio stage: join, ADR, and documented uplink fields. Current draw measured against the battery budget.
What they kept. Band SKUs the partner flashes and points at their own network server. Payload notes stay with them.
Problem. A life-safety reseller needed their name on a battery LoRaWAN smoke/CO device, with CE and EN 14604 scoped for the market — not a generic box.
What we did. Started from the fire-alarm product line. Brand, CMF, pack-out, and alarm payload mapped to their monitoring stack. Marks planned per SKU, not as a company stamp.
What they kept. Pilot units under their brand, plus a certification plan they can take to the next market.
Problem. A building team had wireless CO₂ / VOC sensors that joined a network but arrived as undocumented bytes.
What we did. IAQ platform firmware with a published uplink map (CO₂, VOC, temperature, humidity, status) and configurable intervals. Ceiling housing and CMF for commercial interiors.
What they kept. Devices the partner points at their LNS and BMS. They own the application layer; we own getting the hardware and payload right.
Problem. A campus rollout needed Ethernet indoor units and a pole-mount outdoor unit on the same band plan.
What we did. Shared concentrator and backhaul options; two enclosures and antenna kits. Onboarding notes for the LNS they already run.
What they kept. One radio family, two install SKUs, documentation they keep. We do not operate the network.
Services, Process, and Why ParticlIO — then Contact Us so an engineer can read your brief.
IoT hardware design and manufacturing — PCB, firmware, enclosure, and assembly in one flow.
See servicesOne team for OEM/ODM LoRaWAN — design-house depth with manufacturing follow-through.
Why ParticlIO