Canopy supports a flexible integration architecture that enables comprehensive remote monitoring and management of connected devices—ranging from full-featured endpoints like kiosks and industrial PCs to lightweight sensors and IoT components. The platform supports four primary integration models, each offering varying levels of data access, control, and deployment complexity.
1. Leaf Agent Installation (Deepest Integration)
Platform-level integration with the most comprehensive capabilities
This is Canopy’s most robust integration approach, using the Leaf software agent installed directly on Windows or Linux-based devices. With full access to device-level data and control, Leaf allows for in-depth monitoring, remote operations, and automated management.
Key Capabilities:
- Full device telemetry and health monitoring
- Deep remote control (e.g., file management, command execution, reboot, remote desktop)
- Software deployment and updates
- Local event processing and automation
- Real-time alerting and diagnostics
Common Use Cases:
Self-service kiosks, Windows/Linux controllers, NVRs, digital signage, industrial PCs
2. Network-Based Leaf Deployment (Integration Level Varies based on network protocol used)
Flexible monitoring via network protocols and local APIs
In this model, Leaf runs on a local network-connected device (such as a gateway or edge PC) and interfaces with nearby equipment using network protocols like ICMP Ping, SNMP, or local APIs. Integration depth varies based on the target device’s interface.
Integration Scenarios:
- ICMP Ping: Online/offline monitoring only
- SNMP: Can retrieve device telemetry and other useful information for monitoring depending on the device configuration
- API Access: Enables firmware updates, device restarts, telemetry collection, and more active management capabilities
Key Capabilities:
- Network-based health and status monitoring
- Some control capabilities (restarts, configuration changes)
- Covers multiple device types on the same subnet
Common Use Cases:
IP cameras (e.g., Axis), smart sensors, IoT endpoints, payment terminals, printers
3. Cloud-to-Cloud Integration (Integration level varies based on API capabilities of other system)
Device data shared between Canopy and third-party cloud platforms
This model connects Canopy’s cloud platform to other cloud-managed device ecosystems using APIs. It mirrors many capabilities of a local API integration but is managed entirely at the enterprise level rather than through Leaf.
Key Capabilities:
- Monitoring and diagnostics based on data exposed by the third-party API
- Device inventory and status visibility
- Management actions, where supported by the source platform
Integration Depth:
Varies by the third-party system’s API richness
Common Use Cases:
MDM platforms (Android/iOS), smart PDUs, cellular routers, cloud-connected kiosks
4. Direct-to-Cloud Device Messaging (Dependent on device capabilities)
Device sends data directly to Canopy’s Leaf Broker in the cloud
This lightweight integration bypasses Leaf entirely—devices publish data payloads (via MQTT, HTTPS, etc.) directly to the Canopy Leaf Broker in the cloud. There’s no on-device or network-based Leaf agent required.
Key Capabilities:
- Basic telemetry ingestion
- Monitoring and analytics dashboards
- Actions can be enabled based on capabilities of edge device integration
- Event-driven alerting
Limitations:
- Relies on device manufacturer support for direct publishing
Common Use Cases:
MQTT-enabled devices, LoRaWAN gateways, purpose-built smart sensors, Smart PDU’s
Selecting the Right Integration Path
Each integration method supports a range of use cases and device types. For the richest capabilities, installing the Leaf Agent directly on the device remains the preferred approach. However, the flexibility of network-based, cloud-to-cloud, and direct-to-cloud integrations enables Canopy to support diverse operational environments and product architectures.