Key Concepts

Understanding these core concepts will help you get the most from Inspire.

Endpoints

An Endpoint is a logical target for content delivery. It represents a single screen or display output. Each endpoint has:

• A name and resolution
• An optional paired device
• Assigned scene content
• Schedule rules for when content plays

Endpoints unify what the legacy Optymyse platform called “Displays” and “Agile views” into a single concept.

Scenes

A Scene is a visual layout that contains your content. Think of it as a single screen design. Scenes contain:

• A Layout that divides the canvas into zones
• Zone content — components, media, or data-driven elements placed in each zone
• Schedule rules that control when the scene plays

Scenes can be assigned to one or many endpoints.

Layouts

A Layout defines the zone structure of a scene. A layout has one or more rectangular zones arranged in a grid. Common examples:

Zones

A Zone is a rectangular area within a layout. Each zone holds content independently and can:

• Display a component
• Rotate through multiple content items on a schedule
• Be configured with its own transition effects

Components

A Component is a reusable, themed content block. Components are the primary way to fill zones. Each component has:

• A unique slug for identification
• A set of inputs (data fields the component expects)
• A visual design defined per theme

Components separate content structure from visual presentation. The same component can look different in different themes.

Themes

A Theme is a collection of design tokens and component visual designs. Themes define:

• Colours — Primary, secondary, background, surface, text, and accent palettes
• Typography — Font families, sizes, weights, line heights
• Spacing — Consistent spacing scale
• Shape — Border radius values
• Elevation — Shadow definitions

When you apply a theme to a scene, all components within it adopt the theme’s visual style. Changing the theme re-skins all content instantly.

DataPool

The DataPool is Inspire’s real-time data layer. It:

• Ingests data from Connectors (SQL, files, webhooks, APIs)
• Stores current and historical values as Streams of Items with Fields
• Pushes updates to displays via SignalR in real time
• Supports Snapshots for time-series visualizations

Data flows: Source (external system) -> Connector -> DataPool -> Renderer (display).

Connectors

A Connector is a configured data source that feeds the DataPool. Inspire includes:

Triggers

Triggers automate actions based on conditions. A trigger has:

• Conditions — Rules that evaluate data (e.g. “Temperature > 30”)
• Logic — ALL (every condition must be true) or ANY (at least one)
• Actions — What happens when conditions are met (e.g. switch scene, show alert, override an element)

Triggers enable reactive content — displays that respond to changing data automatically.

Renderer

The Renderer is Inspire’s display client. It runs in a browser on the display device and:

• Receives content and data updates via WebSocket
• Renders scenes using a lightweight Preact-based engine
• Handles transitions, animations, and scheduling locally
• Reports device health and diagnostics back to Edge

The renderer is 18.6 KB gzipped and runs efficiently on low-power signage hardware.

Tenant

A Tenant is an isolated workspace within Inspire. Each tenant has its own:

• Users and roles
• Content library
• DataPool and connectors
• Endpoints and devices
• Themes and templates

Multi-tenancy allows a single Inspire installation to serve multiple organisations or departments.