Every workspace in Kudzu Canopy NOC is organized around one or more networks. A network is the top-level operational scope that contains all the objects the platform uses for monitoring, mapping, reporting, deployment, and AI analysis. Understanding these objects is essential because they form the foundation that every other feature builds on.
Without a well-structured inventory, the platform cannot compute meaningful KPIs, evaluate alarms, render map layers, or generate AI insights. Each object type carries metadata — location, status, activity timestamps, integration bindings — that feeds into analysis algorithms and connects evidence across the interface. Keeping your inventory accurate and up to date directly improves the quality of every downstream result.
| Object | Description |
|---|---|
| Network | The top-level operational scope. Includes a center point, zones, organizations, permissions, and selected configuration such as frequency plan and sensitivity preferences. |
| Gateway | A physical LoRaWAN gateway with location, model, lifecycle status (Planning / Live / Decommissioned), and traffic activity indicators. |
| Device / mote | A LoRaWAN end device. Devices can be known or externally observed, active or disabled, and carry profile/model metadata and recent activity timestamps. |
| Integration | A configured data connection — LNS integration, HTTP ingress endpoint, or API ingress credential — that brings network evidence into the platform. |
| Frequency plan | Regional RF settings used by analysis algorithms and planning simulations. |
| Zone | A named geographic polygon used for planning, deployment, map filtering, and zone-scoped metric breakdowns. |
| Deployment | A planned or imported network layout containing simulated gateways, sample points, coverage files, and survey metadata. |
A network defines the operational boundary for everything you monitor. When you select a network in the sidebar, every view — Action Center, map, dashboards, alarms, reports — scopes to that network’s data. Networks carry configuration such as the center-point location, the assigned frequency plan, sensitivity preference sliders, support notes, listing options, and resource permissions.
Gateways represent the physical LoRaWAN infrastructure. Each gateway record includes its geographic location, model information, lifecycle status, and integration bindings that link it to records in external LNS systems. The platform tracks gateway activity and classifies gateways as active, idling, inactive, or decommissioned based on recent statistics and traffic. You can optionally enable GPS synchronization to keep the map location updated automatically from the gateway’s antenna signal.
Devices are the LoRaWAN end devices whose traffic the platform ingests. A device can be known (part of your inventory) or external/noise (observed by your gateways but not registered). Activity classification includes active, recently seen, not seen, and disabled states. Each device record shows identity fields (Device EUI, AppEUI, AppKey), an operator-specified location, a platform-estimated location based on signal triangulation, and a signal quality histogram.
Integrations are the data pipelines that bring network evidence into Canopy NOC. Three patterns are available:
Integration records include activity indicators so you can see whether a source is active, idle, failing, or never used.
Zones are user-defined geographic polygons. You draw them on the map under network settings, and the platform uses them to classify traffic by the devices within each region. Zones enable zone-scoped analysis, reporting, metric breakdowns, and map filtering.
Frequency plans define the regional RF parameters that analysis algorithms and planning simulations rely on. Deployments represent planned or imported network layouts — they include simulated gateways, sample points, GeoTIFF coverage files, and survey metadata. Together, they let the platform compare intended coverage against observed behavior.