Service Architecture

Gravio consists of the following application modules:

1. Gravio Studio, a Windows, macOS and iOS application to view, edit and configure the server infrastructure.
2. Gravio HubKit, a server software installed on the edge device (Windows, macOS or Linux) to retrieve sensor data, video feeds, run them past inference models and run Actions.
3. Gravio.com, to store configurations and user settings.

Depending on the Gravio package you chose, you also get

1. Gravio Hub, a Linux based small set-top box you can place in your space
2. Gravio Coordinator, the software you can deploy on your local network or your cloud, which will substitute the above mentioned Gravio.com infrastructure to coordinate your Gravio HubKits including user access, data audit via distributed ledger technology and nodes monitoring.

Gravio Studio (GS)

Gravio Studio, the user-friendly editor available on Windows, Mac, iPad and iPhone, to configure, create and manage your IoT network.

Use Gravio Studio to:

• The setup of physical sensor devices including the mapping of where they are located within a physical space.
• The management of the sensors, monitoring and maintenance.
• To create, configure and maintain Actions that are being triggered by the Sensor networks.
• Data viewing for raw sensor data.
  

Gravio HubKit

Gravio HubKit is the Gravio local server, that runs on your edge computing unit. This can be either a Windows, macOS or Linux machine. Alternatively, you can also run it on a Gravio Hub, which is the hardware we provide. The always-on edge computing server ensures connectivity to the input devices (sensors, readers, APIs) and output devices (also known as “actuators”).

The Gravio HubKit runs the following background services:

• Gravio Control Manager — Server that controls communication with Gravio Studio
• Gravio Trigger Manager — A server that receives sensor data from each device management manager server (Serial Port, Bluetooth, Video, etc.) and stores the sensor data. It also checks if the value of the incoming data applies to the condition specified in the trigger setting, and if so, asks Gravio Action Manager to execute it.
• Gravio Action Manager — Server that performs actions and stores sensor data.
• Gravio Serial Port Manager — Responsible for managing the connection to physical sensors via the serial port and sending the data obtained from the sensor to the Gravio Trigger Manager.
• Gravio Bluetooth Service — Responsible for managing connections to physical sensors connected via Bluetooth and sending the data obtained from the sensors to the Gravio Trigger Manager.
• Gravio Video Service — Responsible for managing the connection with the ONVIF Camera, saving images / videos from the camera, and sending the data obtained from image inference to the Gravio Trigger Manager.
• Gravio MQTT Service — Responsible for sending the data retrieved from MQTT to the Gravio Trigger Manager.
• Gravio IVAR Service — Responsible for sending the data retrieved from IVAR, a video recognition software by Gorilla Technology, to the Gravio Trigger Manager.
  

Gravio.com

Each user of Gravio has access to his or her Gravio.com account. Gravio.com contains configurations, user information, and settings for easier deployment across edge networks. It also hosts your configuration backups. The cloud is operated and hosted by ASTERIA Corporation. For clients who want to manage their own hosted backends on their infrastructure, we have the Gravio Coordinator (Enterprise Edition only).

Gravio Coordinator

If you choose not to use the Gravio.com hosted service, you can also use the Gravio Coordinator in the enterprise edition of Gravio. The Gravio Coordinator runs on either the Gravio Hub or from a Docker Container on your own (corporate) infrastructure. In this way, you have full control over your IoT infrastructure and the entire stack is hosted on-premise.

The Gravio Coordinator also helps coordinating the various Gravio HubKits in your network to stay in sync, be monitored and audit the collected sensor data, that has been collected and stored in a decentralised way across all the devices in a blockchain / distributed ledger. This technology allows you to perform audits of the data with the confidence that it has not been tampered with.