Skip to main content

Custom Control and Data Workflows

Custom Control and Data Workflows

Reality Hub provides an open environment for connecting external data, custom controls, dashboards, and automation systems with live Reality 5 productions. Data handling and business logic can be managed in dedicated Reality Hub modules, keeping rendering projects focused on graphics instead of external API connections, data parsing, and operational control.

Through a layered module architecture, developers can combine server-side logic with browser-based user interfaces that appear directly inside Reality Hub. These modules can collect and prepare data, control Lino rundowns, update running graphics, and distribute information across multiple engines and outputs from one centralized operational layer.

Reality Hub Custom Modules & 3rd Party Data Integration

What it enables

  • Layered custom module development Build Reality Hub modules with a server layer for data processing and production logic, together with a browser-based interface for operators. Modules integrate through the Reality Hub SDK without requiring changes to the core platform.
  • Centralized data handling Fetch, validate, normalize, filter, and transform external data inside the module layer before it reaches graphics templates or running engines.
  • Flexible data-source integration Connect market feeds, sports data, weather services, election systems, newsroom platforms, spreadsheets, databases, and other external sources according to production requirements.
  • Data-driven Lino playout Create and update Lino rundown items programmatically, allowing graphics to be prepared with current values before operators or automation systems take them to air.
  • Multi-engine data distribution Send prepared data from one Reality Hub workflow to multiple engines, channels, parallel outputs, or backup configurations without duplicating the integration logic inside every rendering project.
  • Persistent production state Store operator selections and module state on the server so custom interfaces can restore the required production context after a browser refresh or reconnection.
  • Browser-based control Make custom controls and data interfaces available within the web-native Reality Hub environment, reducing the need to build and deploy a separate desktop application for every integration.
  • REST API control Connect in-house applications and third-party systems to shows, engines, nodegraphs, channels, rundowns, and playout operations through documented APIs.
  • Controlled external access Use API keys and permission policies to manage how custom modules, automation systems, and external applications interact with the production environment.

Reality Hub Custom Modules & 3rd Party Data Integration

Built for Faster Custom Development​

Reality Hub uses familiar web technologies, open documentation, REST APIs, and SDK-based development patterns, making custom workflows easier to prototype and maintain. Teams can also use AI-assisted development tools to create initial module structures, control panels, data connectors, and playout logic, then refine them for their own production requirements.

This approach allows broadcasters to build focused tools for finance, weather, sports, elections, newsroom graphics, and other data-driven productions without forcing custom logic into Unreal Engine templates or relying on disconnected control applications.

Click here to visit official documentation.