
Operator by Fibric
Field Dispatch
A managed early-access pattern for matching supported field signals to a reviewed route and dispatch proposal.
ConnectorSensing & telemetry
Pulls a campus of low-power sensors into one feed through your LoRaWAN network server.
Answers are based on this listing. For anything it can't answer, our team can.
For anything this page can't answer, talk to us.
The LoRaWAN connector integrates with your network server (ChirpStack, The Things Stack, or a comparable class of server) rather than the radios themselves. It receives decoded uplinks over the server's API or MQTT integration, applies your payload codecs where the server has not, and emits each reading as a governed event carrying the device EUI, the gateway metadata, and the tenant. LoRaWAN is uplink-mostly by nature, which suits it: door, leak, temperature, and tank-level sensors that report on change or on a slow heartbeat, across a whole campus on batteries.
Because the physical layer is long-range and low-power, the connector treats freshness as a first-class signal: a sensor that stops reporting is itself an event, not a blank spot. This listing is sense-only; no downlinks are issued. It is managed early access: built and maintained by Fibric, and wired with a Fibric deployment engineer through the early-access program.
Authenticates to your LoRaWAN network server with an API key scoped to the applications Fibric may read.
This is a sensing source: it reads, it does not write. Operators act through the write-capable connectors alongside it.
Door, leak, temperature, humidity, and tank-level uplinks across the campus.
Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.
Nothing. This is a sensing source; operators act through the write-capable connectors alongside it.
This listing is informational and not self-serve. A deployment review must validate the connector, credentials, action boundary, recovery path, support, and contractual pricing before use.
Your deployment engineer verifies each line with you during onboarding.
This connector is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.
Listings this is designed to pair with. Each listing has its own live or managed early-access state.

Operator by Fibric
A managed early-access pattern for matching supported field signals to a reviewed route and dispatch proposal.

Operator by Fibric
A managed early-access pattern for reviewing supported telemetry and proposing a maintenance work order before a suspected fault worsens.

Operator by Fibric
A managed early-access pattern for proposing bounded light, air, and access changes against configured room constraints.
Sensing & telemetry connector
Subscribes to your IoT fleet. Every sensor topic becomes a governed event with a timestamp, a source, and a tenant it belongs to.
Control & actuation connector
A managed reference connector for calls and texts. Throttling, stable keys, human authority, and delivery reconciliation reduce repeat-send and flood risk.
This connector is developed, published, and supported by Fibric. It integrates with LoRaWAN Network through published APIs. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy
Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.