System Architecture

Grid Studio is built around an object-based architecture where devices, data sources, logic systems, and user interfaces interact through a unified project structure.

Instead of separating devices, logic, and visualization into independent systems, Grid Studio connects them through objects inside the Project Tree. These objects generate, process, and exchange data across the entire project.

Understanding how these components interact helps explain how Grid Studio systems are typically structured.


High-Level Data Flow

Most systems built in Grid Studio follow a similar data flow pattern.

Devices / Sensors / Protocols

      Objects

Entities / Parameters / Maps

Workflow / Modifier Logic

Outputs / Interfaces / External Systems

This pipeline describes how data typically moves through a project.


Objects

Objects are the fundamental building blocks of a Grid Studio project.

Every device connection, sensor, logic system, timeline, or interface component exists as an object inside the Project Tree.

Objects can:

  • generate data

  • receive data

  • process data

  • trigger events

  • control other systems

Because of this unified structure, different systems in Grid Studio can interact seamlessly.

More details can be found in Objects.


Data Structures

Grid Studio uses multiple data structures depending on the type of information being handled.

Entities

Entities represent structured datasets, typically produced by devices or integrations.

They are commonly used for:

  • device status information

  • protocol data

  • sensor metadata

Parameters

Parameters represent individual values used for configuration, control, or system behavior.

Examples include:

  • numeric values

  • vectors

  • colors

  • strings

  • boolean states

Parameters can be modified directly in the interface or driven by logic systems.


Data Processing

Once data is available in the system, it can be processed using different logic systems.

Workflows

Workflows are event-driven logic systems.

They react to events such as:

  • parameter changes

  • device state updates

  • user interactions

  • time-based triggers

Workflows are commonly used for automation and system control.


Modifiers

Modifiers provide continuous data processing.

Instead of reacting to events, modifiers update values whenever input data changes.

This makes them ideal for:

  • tracking data processing

  • mathematical operations

  • coordinate transformations

  • high-frequency data manipulation


Interfaces

Grid Studio also provides tools to visualize and interact with system data.

These include:

  • Artboards and Widgets for dashboards and control panels

  • Viewport for spatial visualization

  • Monitoring views such as Logs and Graphs

Interfaces allow users to monitor systems, trigger actions, and operate complex setups.


External Systems

Grid Studio often communicates with external systems such as:

  • media servers

  • game engines

  • lighting systems

  • sensors

  • automation hardware

Communication is typically handled through protocol or device objects, which translate data between Grid Studio and external devices.


Summary

In Grid Studio, devices, logic, and interfaces are connected through a unified object architecture.

Objects generate and exchange data through entities and parameters, while workflows and modifiers process this data and drive system behavior.

This flexible architecture allows Grid Studio to control complex real-time systems while keeping all components connected within a single project structure.

Last updated