|updated: 9/7/2017||About IoT Vendor Scorecards|
IoT Function Provider
CloudLeaf could be considered an IoT Platform Provider, except that they appear to be focused more on providing pre-built experiences for specific verticals of Manufacturing, Distribution, Pharmaceuticals, and Life Sciences. Since it’s not clear if their platform is open for others to develop applications on top of (my definition of Platform Provider is this level of openness), I’ve categorized them as Function Provider. Since it appears that CloudLeaf just publicly launched their offering, they may still be trying to determine which way they want to take their offering, if that direction becomes more clear in the future, they may get recategorized.
They categorize their offering into three buckets:
- Sensor Fabric -which combines location aware sensors, gateways and backend cloud services within Data & Insight.
- Business Rules Engine – their Messaging & Automation capabilities
- Actionable Insight – their prebuilt UI’s for their specific vertical use cases.
CloudLeaf is a private company founded in 2014 that received an undisclosed Series A round of funding in early 2017. Their platform appears to have been recently released since there is no developer enablement information publicly available nor details around their listed use cases.
- Physical Devices
- Sensor – CloudLeaf products two of their own sensors:
- CloudLeaf Sensor is a multi-purpose battery operated sensor unit which can measure “telementry” data (they only list temperature, shock, and vibration). The sensor can operate indoor, outdoor, and in transit.
- CloudLeaf Zone Sensor is a battery or power (power source not specified) location sensor which can measure location down to 3 feet accuracy.
- Communication – The CloudLeaf sensors communicate via BlueTooth Smart to their own CloudLeaf gateway. No detail is given regarding security from sensor to gateway.
- Physical Edge Gateways – CloudLeaf Gateway is a lightweight mesh enabled network gateway. No details are provided on the mesh network capabilities.
- Communications – CloudLeaf Gateway talk Bluetooth Smart to the sensors and uses Wifi or Cellular to connect to the internet. No details are given regarding the security or internet protocol aspects of the gateway. It appears to be designed to just connect to CloudLeaf’s cloud services.
- Data Storage
Data & Insight
- Things Operational Big Data – It is implied that CloudLeaf is storing all the data collected from the sensors as part of their Cloud based capabilities.
- Stream Analytics – CloudLeaf’s currently doesn’t provide details around their Business Rules Engine but my assumption is that the rules engine would be functioning in real-time on the stream data coming in from the sensors.
- Machine Learning
- Thing Meta Data – It appears CloudLeaf has a Thing Meta Data repository to help model all the deployed sensors against the environment they are deployed in. But it is not clear if this model is predefined, needs to be defined by the customer, or can only be defined by CloudLeaf. No specific details are currently provided.
- User Meta Data – It is assumed that CloudLeaf supports some sort of User Meta Data repository for the users login to their cloud services. The granularity or multi-tenant nature of this repository is not currently provided.
Messaging & Automation
- Communications and Messaging – It is implied that CloudLeaf gateways (and the sensors behind them) are communicating securely via a standard protocol to their cloud services. Since they are
- Identity Access Management – It is assumed that CloudLeaf’s services support multiple user with customized views per users. Details of this capability is not currently provided publicly.
- Event Processing – CloudLeaf’s Business Rules Engine appears to support basic events which can be defined by thresholds on sensor data. Actions that can be taken based on these events are not currently provided publicly.
- Integration – CloudLeaf doesn’t appear to have any integration capabilities to expand the rules engine beyond basic rules triggered by the sensor data.
- Web Interface – The CloudLeaf cloud services provide some level of administrative and end user web interfaces. Specific details are not currently provided publicly.
- Mobile Interface – It is unclear if there are native mobile interfaces (mobile applications) that are provided or just a web interface which can provide a mobile like experience.
- Voice Interface
- Interface Development APIs – It is not clear if the CloudLeaf cloud services are API enabled which would allow a developer to wrap their functionality within a higher level application.
- Interface Development Environment
- Encryption – While not specifically detailed, it is assumed that sensor data is encrypted from the gateway to the cloud if not also from the sensor to the gateway. No details are provided regarding the encryption of the Operational data collected from the sensors or other data repositories that are part of their cloud services.
- Access Control – The specific level of access control that is provided by the CloudLeaf cloud services is not currently provided publicly.
- Identity Management – The CloudLeaf cloud services provides some level of identity management between their sensors and cloud services, but specific details are not currently provided publicly.
- Secure Device Updates
- Device Lifecycle / Operations – There appears to be a basic sensor/gateway lifecycle management capabilities implied by CloudLeaf. Specific details are not currently provided publicly.
- Security – There appears to be a basic level of security management provided by the CloudLeaf cloud services, but specific details are not currently provided publicly.