

SMT / PCBA
The same file set, on the line
Prototype, pilot, then volume. Mid-size runs are welcome. We do not publish a capacity number here.

PCB assembly services for the same LoRaWAN SKU — built where it was designed.
SMT, assembly, and functional test for the same LoRaWAN and IoT products we design — fixtures written for that radio and payload, not a generic ICT recipe. When a node fails join or a gateway drifts, the person who laid out the board is in the conversation.
Prototype, pilot, and production placement with the same file set the design team signed. Mid-size runs to scale — we do not publish capacity figures here.
Optical inspection plus fixtures and scripts written against the product, not a generic ICT recipe.
Housing, labels, and shipping configuration under the same project lead as the board.
CE/FCC and related marks planned per product and target market. We do not claim company-wide certification for every SKU.
When a part goes end-of-life, the engineer who laid out the board reviews the alternate — design and line stay in one loop.
The drawing, then the floor that proves it.


SMT / PCBA
Prototype, pilot, then volume. Mid-size runs are welcome. We do not publish a capacity number here.
Assembly
Final assembly next to the people who designed the snaps and the label. Yield drift is a conversation.


Test & ship
Functional test written for the SKU. Pack-out and handoff under the same project lead.
Design moves onto the line without a second vendor to re-learn the product. Flexible volumes — quote per project.
You own every design file — at every milestone, not just at the end.
Anonymous project notes — problem, what we did, what the partner kept. No customer names.

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. 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 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.
Sensor node, fire, IAQ, gateway, and an IoT software layer. Start here when you do not want 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.
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