Real-time no-code studio

Assembling without code, from blocks

The principle of the studio is to replace the development of a business application with visual assembly. You place blocks on a work surface, you wire them together — a source to a display, a control to a socket — and you configure them in a dedicated panel. There is no compilation or deployment to manage: the application is built and tested in the same interface.

Each block exposes inputs and outputs. A video player consumes an RTSP source and produces an image; a UDP socket sends and receives frames; a widget displays a value or triggers a command. By wiring these inputs and outputs together, you describe your application's data flow without ever touching the underlying code.

The available blocks

The studio covers the recurring needs of real-time applications: receiving video, exchanging network frames, talking to specialized equipment and presenting it all in an interface. The main blocks are the following.

• RTSP/RTP video players — to display camera streams directly in the application, without an intermediate transcoding gateway.
• UDP/TCP sockets — to send and receive raw frames to a device, a controller or a service, with direct control of the protocol.
• WebSocket — to connect the application to real-time services and exchange bidirectional messages with a server or another node.
• MAVLink — to talk with compatible drones and machines: telemetry, flight commands, status feedback.
• ONVIF — to discover and control compliant network cameras (profiles, streams, PTZ controls depending on the device).
• Custom widgets — gauges, buttons, indicators, maps and custom displays to build the dashboard or the control console.

Real time in the browser

A studio application runs in the browser, but the browser is not confined to the role of a mere display client: it can become a genuine mesh node. The VIGIL-MESH core is embedded as WASM in the page, which lets the application send and receive real-time streams like any other node, without installing software on the workstation.

Concretely, the application's network and video blocks can then reach members of the network directly — cameras, machines, services — instead of going through an intermediary. The browser becomes a full-fledged real-time access point within the mesh.

How the browser node works, its prerequisites and its setup are detailed on the page “Installing the browser node” (/en/docs/install-navigateur).

Use cases

The studio targets applications where network data, video and control meet in a single interface: supervising a fleet of cameras, a dashboard for an industrial site, or a control console for machines and drones.

Controlling machines and drones — latency stakes, command chain, MAVLink and ROS 2 integration — is covered on the dedicated page “Controlling machines and drones” (/en/docs/cas-ros2).