One conversation
Radio, battery, and housing share a room
When an IAQ ceiling node needs one more millimeter for a cell, or a gateway antenna keep-out fights the gasket, that is a conversation — not a change order across a contract.
Why ParticlIO
One IoT hardware partner — not a vendor chain
OEM and ODM LoRaWAN for nodes, detectors, and gateways. Design-house depth, manufacturing follow-through, AI-driven speed.
Radio, battery, and housing in one conversation
The LoRaWAN SKU and the files that build it belong to the same lead.
Same files
The SKU the engineer signed is the SKU that ships
Schematic, Gerbers, firmware, and CAD stay with the same lead through bring-up and pack-out. You own those files at every milestone — and you run the network they join.
One team, end to end
Fewer handoffs, fewer surprises, one schedule.
Electronics, firmware, cloud software, industrial design, and manufacturing live in one project flow with one accountable lead. When the enclosure needs one more millimeter for a battery holder, that's a conversation across the room — not a change order across a contract.
AI-accelerated engineering
Faster iterations, fewer respins.
AI-assisted schematic review, automated DFM on every board revision, and AI-assisted test coverage planning. It is how we work — not something we put on a slide.
Commercial IoT specialists
LoRaWAN products that respect radio, battery, and field life.
Sensor nodes, fire and IAQ endpoints, and gateways — not a generic board shop guessing at duty cycles. Join, ADR, payload, and enclosure keep-out are designed together. You run the network server.
Built for overseas teams
English-first communication. Your IP stays yours.
NDA-first, English-first engineering, remote acceptance, and design files that belong to you at every milestone — not just at the end.
How we sit in the market
| If you talk to | The usual gap | What you get here |
|---|---|---|
| Design studio | Stops at files. You still have to find a line and own the break. | Design and manufacturing in one team. The board is drawn to be built. |
| Large EMS | Small programs wait. Design is not the job. | Mid-size runs are welcome. Design is the main work. |
| Trading / turnkey broker | Work is farmed out. Credit for the result is usually not. | Our engineers own the project from schematic to shipping box. |
AI in the loop, not on the label
We use AI where it changes outcomes: reviewing schematics for errors before they cost a respin, running automated design-for-manufacturing checks on every board revision, and stress-testing validation plans before pilot production. No efficiency percentages. No tool names. An engineer still signs the revision.
What this looks like on a real product
Anonymous project notes — problem, what we did, what the partner kept. No customer names.
Outdoor node — enclosure vs antenna
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.
Custom sensor board — prove it before a panel
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.
One family, three regional bands
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.
Depth comes from products we already ship
Sensor node, fire, IAQ, gateway, and an IoT software layer. Start here when you do not want a blank schematic.
Hardware platform
Sensor node
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.
- · Condition-monitoring end node (industrial)
- · Facility multi-sensor wall node
- · Outdoor environmental / agriculture node
Fire safety
Fire alarm
Smoke, CO, heat, and related alarm hardware as a product line partners customize — housing, marks, and panel integration — while we handle LoRaWAN and manufacturing.
- · Wireless smoke detector (LoRaWAN)
- · CO / smoke combo detector SKU
- · Heat alarm endpoint for commercial ceilings
Building sensing
Indoor air quality
Indoor air quality and environmental sensing — CO₂, VOC, temperature, humidity — with LoRaWAN payloads partners adapt for BMS and building automation.
- · Ceiling CO₂ / VOC IAQ sensor
- · Wall-mount temp / humidity node
- · Multi-parameter office IAQ endpoint
Network edge
Gateway
Gateway hardware as a customizable platform — regional band, backhaul, enclosure, and antenna — so partners ship network edge devices under their brand.
- · Indoor LoRaWAN gateway (Ethernet backhaul)
- · Outdoor pole-mount gateway
- · Cellular-backhaul edge gateway
Software platform
IoT platform
Device models, APIs, and application building blocks partners brand and run — ParticLIO does not operate customer networks or host your production stack.
- · branded monitoring portal starter
- · Device onboarding / fleet model pack
- · Alert and dashboard UI kit
How engagement fits together
Services, Process, and Why ParticlIO — then Contact Us so an engineer can read your brief.
01
Services
IoT hardware design and manufacturing — PCB, firmware, enclosure, and assembly in one flow.
See services03
Why ParticlIO
One team for OEM/ODM LoRaWAN — design-house depth with manufacturing follow-through.
Why ParticlIO