Blinky-Lite™

Architecture for remote monitoring and control.

Blinky-Lite combines device-initiated messaging, web applications and role-based permissions in a layered approach to control-system access.

The basic idea

Connect equipment and people through controlled pathways.

Devices communicate through a message broker. Blinky-Lite applications present information and controls to users, with permissions governing what those users can access.

1. Devices

Devices initiate connections from inside the facility and exchange messages through an MQTT broker.

2. Platform

Blinky-Lite brings together application, data and notification services to support monitoring and operation.

3. Authorized users

Users interact through web applications. Role-based permissions help determine what they can see and do.

Device communication

Connections initiated from inside.

Blinky-Lite uses MQTT publish-subscribe messaging. In the architecture described here, devices initiate connections to a broker rather than requiring users to connect directly to each device for data.

This design can reduce the need to expose edge devices directly for remote access. Device authentication, broker permissions and network configuration remain important.

Layered security

Role-based permissions, authentication, controlled routing and network isolation can work together to limit access.

No communication protocol or architecture guarantees security on its own. Protection depends on the specific deployment, configuration, maintenance and operating practices.

Platform components

Services working together.

The architecture uses containerized services for platform functions. The exact configuration depends on the deployment.

Application server

Serves the web applications users interact with.

Database and notifications

Support data and application configuration, alarms and notification functions.

Message broker

Routes publish-subscribe messages between devices and platform components.

Access and deployment

Designed for more than one environment.

A deployment can serve users within a facility and can also be configured for remote access using additional controlled network pathways.

Multiple Blinky-Lite systems can also be connected through broker arrangements that share selected information. The appropriate configuration depends on the application and security requirements.

Explore the technical documentation

The existing Blinky-Lite documentation remains available while we develop this unified website.

Open the documentation →

Discuss your system

Every deployment has different requirements.

Talk to BL Monitor and Control about your equipment, connectivity, remote-access needs and integration plans.

Email us

Video